What animates in this block, and the technique — GSAP pin/scrub, three.js scene, SVG line-draw, stagger reveal, count-up. Motion always explains the system or the sector; never decoration.
Where the content derives from: a deck slide (e.g. DECK S7), the hardware datasheets (DS R1.0), the current site (SITE), or NEW copy to be drafted.
Ships only after this item passes the content-clearance list (Strategy §4): customer / partner / government names, geographies, counts, advisor consent, imagery rights. Until cleared, the build carries an anonymized or omitted variant.
One continuous story: the Living Site Model (a particle-and-line abstract facility) persists from the hero through the pinned SEE → UNDERSTAND → ACT sequence, then the page widens out to sectors, platform, hardware and proof.
H1 uses the company’s own approved line “Unlock the Unseen”; sub-line derived from the mission (“AI-driven security, aerial logistics & business insight for the physical world”). Final copy at P3; alternates offered then.
Camera FOV cones sweep and illuminate the site model. Fixed coverage: Robin · Sparrow · Skycatcher.
Detections thread between cameras — cross-camera re-ID lines converge into the Hornet core (X-gateway node).
BB drone lifts from its dock; flight path draws to the event — responds to a threat, or delivers a payload.
Register note: the pipeline slide’s drone-count discrepancy (1,130 headline vs 1,230 site-sum) is still open in Deck V2-D3 — one more reason this block ships count-free regardless of clearance outcome.
All three sector pages run the same seven-block template so the system reads as one company; the hero motif, capability set, hardware row and vignette are sector-specific.