Critical Infrastructure Airspace Protection

Data status: Illustrative

A perimeter system tells you that something happened. It does not tell you how long it has been watching, how fresh each source is, or which hours nobody was looking. For a site that cannot rely on assumptions, the gaps matter as much as the events, and they are the part that stays invisible.

• Independent sources around the siteWhat each source contributes over time, around a generalised asset. No perimeter, distance or layout is published here.
• FreshnessHow recently each source reported, so that a stale view is told from a current one.
• Unknown periodsThe hours in which no source could support a statement, recorded as unknown and not as quiet.

1. Combines independent sources around a generalised asset.
2. Keeps a continuity log, hour by hour, with freshness and with unknown periods kept as their own state.
3. Provides replay and a review log, so that a shift can hand over what was seen and what was not.

• Unknown hours are shown as unknown, never as a calm period.
• No geometry and no distances: the asset is a glyph.
• A review log takes the place of an alarm.
• Awareness only: no defeat, no response, no tasking.

Critical infrastructure protection is an application of the core platform. It takes the unified airspace state around a site, keeps a continuity record of it and turns it into something a shift can review and hand over. It adds no sensing of its own and takes no action.

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 the operators of a site that cannot rely on assumptions a persistent, reviewable account of the airspace around it, including what was not known.

Primary contribution

A continuity log with freshness and explicit unknown periods, replay of events and a review log for handover.

Decision value

Lets a reviewer see not only what was observed but when nobody could have observed anything, and how current each source was.

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, freshness and unknown periods are recorded, then specify a first review of a synthetic day before any claim is made.

Behaviour when degraded

When a source goes quiet, the hours it covered alone are recorded as unknown and not as clear. A shift can read as complete only when none of its hours is degraded or unknown.

Role in integration

Would take the unified state from the core platform and the fusion engine, and send review records to the people on shift. It does not control any equipment.

Human review

A person reviews every shift log and every event that rests on a degraded or unknown period, and signs the handover.

Public-safe limitation

No site, perimeter, distance, sensor or response procedure is described. The ring on this page uses invented days.

Open unknowns

How unknown periods should be defined, how much freshness a source must show to count and how reviews should be organised across shifts are not yet known.

When a source goes quiet, the hours it covered alone are recorded as unknown and not as clear. A shift can read as complete only when none of its hours is degraded or unknown.

• A site where a gap in awareness is itself a risk

  Why it matters here

  A quiet log can mean a calm sky or a blind sensor, and the two look the same.

  What it contributes

  A record in which an unknown hour is visible as unknown.

  What it does not replace

  Physical security, or the people responsible for the site.

• Shift handover

  Why it matters here

  What the last shift did not know is the most useful thing to tell the next one.

  What it contributes

  A review log that lists complete, partial and unknown periods.

  What it does not replace

  A conversation between the people on duty.

Would take the unified state from the core platform and the fusion engine, and send review records to the people on shift. It does not control any equipment.

Write down how continuity, freshness and unknown periods are recorded, then specify a first review of a synthetic day before any claim is made.

• This is a concept. There is no specification, prototype or measured result behind it.
• The ring uses invented days. It shows how unknown periods are kept apart, not how any site behaved.
• Awareness is not protection. Nothing here prevents, stops or answers an event.
• A complete shift means that every hour had support from sources. It does not mean that nothing happened.

• Drone Detection & Airspace Intrusion IntelligenceEvidence level: E0

  Low-altitude detection supplies the events that the continuity log places in time.

• Near-Ground Airspace Intelligence NetworkEvidence level: E0

  Near-ground airspace intelligence addresses the occlusion that sites among structures and terrain face.

• Multi-Sensor Fusion EngineEvidence level: E0

  Fusion supplies the unified state whose continuity is recorded.

• Distributed Passive Radar NetworkEvidence level: E0

  A distributed passive network is one way for a site to keep several independent sources.

• Airspace Intelligence Core PlatformEvidence level: E1

  The core platform holds the state, the history and the replay that the review log draws on.