Project · Protected Environments
Drone Detection & Airspace Intrusion Intelligence
Detect activity. Build context. Preserve the evidence behind the airspace state.
Evidence levelE0Concept
Event evidence ladder
Interactive view
Data status: Illustrative
One invented event. Add evidence and it climbs: observation, candidate, correlated, classified hypothesis. Remove a lower item and everything above it falls back. Switch on context chips and watch the rung stay where it is.
- ObservationSomething was seen by one source.Reached
- CandidateThe trace persists and is worth following.Not reached
- CorrelatedIndependent sources agree about it.Not reached
- Classified hypothesisA class is proposed, with a band, and remains open to review.Not reached
Where the event stands
Observation
Confidence band: 15–45
The event and the bands are invented. The top rung is a hypothesis and never a confirmation.
Why this exists
A single-sensor alert runs two different claims together: something is there, and it is a drone with an intent. The first can be seen. The second cannot be read from one trace, and a system that blurs them makes every unidentified object look like a decision waiting to be taken.
What it takes in
Each input adds something and leaves something unproven.
- Observations from independent sourcesRadio-frequency, passive spatial and optical traces of low-altitude activity, each with its own quality. No sensor or site is described here.
- Persistence and timingHow long an event lasts, when it occurs and whether it recurs, kept as context and not as a verdict.
- Gaps in coverageWhere no source could have seen, so that an absence of evidence is not read as evidence of absence.
How it works
Three steps, in the order the state is formed.
- Climbs one event up a ladder: observation, candidate, correlated, classified hypothesis.
- Attaches intrusion-context chips for persistence, timing and repetition, which describe the event and never move it up the ladder.
- Keeps an evidence record and a replay for every event, with the confidence band of each rung.
- Unidentified is not a verdict: the top rung is a hypothesis with a band.
- Context describes an event and does not promote it.
- No response workflow, and no numeric trigger anywhere in the page.
- Every event can be reopened with the evidence that put it on its rung.
Where it sits in the architecture
Low-altitude detection is an application of the core platform. It takes correlated observations from the fusion engine, places each event on an evidence ladder and keeps the record and replay behind it. It is awareness for review and not an instrument of response.
| Stage | Value |
|---|---|
| 1 | Sources |
| 2 | Model |
| 3 | Policy |
| 4 | Interface |
| 5 | Consumer |
| 6 | Audit |
Evidence and assurance
What has been shown, to which level, and what has not.
Evidence ladder
- E0 · Concept reached
- E1 not reached
- E2 not reached
- E3 not reached
- E4 not reached
- E5 not reached
Project assurance panel
- Mission and context
- Keep detection, classification and intrusion context honestly apart for activity in the low-altitude airspace.
- Primary contribution
- Events on a four-rung evidence ladder with a confidence band at each rung, context chips that describe without promoting, and an evidence record with replay.
- Decision value
- Lets a reviewer see what an event rests on and what it does not, and prevents a persistent trace from being read as intent.
- 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 the four rungs and the evidence each one requires, then specify a first review of synthetic events before any claim is made.
- Behaviour when degraded
- When a source drops out, the events that depended on it fall back to the highest rung that the remaining evidence supports, and the record says why. The chips stay, because they describe the event, but they do not hold it up.
- Role in integration
- Would take correlated observations from the fusion engine and context from the core platform, and send evidence records to the people reviewing. It triggers nothing.
- Human review
- A person reviews every event at the classified-hypothesis rung and decides what, if anything, follows. The system does not recommend a response.
- Public-safe limitation
- No sensor, site, procedure or numeric trigger is described. The ladder on this page uses an invented event.
- Open unknowns
- What evidence each rung should require, how context chips should be presented without suggesting intent and how events should be reviewed are not yet known.
When inputs degrade
When a source drops out, the events that depended on it fall back to the highest rung that the remaining evidence supports, and the record says why. The chips stay, because they describe the event, but they do not hold it up.
- Normal
- Degraded
- Unavailable
| Time (relative) | Component 1 | Component 2 | Component 3 |
|---|---|---|---|
| 1 | Normal | Normal | Normal |
| 2 | Normal | Normal | Normal |
| 3 | Normal | Normal | Normal |
| 4 | Normal | Normal | Unavailable |
| 5 | Normal | Normal | Unavailable |
| 6 | Normal | Degraded | Normal |
| 7 | Normal | Degraded | Normal |
| 8 | Degraded | Normal | Normal |
| 9 | Degraded | Normal | Degraded |
| 10 | Normal | Normal | Normal |
| 11 | Normal | Normal | Normal |
| 12 | Normal | Normal | Normal |
Where it applies
A site that sees unexplained low-altitude activity
- Why it matters here
- A sighting is not an explanation, and acting on it as if it were is a decision made without evidence.
- What it contributes
- A ladder that shows how far the evidence has got.
- What it does not replace
- The people who decide what to do, or the authorities responsible for the airspace.
A review after an event
- Why it matters here
- What was known at each moment matters more afterwards than the final label.
- What it contributes
- An evidence record and a replay in which each rung is dated.
- What it does not replace
- An investigation.
Role in the data flow
Would take correlated observations from the fusion engine and context from the core platform, and send evidence records to the people reviewing. It triggers nothing.
Validation path
Write down the four rungs and the evidence each one requires, then specify a first review of synthetic events before any claim is made.
| Item | Defined | Prototype | Integrated | Field |
|---|---|---|---|---|
| Module A | Done | In progress | Not started | Not started |
| Module B | Done | Not started | Not started | Not started |
| Module C | In progress | Not started | Not started | Not started |
Limitations
- This is a concept. There is no specification, prototype or measured result behind it.
- The ladder uses one invented event and invented bands. It shows how evidence is kept apart from context, not how a system performs.
- A classified hypothesis is not an identification. Its band is wide on purpose.
- The page describes awareness. It describes no countermeasure, response procedure or enforcement.
Related projects
Each link says why the two belong together.
Capabilities
Solutions
Technology
A continuity record, or an evidence ladder
Two ways of keeping awareness open to review.
| Aspect | Critical Infrastructure Airspace Protection | Drone Detection & Airspace Intrusion Intelligence |
|---|---|---|
| What it keeps | A record of each hour, as continuous, degraded or unknown. | A record of each event, showing how far its evidence has climbed. |
| What it refuses | To treat an unknown hour as a calm one. | To treat context as if it were evidence. |
| Who reads it | The shift that hands over and the shift that takes over. | The reviewer who decides what, if anything, follows an event. |