Airspace Event Journal: Bounded Text Log of What the Mesh Measured
Boils the day's radio activity down to a small text diary a person or an AI can read end to end.
Contested Space · Contested capability
Latent emits a reading. It does not switch cameras, unlock cages, cut power or open a ticket. Your VMS, PoE switch or access controller does that, on your side of the boundary. A Latent blueprint contains no executable code, no remote URLs and no device secrets — by schema, not by policy.
No face, no plate, no MAC, no device identity, no payload. A movement signature is a shape moving through a room, not a person. Nothing stored here resolves to an individual.
A jammer already running when you took the baseline is invisible. The baseline must be captured in a verified-quiet window, and a baseline of unknown provenance is worth nothing.
Each node mints its own key over USB, in your hand. Physical possession is the root authority: a device that cannot prove physical presence is refused enrollment outright. A cloud pairing PIN is a weaker ownership claim and is never treated as liveness.
Every reading is attributable to a device id, profile id, hardware id and firmware version recorded at install and verified by mutual HMAC-SHA256 proof over an LFW1 nonce exchange. A node whose proof did not verify is marked untrusted, not merely offline.
Completing an installation is a high-risk action. It requires your explicit browser approval, an approval snapshot that still matches, an idempotency key, and heartbeats less than three minutes old. There is no silent commissioning.
How enrollment worksProperties you can map to your own controls
These are properties, not certifications. Latent does not assert compliance with any framework on your behalf.
The evidence is proven or strong, but this capability still needs a capability-specific ESP32 or Rust runtime adapter.
Published physics or adjacent results support the hypothesis; capability-specific product and site validation are still required.
No browser runtime is assigned to this capability yet.
No capability-specific offline runtime is mapped yet. Keep the feature visible, explain the required edge adapter, and never fabricate a live result.
Intended capability
This describes the intended outcome. Readiness is needs edge adapter, evidence is class B, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
The single 64 KB WASM page is genuinely built for reduction, not for imaging: turning a continuous stream of scalar link statistics into a bounded token sequence is arithmetic that fits in one page with room to spare. The blueprint language's text pattern already bans URLs and markup, so the event grammar and the document that carries it are the same shape of bounded, inert text.
Per-node link-health and noise-floor series + upstream kernel verdicts -> fixed-grammar event encoder with a hard per-window token budget -> deduplication and run-length collapse across quiet windows -> append-only daily journal -> host-side LLM reasoning over a multi-day window (off-device by definition).
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Own-hardware: 30 days of journal from an eight-node office deployment, with three scripted anomalies planted on unannounced days; measure whether a frontier model reading five days of journal identifies each planted event and its room, and count how many real anomalies the grammar discarded because it had no field for them. No runtime kernel computes the headline — the journal consumes upstream events, following the same precedent as rack-tamper-geometry-door-panel-blanking and hot-aisle-technician-copresence-ledger.
'Airspace Journal' — a days-deep, human-readable and model-readable record of what the mesh measured, sold to the SOC lead as a source that feeds their platform, on the stated condition that an anomaly the grammar did not anticipate is discarded forever.
A quiet reading is not an all-clear. If nodes are stale, degraded or jammed, this runtime says so explicitly. It never infers safety from missing data.