{
  "version": 1,
  "base_url": "https://lorincz-llc.github.io/diagrams/",
  "url_resolution": "Resolve relative URL fields against base_url.",
  "nodes": [
    {
      "id": "fpv/field-kit",
      "title": "When each piece of the FPV kit comes out",
      "url": "diagrams/fpv/field-kit/",
      "kind": "diagram"
    },
    {
      "id": "fpv/control-and-video",
      "title": "The sticks and the picture use separate radio links",
      "url": "diagrams/fpv/control-and-video/",
      "kind": "diagram"
    },
    {
      "id": "fpv/charge-and-rotate",
      "title": "Four flight packs, two charger channels",
      "url": "diagrams/fpv/charge-and-rotate/",
      "kind": "diagram"
    },
    {
      "id": "fpv/props-and-field",
      "title": "From props-off bench to the next pack",
      "url": "diagrams/fpv/props-and-field/",
      "kind": "diagram"
    },
    {
      "id": "fpv/airspace-and-height",
      "title": "Which altitude applies at this U.S. recreational site?",
      "url": "diagrams/fpv/airspace-and-height/",
      "kind": "diagram"
    },
    {
      "id": "fpv/remote-id",
      "title": "When to use the Holy Stone broadcast module",
      "url": "diagrams/fpv/remote-id/",
      "kind": "diagram"
    },
    {
      "id": "fpv/height-over-terrain",
      "title": "Level flight can climb above the 400 ft AGL ceiling",
      "url": "diagrams/fpv/height-over-terrain/",
      "kind": "diagram"
    },
    {
      "id": "fpv/pack-energy",
      "title": "How much nominal energy is in each pack?",
      "url": "diagrams/fpv/pack-energy/",
      "kind": "diagram"
    },
    {
      "id": "network/tcp-return",
      "title": "Where did the reply go?",
      "url": "diagrams/network/tcp-return/",
      "kind": "diagram"
    },
    {
      "id": "network/globalprotect",
      "title": "A GlobalProtect connection",
      "url": "diagrams/network/globalprotect/",
      "kind": "diagram"
    },
    {
      "id": "network/public-dns",
      "title": "Who answers a public DNS lookup?",
      "url": "diagrams/network/public-dns/",
      "kind": "diagram"
    },
    {
      "id": "agent-work/split-the-work",
      "title": "Should two agents take this job?",
      "url": "diagrams/agent-work/split-the-work/",
      "kind": "diagram"
    },
    {
      "id": "agent-work/resume-from-a-checkpoint",
      "title": "Resume a diagram build after a timeout",
      "url": "diagrams/agent-work/resume-from-a-checkpoint/",
      "kind": "diagram"
    },
    {
      "id": "agent-work/review-the-change",
      "title": "Review one changed connection",
      "url": "diagrams/agent-work/review-the-change/",
      "kind": "diagram"
    },
    {
      "id": "data/terrain-clearance",
      "title": "Aircraft and terrain elevations",
      "url": "data/terrain-clearance/",
      "kind": "dataset"
    },
    {
      "id": "data/pack-energy",
      "title": "Flight and radio pack nameplates",
      "url": "data/pack-energy/",
      "kind": "dataset"
    }
  ],
  "edges": [
    {
      "from": "fpv/field-kit",
      "to": "fpv/control-and-video",
      "relation": "next-step",
      "reason": "Follow the radio and goggles signal paths before powered bench checks."
    },
    {
      "from": "fpv/field-kit",
      "to": "fpv/charge-and-rotate",
      "relation": "explains",
      "reason": "See exactly where each of the four flight packs connects and when to swap it."
    },
    {
      "from": "fpv/field-kit",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Follow the handoff from a props-off bench to a single installed flight pack."
    },
    {
      "from": "fpv/field-kit",
      "to": "fpv/airspace-and-height",
      "relation": "prerequisite",
      "reason": "Choose a permitted site and ceiling before the outing."
    },
    {
      "from": "fpv/control-and-video",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Inspect and fit the props only after the bench control and video checks."
    },
    {
      "from": "fpv/control-and-video",
      "to": "fpv/field-kit",
      "relation": "explains",
      "reason": "Find the transmitter battery, goggles supply, quad and tools in the day’s order."
    },
    {
      "from": "fpv/control-and-video",
      "to": "fpv/remote-id",
      "relation": "contrasts",
      "reason": "Remote ID is a separate broadcast with its own status and operating requirements."
    },
    {
      "from": "fpv/charge-and-rotate",
      "to": "fpv/field-kit",
      "relation": "explains",
      "reason": "See when to charge, carry, install and put away each kind of pack."
    },
    {
      "from": "fpv/charge-and-rotate",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Fit one ready pack after the props and field checks are complete."
    },
    {
      "from": "fpv/props-and-field",
      "to": "fpv/control-and-video",
      "relation": "prerequisite",
      "reason": "Verify live controls, disarm, failsafe and camera feed on the props-off bench."
    },
    {
      "from": "fpv/props-and-field",
      "to": "fpv/charge-and-rotate",
      "relation": "prerequisite",
      "reason": "Select a healthy, ready flight pack from the four-pack rotation."
    },
    {
      "from": "fpv/props-and-field",
      "to": "fpv/remote-id",
      "relation": "prerequisite",
      "reason": "Verify the add-on module before the flight when using the broadcast-module route."
    },
    {
      "from": "fpv/props-and-field",
      "to": "fpv/airspace-and-height",
      "relation": "prerequisite",
      "reason": "Check the actual launch location, restrictions and ceiling."
    },
    {
      "from": "fpv/airspace-and-height",
      "to": "fpv/height-over-terrain",
      "relation": "explains",
      "reason": "Work out the height above the changing ground in a numerical example."
    },
    {
      "from": "fpv/airspace-and-height",
      "to": "fpv/remote-id",
      "relation": "prerequisite",
      "reason": "Check the aircraft’s Remote ID route and the pilot visibility condition."
    },
    {
      "from": "fpv/airspace-and-height",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Complete the equipment checks at the permitted field."
    },
    {
      "from": "fpv/remote-id",
      "to": "fpv/airspace-and-height",
      "relation": "prerequisite",
      "reason": "Check the permitted area, height and current airspace restrictions as a separate decision."
    },
    {
      "from": "fpv/remote-id",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Check the module’s status while preparing the aircraft at the field."
    },
    {
      "from": "fpv/remote-id",
      "to": "fpv/control-and-video",
      "relation": "contrasts",
      "reason": "The ID broadcast, flight-control signal and camera feed serve distinct purposes."
    },
    {
      "from": "fpv/height-over-terrain",
      "to": "fpv/airspace-and-height",
      "relation": "prerequisite",
      "reason": "Establish which limit applies before using the figure’s 400-foot reference line."
    },
    {
      "from": "fpv/height-over-terrain",
      "to": "fpv/props-and-field",
      "relation": "next-step",
      "reason": "Use the chosen route and ceiling when briefing the crew at the field."
    },
    {
      "from": "fpv/pack-energy",
      "to": "fpv/charge-and-rotate",
      "relation": "next-step",
      "reason": "Identify the proper charging program and sequence for each physical flight pack."
    },
    {
      "from": "fpv/pack-energy",
      "to": "fpv/field-kit",
      "relation": "explains",
      "reason": "See when the four aircraft packs and the separate transmitter pack each come out."
    },
    {
      "from": "network/tcp-return",
      "to": "network/globalprotect",
      "relation": "prerequisite",
      "reason": "Locate the VPN gateway and its inside interface before following the inner TCP connection."
    },
    {
      "from": "network/tcp-return",
      "to": "agent-work/resume-from-a-checkpoint",
      "relation": "analogy",
      "reason": "A packet capture and a persisted job record both identify the last step with evidence. Each leaves the following step to be checked."
    },
    {
      "from": "network/tcp-return",
      "to": "agent-work/review-the-change",
      "relation": "next-step",
      "reason": "See how a second reader can verify the missing-hop label against the two capture points."
    },
    {
      "from": "network/globalprotect",
      "to": "network/tcp-return",
      "relation": "next-step",
      "reason": "Trace one inner connection after decapsulation and compare the observations across two hops."
    },
    {
      "from": "network/globalprotect",
      "to": "network/public-dns",
      "relation": "explains",
      "reason": "When a portal or gateway is configured by hostname, DNS can supply its address before the app connects."
    },
    {
      "from": "network/globalprotect",
      "to": "fpv/control-and-video",
      "relation": "analogy",
      "reason": "A working portal exchange alone tells you little about traffic through the tunnel. On a quad, a working control link alone tells you little about the video link. The two examples use different protocols."
    },
    {
      "from": "network/public-dns",
      "to": "network/globalprotect",
      "relation": "next-step",
      "reason": "After the app has an address for a configured hostname, follow portal configuration and gateway selection."
    },
    {
      "from": "network/public-dns",
      "to": "network/tcp-return",
      "relation": "contrasts",
      "reason": "A DNS answer supplies an address. The TCP trace follows a separate exchange to determine how far a reply actually traveled."
    },
    {
      "from": "agent-work/split-the-work",
      "to": "fpv/field-kit",
      "relation": "explains",
      "reason": "Inspect the concrete equipment page that writer A is responsible for."
    },
    {
      "from": "agent-work/split-the-work",
      "to": "fpv/airspace-and-height",
      "relation": "explains",
      "reason": "Inspect the independently sourced airspace page that writer B is responsible for."
    },
    {
      "from": "agent-work/split-the-work",
      "to": "agent-work/resume-from-a-checkpoint",
      "relation": "next-step",
      "reason": "Give each long-running branch a record that another worker can verify and resume."
    },
    {
      "from": "agent-work/split-the-work",
      "to": "agent-work/review-the-change",
      "relation": "next-step",
      "reason": "Give the integrated output to a reviewer with its exact source revision and reader-facing finish condition."
    },
    {
      "from": "agent-work/resume-from-a-checkpoint",
      "to": "agent-work/split-the-work",
      "relation": "prerequisite",
      "reason": "A stable job ID, an owner and an agreed output make the checkpoint useful across workers."
    },
    {
      "from": "agent-work/resume-from-a-checkpoint",
      "to": "network/tcp-return",
      "relation": "analogy",
      "reason": "Both the journal and the packet capture mark progress observed at a specific point. A later step needs its own evidence."
    },
    {
      "from": "agent-work/resume-from-a-checkpoint",
      "to": "fpv/charge-and-rotate",
      "relation": "next-step",
      "reason": "Open the actual subject of the next page in this worked build queue."
    },
    {
      "from": "agent-work/review-the-change",
      "to": "network/tcp-return",
      "relation": "explains",
      "reason": "Open the candidate's subject and inspect the observed SYN-ACK and the dotted expected leg."
    },
    {
      "from": "agent-work/review-the-change",
      "to": "agent-work/resume-from-a-checkpoint",
      "relation": "next-step",
      "reason": "Use the accepted revision and image hashes as the starting point for another worker."
    },
    {
      "from": "fpv/field-kit",
      "to": "fpv/remote-id",
      "relation": "shared-concepts",
      "concepts": [
        "remote-id",
        "tanq-2"
      ],
      "reason": "Both discuss remote id, tanq 2."
    },
    {
      "from": "fpv/height-over-terrain",
      "to": "data/terrain-clearance",
      "relation": "derived-from",
      "reason": "Subtract terrain elevation from aircraft elevation at the same position. Compare the result with the ceiling in feet above ground level.",
      "source_sha256": "639271aa0d77c50c69ef66d5a7efd4704043637bcb06688a959978a5b3c5e5b7"
    },
    {
      "from": "fpv/pack-energy",
      "to": "data/pack-energy",
      "relation": "derived-from",
      "reason": "Multiply nominal volts by amp-hours per pack and count. Divide the printed milliamp-hours by 1,000 to obtain amp-hours. The result is nameplate energy in watt-hours.",
      "source_sha256": "84f493d660220ad2a5d48a167e51682344bd134724fee113d63c3aeb5593304e"
    }
  ]
}
