elvone · counter-UAS · neuriya.ai
One brain.
Thirteen situations.
One evidence file.
The storyline, and thirteen ways to tell it. Same architecture on every page — only the lit components change. That repetition is the argument.
00 · Reading guide
What this document is, and the four things it will not do
A companion to the 52-page deck, not a replacement. The deck argues the business in diligence order; this argues the product in the customer’s order.
Illustrative
Every scenario is design intent. None has been run at a customer site. Where a scenario depends on an untested claim, the page says which claim and which gate closes it.
Conditioned
No detection figure appears without target size, range and clutter class — or it is marked a target with a date. “~1–2 km against a 0.35 m class, sky background, to be measured.”
Bracketed & hypothesised
[ ] is a fact only the founders can supply. H: is a hypothesis a named test retires. All pricing is H: until two pilot quotes are accepted.
Bounded
The commercial product never fires, jams, cues an effector or acts autonomously. No satellite detects a small drone in flight. Both hold on every scenario page.
Gate status today
0 of 11 maturity gates passed. The artefacts exist; the evidence does not yet. The gate board in the full deck says which named test closes each gate, and by when. Judge the evidence plan and its dates, not the polish.
concepts/scenario-playbook.md §1; concepts/product-thesis-v3.md §9 (gates) and §3 (claims T1–T14 with status).
02
00 · The spine
Five acts. A scenario drops into Act IV; nothing else changes.
The rhetorical move this document exists to make: after the third scenario the room stops asking “does it handle my case” and starts asking “what does the posture cost”.
I
The seconds
On 2 March 2026 the Kingdom’s largest refinery had cameras, some radar, and no picture.
Ras Tanura 2 Mar 2026; Eastern Province intercepts 18 Mar 2026 — public record
II
The four failures
The gap is not a shortage of sensors. It is separate screens, bird-or-threat, no evidence trail, and capital-project pace.
investor-pack/01-pressure-test.md
III
The physics
A 0.35 m quadcopter is about 1.5 px at 1.5 km on a 50 mm LWIR lens. The cameras a site owns cannot see it — and fibre-optic airframes emit nothing for an RF stack to hear.
Claim T3, validated on physics; NATO fibre-optic FPV challenge, Apr 2025
IV
Your situation
Connect → Fuse → Classify → Respond. Then thirteen situations, thirteen configurations, one system.
This document, the scenario pages
V
The same file
Whatever lit up, the operator sees one ranked list and the review gets one replayable case file.
The gate board; the ask
So what
Acts I–III are fixed and take six minutes. Act IV is the variable, and it is chosen for the person in the room — a site manager gets S1 and S2; a defence expert gets S6 and S9. Act V is the same in every telling.
concepts/scenario-playbook.md §2, §7 (routes by audience).
03
01 · Acts I–II
Not a shortage of sensors: four failures between a blip and a decision
Ras Tanura, 2 March 2026 — drones intercepted, debris fire, propane and butane exports halted for weeks. The site was not sensor-poor.
Failure 1
Separate screens
CCTV, radar, RF detectors and access control each on their own console with no shared picture. The operator integrates them in their head, at 04:00.
Failure 2
Bird or threat
An operator watching separate feeds cannot reliably separate a bird, a hobby drone, a friendly aircraft and an incoming threat in the seconds that matter.
Failure 3
No evidence trail
Afterwards there is no replayable record of what was seen, what was decided and why. The HCIS review becomes a reconstruction.
Failure 4
Capital-project pace
Incumbents sell a proprietary stack at national-programme prices on a multi-year procurement. Sites need an opex-line answer this year.
So what
The value is the seconds saved and the decision proven. The product must classify before it alerts, and record everything it saw — including what it chose not to alert on.
investor-pack/01-pressure-test.md; concepts/product-thesis-v3.md §2. Claim T1 is tested by 10 structured interviews, target week 4 (gate G1).
04
01 · Act III
The physics that removes the easy answer
Three facts kill “just use the cameras you already have” and “just listen for the radio link”, and set the number of nodes. All three are why the product is sensor-agnostic and not sensor-free.
Fact one · resolution
1.5 px
is what a 0.35 m quadcopter occupies at 1.5 km on a 50 mm long-wave infrared lens, 12 µm pitch, sky background. A fence-line CCTV camera, pointed at the ground with a wider lens, sees less than that.
So “fuse what you have” is necessary and not sufficient. Every deployment needs a cheap cue sensor for the air — which is why the RF cue kit, ~US$520 BOM, deploys before anything else.
Fact two · emission
0 W
is what a fibre-optic or autonomous waypoint airframe radiates. No Remote ID, no control link, no video downlink. Every RF-based product — incumbents included — is blind to this class by construction, not by configuration.
NATO ran a fibre-optic FPV detection challenge at only 300–500 m in April 2025. RF-silent is the new baseline, and it is the reason a passive layer is not optional.
Fact three · geometry
3 nodes
Two bearing-only sensors and N targets produce N² ghost intersections. A third bearing rejects them. Separated viewpoints resolving what one viewpoint cannot is literally the physics the product is named for.
Altitude is the weakest axis of a ground triangle — which is the entire reason the tethered sky cube exists, and why it is an evaluation and not a claim.
The conclusion the three facts force
Start with the sensors the site has; add only what the threat demands. Never “no hardware needed” — and never “not another sensor to buy”. Sensor-agnostic, not sensor-free. The cheapest sensor the threat demands is always part of the offer, and the number of nodes is set by geometry, not by a price list.
Claim T3, validated on physics. Pixel figure: 0.35 m at 1.5 km, 50 mm LWIR lens, 12 µm pitch, sky background. NATO fibre-optic FPV challenge, Apr 2025; concepts/sense-cubes.md §2 rule 4; investor-pack/05-market-sizing.md §4.
05
01 · Act III
National air defence is built for missiles; site security for the fence line
Small drones live in the layer between. That layer is the seed business; the doctrine that fills it is the roadmap.
| Threat class | Spec | Who answers today | elvone |
|---|
| Group 1–2 small UAS | 0.2–2 m · up to 25 kg · quadcopters, FPV, fibre-optic, autonomous waypoint | Site security: separate screens, human judgement, a phone call to the authorities | Seed scope. The scenario library lives here |
| Group 3 and loitering munitions | 3–4 m span · Shahed-class · hundreds of km | National IAMD radars and interceptors; sites get no cue | Publishes tracks into IAMD; the layered doctrine adds early warning later (S9) |
| Cruise and ballistic missiles | — | National air defence | Out of scope, by design |
So what
Ras Tanura was not a quadcopter over the fence, and it was not a missile either. The site layer is the business we are raising for; the layer between is the reason the business has a second act.
investor-pack/13-technical-diligence-pack.md §1 (scope); concepts/layered-sensing-doctrine.md §1–2.
06
02 · Act IV
Connect, fuse, classify, respond — and then the same four steps, thirteen times
The architecture never changes. What changes is which components are lit, which posture is running, and who approves.
01
Connect
Existing CCTV, radar and RF detectors connect once over open standards — SAPIENT (BSI Flex 335), ASTERIX CAT-129/240, ONVIF, Remote ID — or vendor adapters. Nothing is replaced. Sensing cubes fill the gaps.
02
Fuse
Every source becomes a stream of timestamped detections with an explicit latency estimate and covariance. Core aligns, associates and merges into one 3D track per object.
03
Classify
Each track is scored bird / commercial / friendly / suspicious / hostile, with calibrated confidence and the features that drove it. No online learning; models frozen in the field.
04
Respond
Confirmed threats route to the site’s emergency procedures with a replayable evidence pack. Every decision is logged for the after-action review.
Is
A fusion and classification brain · an evidence and bit-exact replay system · an operator console in Arabic and English, on-prem or air-gapped · an open-standards integration layer · a family of sensing cubes on one spine · an optional regional imagery layer for launch-site cues
Is not
An effector, a jammer or a targeting system · a cloud service · a general video-analytics platform · a single proprietary sensor · an autonomous engagement system · a satellite that detects drones in flight (no satellite does)
The situations that follow · the seed sells S1, S2, S3, S8 and the limits in S10–S12; the rest show the reach
S1
Dawn on the fence line
the drone that says nothing
P1 · Eastern Province refinery
p 10
S2
The bird that wasn’t
the alarm nobody had to answer
P0 · Coastal desalination plant
p 11
S3
The contractor’s survey drone
cleared in eight seconds
P0 · Petrochemical complex
p 12
S4
Match night
posture up on Thursday, down on Sunday
P2→P3 · Stadium / giga-project venue
p 13
S5
The camp sixty kilometres out
evidence before the flight
P2 · Eastern Province site cluster
p 14
S6
Runway 34L
the clutter problem changes, the brain does not
P1 · GACA / Matarat airport
p 15
S7
Three hundred kilometres of pipeline
the asset that has no fence
P3 · Pipeline / power-line corridor
p 16
S8
Eleven sites, one shift
the estate view
P0–P2 · Multi-site operator: Aramco affiliate
p 17
S9
Through a prime
where the commercial product stops
P4 · Defence or border installation
p 18
S10
Shamal
the day the cubes go half-blind
P1 · Petrochemical complex
p 19
S11
14:40
the twenty minutes the thermal cube cannot see
P1 · Eastern Province refinery
p 20
S12
The wadi
below the horizon, against a hot ground background
P1 → P2 · Inland site cluster
p 21
S13
Listening to what is already in the air
passive radar — research only, not in the seed
— · Eastern Province refinery (as a worked example)
p 22
concepts/product-thesis-v3.md §4. Commercial sites have a legal, useful respond step without an effector — claim T10, validated on regulation. Scenarios are illustrative design intent.
07
02 · Act IV · the mechanism
Two dials produce every configuration in this document
A customer does not buy a sensor list. They buy a posture, and the platform recommends when to raise or lower it. Layers are added or surged as the posture changes; Core, the console and the evidence file never change.
Dial one · the layer ladder
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
Seed reaches the bottom two rungs, plus tasked imagery. The rest are evaluations and roadmap — drawn dim on every scenario page rather than hidden, so the scope is always legible.
Dial two · the posture ladder
P0
Monitor
Legacy + RF cubes + Core
SAR 450k/yr SEED
P1
Detect
+ thermal/optical ground triangle
SAR 900k/yr + cubes SEED
P2
Aware
+ imagery ring + acoustic/radar cubes
SAR 1.8M/yr + add-ons SEED
P3
Overwatch
+ tethered aerostat + patrol on call
Large tier + surge SERIES A
P4
National
+ stratospheric feed + IAMD publication
Programme, via a prime VISION
Escalation is decision support, not automation. The platform recommends from threat intelligence, detected activity, calendar and incident; the customer approves; every change is logged. HCIS already grades facilities by criticality — postures speak that language.
And a third thing the dials produce for free · cueing chains, or how the layers talk to each other
Regional cue → patrol → ground
Change detection flags new activity at a staging area 60 km out. A patrol sortie confirms vehicles and a pad. The cluster posture is raised; ground cubes tighten thresholds on the approach bearing.
S5
Ground → sky → responder
A ground triangle initiates at 1.5 km on two-node coincidence. The aerostat radar confirms range and altitude, converting a bearing-only track into a firm 3D track in under two seconds.
S4
Stratosphere → national
A thermal cue on a Shahed-class object 120 km out is published over ASTERIX CAT-129 to the national IAMD and to every site cluster on its predicted track. Sites raise posture pending approval.
S9
Patrol → corridor evidence
A scheduled pipeline patrol records RF emitters and EO/IR anomalies along 300 km. Nothing alerts — but the pattern-of-life dataset grows and the next sortie is prioritised by anomaly.
S7
concepts/layered-sensing-doctrine.md §2, §3, §4 (D-16); DECISIONS.md D-09 pricing, D-15, D-17. H: tier prices are hypotheses until two pilot quotes are accepted (gate G6).
08
02 · Act IV · the vocabulary
The fixed cast of every scenario
Unengaged components are shown greyed on every scenario page, never hidden. You can always see what is not being used.
| Component | What it is | Revenue line | Maturity today |
|---|
| Core | Fusion, classification, evidence, bit-exact replay, bilingual console, on-prem or air-gapped | Site subscription by posture | TRL 2–3 · fusion MVP on real feeds is gate G2, week 6 |
| Cue · RF | RF cube: Remote ID decode, 2.4/5.8 GHz link detection, optional direction-finding | SAR 15k/node incl. support (BOM ~US$520) | TRL 4 · buy-and-integrate, weeks |
| Sense · thermal | 3× uncooled LWIR 640×512 staring, 90° sector, CFRP mount, no motors | Hardware + support | TRL 3 · detailed design and BOM; Phase 0 bench pending (G4) |
| Sense · optical | 4K global-shutter visible/NIR staring; optional event camera | Hardware + support | TRL 3 · shares the thermal pipeline |
| Sense · acoustic | 8–16 element microphone array; beamforming, rotor harmonics | Hardware + support | TRL 2 · one array trialled in the environmental campaign |
| Sense · radar | COTS FMCW 24/60/77 GHz or Ku micro-radar. Emits — CST approval needed | Hardware + support | TRL 2 · two modules evaluated M7–M18 |
| Fleet | Multi-site command view; cross-site correlation; estate posture | Fleet console, usage-based | Alpha M12 · GA M15 |
| Sky | Tethered aerostat sky cube, 300–1,000 m. The vertical baseline a ground triangle lacks | Surge, per month | Evaluation months 9–18 (D-15) |
| Patrol | EO/IR + RF DF payload on a partner GACA-licensed airframe. We build the payload, not the aircraft | Surge, per sortie | Series A feasibility (D-17) · no flights in the seed |
| Orbit | Tasked commercial imagery; change detection over a ring. Regional cues, never detections | Add-on, per tasking | H1 in the seed (D-15) · sourced via Neo Space Group / UP42 |
| Defence | Separately licensed variant with effector hand-off to the customer’s C2. No autonomous engagement | SAR 3–6M/site/yr via a GAMI-licensed prime | Series A · GAMI licence applied M3 |
| Legacy sensors | The site’s own CCTV, radar and RF detectors, ingested with an estimated latency | No licence — free coverage | Adapters + open standards |
Two rules that hold on every scenario page
No satellite detects a small drone in flight. · The commercial product recommends and records — it never fires, jams or acts autonomously. Confirmed threats go to the site’s authorised responder. Effector hand-off exists only in the GAMI-licensed defence variant.
concepts/sense-cubes.md §3; concepts/layered-sensing-doctrine.md §2; investor-pack/13-technical-diligence-pack.md §4, §8. Costs indicative; every range carries its conditions or is marked to be measured.
09
S1
Dawn on the fence line — the drone that says nothing
Site Eastern Province refinery, HCIS-regulatedBuyer Industrial Security manager
A fibre-optic FPV airframe crosses the perimeter at first light. It transmits nothing — no Remote ID, no control link, no video downlink. Every RF-based product on the market, incumbents included, is blind to it by construction.
T−00:40
Nothing on RF. The Cue nodes are silent — and their silence is itself recorded.
Cue · RF
T+00:00
Two thermal nodes of the ground triangle initiate on a sub-pixel-class track against sky background. Neither would alert alone.
Sense · thermal
T+00:03
Heterogeneous coincidence: the optical cube agrees in bearing and time. Different physics, same object.
Sense · optical
T+00:06
Core resolves bearings into a 3D track and scores it — hover fraction, turn-rate against speed, no wingbeat band.
Core
T+00:11
Ranked first on the triage board, with calibrated confidence and the features that drove it.
Core
T+00:35
Operator confirms; case file opens; hand-off to the site’s authorised responder under the existing emergency procedure.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
One ranked line, not four consoles.
What the evidence file holds
Every contributing detection, the confidence tier by sensor mix, the operator’s decision and its timestamp — bit-exact replayable for the HCIS SEC-05/06 review.
What it is sold as
P1 Detect — SAR 900k/yr + cubes (H).
What is unproven here
The thermal cube’s Pd against a 0.35 m class target at 1–2 km, sky background, is a design target with an error budget that closes only with a CFRP mount. Phase 0 bench, gate G4, week 8.
10
S2
The bird that wasn’t — the alarm nobody had to answer
Site Coastal desalination plant, heavy gull trafficBuyer Industrial Security manager
The expensive failure at a coastal site is not a missed drone. It is forty alarms a night until the shift stops looking. This is the system’s most-used function: deciding not to alert, and proving it decided.
T+00:00
A legacy site radar returns a track. On its own console, this is an alarm.
Legacy sensors
T+00:01
Core ingests it with an estimated latency for that feed — shown to the operator rather than hidden.
Core
T+00:02
The thermal node’s wingbeat-spectrum test finds energy in the 2–15 Hz band.
Sense · thermal
T+00:02
No RF link, no Remote ID — consistent with a bird, not exculpatory on its own.
Cue · RF
T+00:04
Classified bird, calibrated confidence, below alert threshold. No siren. Logged.
Core
overnight
Every single-cube detection no other cube confirms is mined as a hard negative — dust devils, shimmer, thermal artefacts — at zero labelling cost.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A quiet board — and a suppression log they can audit.
What the evidence file holds
The non-alert is recorded as fully as an alert. “Why did nothing happen at 02:14” is an answerable question.
What it is sold as
P0 Monitor — SAR 450k/yr (H).
What is unproven here
Claim T7 — that heterogeneous coincidence lowers false alarms enough to run each cube at aggressive thresholds. The theory is sound (accidental coincidences ≈ f²·Δt·g); the three-node campaign measures FA/hour by class.
11
S3
The contractor’s survey drone — cleared in eight seconds
Site Petrochemical complex, JubailBuyer Industrial Security manager
Most airspace events at an industrial site are not attacks. They are a contractor’s survey flight, a neighbour’s hobbyist, a media crew. Treating every one as an incident is how a security team loses its own budget.
T+00:00
RF cube decodes Remote ID: serial, position, and operator position.
Cue · RF
T+00:02
Serial matches the whitelist entry raised for this week’s tank survey.
Core
T+00:04
Track is drawn on the console as authorised, with the work-order reference attached.
Core
T+00:08
No alert. The flight is logged, geofence adherence is checked against the permit, and the operator is located on the site map.
Core
—
Free ground truth: a compliant aircraft near a site is a timestamped, position-labelled training example, at no cost. This is why the RF cube deploys before any other hardware.
Cue · RF
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
Airspace administration, not an incident queue.
What the evidence file holds
A permit-compliance record — useful in its own right at an HCIS review.
What it is sold as
Included in P0. The reason the RF cube (BOM ~US$520) ships first.
What is unproven here
Nothing physical. The dependency is commercial — claim T2, that a site pays an opex-sized subscription for this. Two accepted pilot quotes, gate G6.
12
S4
Match night — posture up on Thursday, down on Sunday
Site Stadium / giga-project venueBuyer Event security lead, via the operator
P2→P3
Aware → Overwatch
P2 SEED · P3 SERIES A
The agility scenario. A venue does not need P3 for 360 days a year; it needs it for five. The platform recommends the escalation from calendar, threat intelligence and detected activity — and the customer approves it. Escalation is decision support, not automation.
D−14
Posture panel recommends escalation: calendar event, MoI advisory, and a rise in unresolved RF detections in the ring. Customer approves. Logged.
Core
D−10
Imagery ring tasked at higher revisit over the approach sectors; change detection flags a new hardstand — a regional cue, never a detection.
Orbit
D−03
Tethered sky cube inflated over the venue cluster. Altitude is the weakest axis of a ground triangle; a node several hundred metres up fixes it.
Sky
D−00
Ground triangle thresholds tightened; acoustic cubes added for approaches masked by the stands.
Sense · thermalSense · opticalSense · acoustic
T+00:00
A track initiates on the ground triangle; the sky cube’s radar confirms range and altitude, turning a bearing-only track into a firm 3D track in under two seconds.
SkyCore
D+02
Posture returns to P2. The aerostat goes home. The subscription does not change.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
The same console, with more sources contributing and the confidence tiers moving up accordingly.
What the evidence file holds
The posture change, the evidence behind it, and the named human who approved it.
What it is sold as
Large tier + add-ons, plus surge: aerostat per month, patrol per sortie, imagery per tasking.
What is unproven here
The whole surge line is Series A. The seed commits to one aerostat evaluation, months 9–18, and a patrol-cube feasibility note with a licensed operator — no flights.
13
S5
The camp sixty kilometres out — evidence before the flight
Site Eastern Province site clusterBuyer SOC lead, multi-site operator
P2
Aware
P2 SEED (imagery add-on) · PATROL SERIES A
The cueing chain. Every other scenario starts after something is already in the air. This one starts six days earlier — and it is the clearest illustration of why the layers are worth more together than apart.
D−06
Change detection over the configurable ring flags new activity ~60 km out: vehicles, a cleared pad, a persistent thermal anomaly. Surfaced as a regional cue — it cannot enter track fusion or pollute the false-alarm accounting.
Orbit
D−04
A patrol sortie is scheduled with a GACA-licensed partner operator. The aircraft broadcasts its own Remote ID and is whitelisted in Core as a friendly track.
Patrol
D−04
EO/IR and RF DF from 300–1,500 m AGL confirm vehicles and a pad; RF geolocation over tens of kilometres from altitude.
Patrol
D−03
Cluster posture raised on the evidence. Customer approves. Ground cubes tighten thresholds on the approach bearing.
Core
D+00
If something flies, the ground triangle is already looking the right way — with a prior.
Sense · thermalSense · opticalCore
—
The cue outcome — did the launch-site cue precede a track? — is supervised signal for the recommendation engine.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A map ring with cues — distinct in colour and in kind from tracks.
What the evidence file holds
The cue, the sortie, the posture decision and the outcome: the chain a post-incident review actually wants.
What it is sold as
Imagery add-on (P2); patrol per sortie (P3).
What is unproven here
Everything about the patrol layer sits behind GACA BVLOS and restricted-zone approvals plus MoI concurrence, routed through a licensed operator. We build the payload and the integration, not the aircraft.
14
S6
Runway 34L — the clutter problem changes, the brain does not
Site GACA / Matarat airportBuyer Airport security, coordinating with ATC
P1
Detect + radar cube
FAST FOLLOW
An airport is a different physics problem wearing the same clothes: dense bird traffic, dense legitimate air traffic, and a consequence of error measured in flight delays. The cube mix changes. Core does not.
T+00:00
The radar cube returns range and radial velocity directly — the two things a bearing-only triangle lacks.
Sense · radar
T+00:01
Rotor micro-Doppler is the strongest bird/drone separator available; the thermal wingbeat test runs in parallel, on different physics.
Sense · radarSense · thermal
T+00:03
Cross-checked against Remote ID and the whitelist for authorised airfield operations.
Cue · RFCore
T+00:05
Classified, and published to the airport’s own systems over ASTERIX CAT-129/240 — an open standard, no vendor permission required.
Core
T+00:20
Hand-off to the authorised responder and to ATC under the airport’s own procedure. elvone does not close a runway; it gives the person who does a defensible picture.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
The same triage board, with radar-derived range on the track.
What the evidence file holds
The ASTERIX publication is itself part of the record.
What it is sold as
P1 plus radar cubes. 27 airports sit in the bottom-up sizing.
What is unproven here
The radar cube emits, so it needs CST spectrum approval — a parallel workstream, not a technical risk. Cheap modules give 0.5–1.5 km and carry ground clutter. Two modules evaluated M7–M18; the cube passes its gate or it is retired, and nothing else depends on it.
15
S7
Three hundred kilometres of pipeline — the asset that has no fence
Site Pipeline / power-line corridorBuyer Asset protection, via the operator’s SOC
Fixed cubes are priced per site. A linear asset has no site. This scenario answers the question every energy operator asks about ten minutes in — and is honest that the answer is a roadmap item, not a product.
—
A scheduled sortie flies the corridor, recording RF emitters and EO/IR anomalies along 300 km. Nothing alerts.
Patrol
—
The pattern-of-life dataset grows; the next sortie is prioritised by anomaly rather than by schedule.
Core
—
Where the corridor passes a pump station or a valve yard, the ground cubes already there fuse into the same picture.
Sense · thermalCore
—
A regional cue on the imagery ring re-tasks the next sortie.
OrbitPatrol
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A corridor view in the Fleet console, not a site view.
What the evidence file holds
Sortie records and the anomaly history — evidence of diligence for the regulator as much as for the incident.
What it is sold as
Surge, per sortie, on top of the sites along the corridor.
What is unproven here
All of it. Patrol cubes are Series A feasibility (D-17); payload order US$30–80k, aircraft and operations through a partner. A moving platform cannot use the static background model — it needs target-referenced tracking and per-frame RTK+IMU pose. Real engineering scope, deliberately outside the seed.
16
S8
Eleven sites, one shift — the estate view
Site Multi-site operator: Aramco affiliate, SWCC, SEC, Mawani, Royal CommissionBuyer SOC lead
P0–P2
mixed across the estate
SEED · FLEET ALPHA M12
The second seed buyer does not have a site problem. They have a consistency problem: eleven sites, eleven vendors, eleven definitions of “suspicious”, and one night shift expected to hold all of it.
—
Every site runs the same classification logic and writes the same evidence schema — on-prem, at each site.
Core
—
The Fleet console shows posture, health and open cases across the estate on one board, in Arabic and English.
Fleet
T+00:00
Two sites 18 km apart each initiate a low-confidence track within four minutes.
Sense · thermalCore
T+00:04
Cross-site correlation raises both: a repeated pattern across an estate is evidence a single site cannot see.
Fleet
T+00:06
Estate-wide posture recommendation to the SOC lead. One approval, logged once, applied to the cluster.
FleetCore
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
One board for eleven sites, with the same words meaning the same thing at each.
What the evidence file holds
Consistent across the estate — the reason a corporate security programme, not a site budget, pays for this.
What it is sold as
Fleet console, usage-based, on top of the per-site subscriptions. This is the land-and-expand motion inside the first two operators (Y2: 8 sites).
What is unproven here
Claim T2 at estate scale, and gate G3 — one signed design-partner LOI below SAR 1M, a second in legal, target week 8.
17
S9
Through a prime — where the commercial product stops
Site Defence or border installationBuyer Defence programme office (MoD, SANG, MoI), via a GAMI-licensed prime
P4
National
SERIES A · VISION
The last scenario is a boundary, not a capability. It is here so that nobody in the room leaves believing the commercial SKU does any of this.
—
Cube arrays assembled in-Kingdom on the common spine — the localisable hardware a prime needs for local-content scoring.
Sense · thermalSense · radarDefence
—
Tracks published to the national IAMD over ASTERIX CAT-129.
Core
—
Early warning from a stratospheric feed via a service partner cues site clusters on a predicted track; sites raise posture pending operator approval.
Core
—
Effector hand-off to the customer’s C2. Not autonomous engagement. Not in the commercial product. Not without the GAMI licence.
Defence
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
The prime’s C2, with elvone as the sensing and fusion layer beneath it.
What the evidence file holds
The same schema. Sovereignty is the point.
What it is sold as
SAR 3–6M per site per year via a prime. 60+ installations in the bottom-up sizing.
What is unproven here
The GAMI licence (applied M3), the prime relationship, and every teaming red line in channel-strategy.md — IP and weights ours, console-skin white-label only, pricing floor, no broad exclusivity, 20–35% prime share.
18
S10
Shamal — the day the cubes go half-blind
Site Petrochemical complex, Jubail · summer dust eventBuyer Industrial Security manager
The first question any Eastern Province operator asks is “what happens in a dust storm?” Every passive sensor we sell degrades in one. This scenario exists to show what the system does about it: it measures its own degradation and declares it, rather than reporting a nominal coverage it no longer has.
T−02:00
Not a weather feed — the cubes’ own scene statistics. Contrast falls across the optical cube’s field; Core drops its weight toward zero on measured contrast, not on a rule about weather.
Sense · opticalCore
T−00:30
LWIR degrades too. Dust absorbs and scatters in the 8–12 µm band; the thermal cube’s effective radius contracts. The console shrinks the coverage ring on screen to the reduced figure.
Sense · thermalCore
T+00:00
Declared degraded coverage. The posture panel recommends escalation and names the reason. A site that cannot see is told it cannot see.
Core
T+00:20
What holds: an RF link is indifferent to dust, and a shamal is loud but broadband — the acoustic array still resolves rotor harmonics at close range. The cue layer carries the picture in close.
Cue · RFSense · acoustic
T+00:30
A track initiates inside the reduced radius on acoustic bearing and RF link detection. Classified at an explicitly lower confidence tier — the mix that produced it is worse, and the number says so.
Core
T+01:10
The case file records the meteorological state, the degraded ranges and the tier. “What could you actually see at 15:40” is an answerable question at the review.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A coverage ring that shrank, with the reason attached — and a confidence tier that fell with it.
What the evidence file holds
Meteorological state, per-cube effective range at the time, the sensor mix that produced the track, and the confidence tier. Degradation is logged as an event in its own right.
What it is sold as
P1 Detect — no separate SKU. This is why the posture is a mix of physics rather than one sensor.
What is unproven here
The LWIR attenuation coefficient for an Eastern Province shamal is taken from published atmospheric data, not from our measurement. The environmental campaign (Track B, M7–M12) measures it on our own cores. Until then the degraded-radius model is a design assumption and is labelled as one on the console.
19
S11
14:40 — the twenty minutes the thermal cube cannot see
Site Eastern Province refinery, HCIS-regulatedBuyer Industrial Security manager
Twice a day the sky background and an airframe’s skin converge in apparent temperature, and an LWIR detector’s contrast goes to zero. Thermal crossover is not a fault; it is physics, and it is on a schedule. Every passive-infrared product in the market has this window. Most do not tell you about it.
T−00:45
The site surface-energy model forecasts the window: sky radiance and predicted airframe skin temperature converge. Predicted crossover 14:31 – 14:53.
Core
T−00:20
The operator is told before it happens, not after. The posture panel recommends leaning on optical and RF for the window. Approved, and logged.
CoreSense · opticalCue · RF
T+00:00
Crossover. Apparent ΔT falls below the cube’s own detection floor. It publishes degraded — it does not go quiet. A sensor that stops publishing is indistinguishable from a sensor that has failed.
Sense · thermal
T+00:06
Daylight and clear: the optical cube carries it, at roughly 6× the angular precision of LWIR, for a tenth of the cost. The triangle geometry is unchanged; only the physics in it changed.
Sense · optical
T+00:14
Track fused from optical bearings and recorded RF silence. The confidence tier reflects the missing modality explicitly, rather than quietly reporting the same number with less behind it.
Core
T+00:23
Window closes. The thermal cube re-enters the solution and the covariance tightens. Every detection in the file carries its crossover state.
Sense · thermalCore
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A forecast, then a sensor that says “degraded” with a countdown — and a confidence tier that moves with the sensor mix.
What the evidence file holds
The forecast, the approved posture change, the per-detection crossover state, and the tier at each moment. The window is in the record whether or not anything flew through it.
What it is sold as
P1 Detect. Predictive crossover scheduling is why the thermal and optical cubes are sold together (D-08) and never separately.
What is unproven here
Predictive thermal-crossover scheduling is claimed as proprietary in sense-cubes.md §5 and has never been run against measured sky radiance at a Saudi site. How wide the window is, how well a surface-energy model predicts it, and whether the optical cube genuinely covers it, are Phase 0 measurements — gate G4, week 8.
20
S12
The wadi — below the horizon, against a hot ground background
Site Inland site cluster, broken terrainBuyer Industrial Security manager / asset protection
P1 → P2
Detect → Aware
SEED · the limit, stated
sense-cubes.md says the thermal cube is a sky-background instrument and that below-horizon approaches are out of scope. Nine scenarios never showed what that costs. This one does: the sector that is not covered, the survey that finds it before anything is bought, and the partial, cheap, honest answer.
D−30
Siting survey, before a single cube is ordered: terrain model plus imagery finds the masked sectors from every candidate mast position. Three approaches sit below the horizon from all of them.
OrbitCore
D−30
The honest consequence, in writing. Against a wadi floor at 47 °C the thermal contrast inverts and the sky-background model is not valid. This sector is not covered by the triangle, and the survey report says exactly that.
Sense · thermal
D−00
Acoustic cubes at the wadi mouth: 300–600 m, bearing only, no range — but indifferent to background temperature and indifferent to emissions. Partial, cheap, and not oversold.
Sense · acoustic
T+00:00
An airframe follows the wadi, masked from the triangle for its whole run-in. Acoustic initiates on rotor harmonics. One bearing, no range, low confidence — and that is what the board shows.
Sense · acoustic
T+00:09
It clears the ridge and enters sky background. Thermal and optical acquire immediately — the acoustic bearing was the prior that told them where to look, which is the whole value of a partial sensor.
Sense · thermalSense · opticalCore
T+00:15
Fused and classified. The file records that the first nine seconds were acoustic-only, at what confidence, and that the sector is a known gap in this site’s coverage.
Core
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
A coverage map with a hole in it, drawn at survey time and never quietly filled in later.
What the evidence file holds
The siting survey and its named gaps, the acoustic-only interval and its confidence, and the moment the track entered covered airspace. The gap is part of the record, not an omission from it.
What it is sold as
P1 plus acoustic cubes. The full answer — an elevated mast, or the aerostat at P3 — is priced separately because at most sites it costs more than the problem is worth.
What is unproven here
The acoustic cube is TRL 2: one array, trialled during the environmental campaign, not committed. Desert afternoon wind is its failure mode and we have not measured it. This scenario deliberately ends at partial, not solved — a below-horizon approach at an inland site is a real limit of the seed product.
21
S13
Listening to what is already in the air — passive radar — research only, not in the seed
Site Eastern Province refinery (as a worked example)Buyer — · no SKU, no price, no roadmap commitment
—
research
RESEARCH · NOT IN THE SEED
This page is a research note, not a capability. It is here because passive radar is the only modality in the family that answers both of the hardest objections in this pack at once — and because decision D-22 is open. Nothing on this page is sold, priced, scheduled or committed.
—
An FM broadcast tower tens of kilometres away is already illuminating this airspace. So is a DVB-T transmitter, and every 5G base station. The energy is continuous, free, and somebody else’s.
Passive radar
—
A reference antenna listens to the transmitter; a surveillance antenna listens to the sky. Cross-ambiguity processing between the two yields bistatic range and Doppler.
Passive radar
—
What that buys, precisely: range and radial velocity — the two things a bearing-only optical triangle fundamentally lacks — with no emission, and therefore no CST spectrum licence to obtain. It answers S1’s RF-silent airframe and S6’s licence problem with one piece of physics.
Passive radarCore
—
What it does not buy: detection of a 0.35 m airframe. Published passive-radar performance is aircraft-scale. The bistatic radar cross-section of a small plastic quadcopter against FM illumination at 1–2 km is the open question, and it is open.
Passive radar
—
And the harder gap: the antennas are the easy part. Direct-signal interference cancellation and clutter suppression at 60–90 dB is where passive radar is actually won or lost, and we do not have that capability in-house today.
Passive radar
Layers engaged
500 km
Orbit
Launch sites, staging, pattern-of-life — regional cues, never detections
~20 km
Stratosphere
Shahed-class in flight over hundreds of km — early warning
300–1,000 m
Tethered sky
Cluster-scale picture; fixes the altitude axis a ground triangle cannot
300–1,500 m AGL
Patrol
Corridors; investigation of a cue; close-range identification
6 m masts
Ground cubes
The workhorse: detection, classification, evidence
site
Legacy
Confirmation and evidence, at no extra coverage cost
CoreCue · RFSense · thermalSense · opticalSense · acousticSense · radarPassive radarFleetSkyPatrolOrbitDefenceLegacy sensors
What the operator sees
Nothing. There is no product here to look at.
What the evidence file holds
None. This scenario has never been run, simulated or bench-tested by us.
What it is sold as
Nothing. Not a SKU, not an add-on, not a roadmap item, not a price. If it appears in a customer conversation as anything other than a research interest, that is a misrepresentation.
What is unproven here
All of it. Decision D-22 is open (concepts/expert-capability-map.md §4). It is re-opened only on evidence of in-house cross-ambiguity and clutter-suppression capability and after two paying sites exist — the scope-creep rule in risk-register.md R-S5. Small-target bistatic RCS, illuminator geometry per site, and compute cost are all unresolved.
22
03 · The coverage matrix
Read across a row: how many situations a component earns its place in
Read down a column: how few components a given situation actually needs. This is the flexibility argument without words.
| S1 Dawn on the fence line | S2 bird that wasn’t | S3 contractor’s survey drone | S4 Match night | S5 camp sixty kilometres out | S6 Runway 34L | S7 Three hundred kilometres of pipeline | S8 Eleven sites, one shift | S9 Through a prime | S10 Shamal | S11 14:40 | S12 wadi | S13 Listening to what is already in the air |
|---|
| Core | ● | ● | ● | ● | ● | ● | ● | ● | ● | ● | ● | ● | ○ |
| Cue · RF | ○ | ○ | ● | ○ | ○ | ○ | · | ○ | ○ | ● | ○ | ○ | · |
| Sense · thermal | ● | ● | · | ● | ○ | ○ | ○ | ○ | ○ | ○ | ● | ● | · |
| Sense · optical | ● | · | · | ● | ○ | ○ | ○ | ○ | ○ | ○ | ● | ○ | · |
| Sense · acoustic | · | · | · | ● | · | · | · | · | ○ | ● | · | ● | · |
| Sense · radar | · | · | · | ○ | · | ● | · | · | ○ | · | · | · | · |
| Passive radar | · | · | · | · | · | · | · | · | · | · | · | · | ● |
| Fleet | · | · | · | ○ | ○ | · | ● | ● | ○ | · | · | · | · |
| Sky | · | · | · | ● | · | · | · | · | ○ | · | · | · | · |
| Patrol | · | · | · | ○ | ● | · | ● | · | ○ | · | · | · | · |
| Orbit | · | · | · | ○ | ● | · | ○ | ○ | ○ | · | · | ○ | · |
| Defence | · | · | · | · | · | · | · | · | ● | · | · | · | · |
| Legacy sensors | ○ | ● | ○ | ○ | ○ | ○ | · | ○ | ○ | ○ | ○ | ○ | · |
● primary · ○ contributing · · not engaged
What the matrix says
Core is the only solid row — the thesis in one line: the brain is the product, the cubes are the moat. No cube row is solid, which is the design rule that no cube is load-bearing for another; each has its own kill gate and can be retired without taking anything else with it. And the busiest columns, S4 and S5, are the furthest from the seed — the honest reading is that the seed sells S1, S2, S3 and S8.
concepts/scenario-playbook.md §6; DECISIONS.md D-08 (cube sequence), D-16 (postures). Scenario set is illustrative design intent.
23
04 · Act V
Whatever lit up, the review gets the same file
The scenarios diverge. The output does not. That is the part that compounds — and the part a foreign vendor or a cloud product cannot copy from outside the Kingdom.
One schema
Every layer — a satellite cue, a patrol sortie, a thermal node, a legacy radar — publishes the same timestamped detection record. The evidence file, the classification logic and the console never change with the sensor mix.
Bit-exact replay
The same binary runs live and recorded input; time comes from the message; randomness is seeded; no fast-math. A double replay must diff empty — a CI gate from month 1.
Free ground truth
Remote ID labels every compliant aircraft near every site. Coincidence gating mines hard negatives — dust devils, shimmer, birds, artefacts — at zero labelling cost. Every pilot adds Saudi-sky, Saudi-clutter data.
Sovereign by construction
Processing is on-prem or air-gapped; detections are a few hundred bytes and no raw video, audio or IQ crosses the network. Models are retrained offline and promoted through shadow mode — better classification without giving up data sovereignty.
The ask
US$5M (SAR 18.75M) seed for 18 months, plus SAR 6–8M non-dilutive targeted for the cubes. Series A gate: 2 paying sites, SAR 3–5M contracted ARR, ISO 27001, one HCIS-reviewed deployment, first cubes validated, GAMI licence. Judge the evidence plan and its dates, not the polish.
concepts/product-thesis-v3.md §5 (flywheel); investor-pack/13-technical-diligence-pack.md §3, §5; DECISIONS.md D-20 (round size), D-10 (Series A gate).
24
04 · Using this in a room
Six routes through the same scenario library
The spine is fixed and takes six minutes. Choose Act IV for the person in front of you.
| Audience | Time | Route | The question you want back |
|---|
| Site security manager | 10 min | Acts I–III → S1 → S2. Stop. | “What does P1 cost, and how long is the install?” |
| SOC lead, multi-site operator | 15 min | Acts I–III → S8 → S3 as the daily-use case → matrix | “Can you start with three sites and the Fleet view?” |
| Investor, first meeting | 20 min | Full spine → S1 → S4 → S5 (the flexibility triple) → matrix → the gate board | “Which gate closes first, and what does it cost to close?” |
| Defence expert (Sanabil call) | 30 min | S6 → S9 → matrix → straight into 14-defence-expert-qa.md | “Show me the Phase 0 error budget and the CST path.” |
| Prime / integrator | 15 min | S9 → matrix → channel-strategy.md red lines | “What is the local-content score on the cube spine?” |
| GADD / grant reviewer | 15 min | Component table → S1 → S5 → grant-application-draft.md | “What is assembled in-Kingdom, and on what timeline?” |
The one thing not to do
Do not present a scenario page without its “What is unproven here” cell. The pack’s whole credibility position — and the correction already recorded as D-21, where a public claim of live deployments was withdrawn — is that we do not assert what we have not measured. The scenarios are illustrative design intent, and saying so out loud is what makes the rest of the document believable.
concepts/scenario-playbook.md §7; DECISIONS.md D-21. Companion artefacts: investor-pack/03-pitch-deck-v3-script.md, 13-technical-diligence-pack.md, 14-defence-expert-qa.md.
25