City / Regional Low-Altitude Airspace Network

Data status: Illustrative

City airspace is cluttered, dense and divided among many jurisdictions. Every local picture is incomplete, and each handoff between them is a place where a track can be dropped or invented. Showing how crowded the sky is, as if that were how risky it is, makes the picture look more informative than it is.

• Site-level statesThe airspace state that each local node or site already holds, with its own confidence and freshness. No city, district or operator is named here.
• Handoff cellsThe abstract cells into which a region is divided, and the boundaries between them where continuity has to be carried.
• CoverageWhere observation is thick and where it is thin, because coverage across a city is never uniform.

1. Links the site-level states of distributed nodes into one regional picture.
2. Carries continuity across handoff cells as an explicit hypothesis, drawn dotted and labelled as one.
3. Shows density without turning it into a risk rating.

• Density is not risk: the picture shows how crowded a cell is and attaches no risk label.
• Non-uniform coverage is displayed honestly, not smoothed over.
• Continuity across a boundary is a hypothesis and never styled as observed.
• Regional sharing is governed: what one site shares with another is a decision, not a default.

The regional picture is an application of the core platform. It takes the states of many sites, carries continuity across the boundaries between them as a labelled hypothesis and shares the result under governance. It adds no sensing, and it makes no judgement about risk.

Read the architecture

Evidence ladder

1. E0 · Concept reached
2. E1 not reached
3. E2 not reached
4. E3 not reached
5. E4 not reached
6. E5 not reached

Project assurance panel

Mission and context

Give a city or region a low-altitude picture assembled from local observations that were never complete on their own, without hiding where it is thin.

Primary contribution

A regional state that links site-level states, carries continuity across handoffs as a hypothesis and shows density with no risk label.

Decision value

Lets a reviewer see where the regional picture rests on observation, where it rests on a hypothesis across a boundary and how thin coverage is.

Evidence status

Evidence level: E0 · Concept Concept and research direction only. No specification, prototype, test result or deployment is claimed.

Next validation step

Write down how continuity is carried across a handoff and how density is shown, then specify a first review of a synthetic district before any claim is made.

Behaviour when degraded

When a site stops reporting, its cell is marked as unsupported and the continuity across its boundaries is dropped to a hypothesis or removed. The picture says so and does not fill the gap.

Role in integration

Would take site-level states from the core platform and distributed nodes, and share regional views through the data API under governance. It does not feed enforcement systems.

Human review

A person reviews every handoff that carries continuity as a hypothesis, and every decision to share a regional view with another party.

Public-safe limitation

No city, district, operator, corridor or route is described. The ribbon on this page uses five invented cells.

Open unknowns

How cells should be drawn for a real city, how long a hypothesis can be carried across a handoff and how sharing should be governed are not yet known.

When a site stops reporting, its cell is marked as unsupported and the continuity across its boundaries is dropped to a hypothesis or removed. The picture says so and does not fill the gap.

• A city that wants one low-altitude picture across districts

  Why it matters here

  Each district sees part of the sky, and the seams between them are where the picture breaks.

  What it contributes

  A regional state in which the seams are visible and labelled.

  What it does not replace

  The authorities responsible for each district, or any enforcement function.

• A region that shares a view between operators

  Why it matters here

  Sharing without governance exposes more than the parties meant to share.

  What it contributes

  A regional view whose sharing is a recorded decision.

  What it does not replace

  Agreements between the parties.

Would take site-level states from the core platform and distributed nodes, and share regional views through the data API under governance. It does not feed enforcement systems.

Write down how continuity is carried across a handoff and how density is shown, then specify a first review of a synthetic district before any claim is made.

• This is a concept. There is no specification, prototype or measured result behind it.
• The ribbon uses five invented cells and an invented object. It shows how continuity and density are kept apart, not how a city behaves.
• A density setting is not a measure of danger. The page assigns no risk rating to any cell.
• A hypothesis carried across a handoff can be wrong. It is shown as one for that reason.

• Near-Ground Airspace Intelligence NetworkEvidence level: E0

  Near-ground airspace intelligence handles the occlusion that breaks views inside a city.

• Distributed Passive Radar NetworkEvidence level: E0

  A distributed passive network supplies the local observations that the regional picture links.

• Drone Detection & Airspace Intrusion IntelligenceEvidence level: E0

  Low-altitude detection supplies the events whose handoffs are carried across cells.

• Airspace Data & Intelligence APIEvidence level: E0

  The data API is how a regional view would be shared under governance.

• Airspace Intelligence Core PlatformEvidence level: E1

  The core platform holds the site-level states, the history and the replay.