Cued Engagement — the Yachay-Dome /v1/cue product

This is the product: a signed, Khipu-receipted target package — track + four-color classification + predicted-impact + recommended response tier + ATAK-compatible CoT XML + MIL-STD-2525 symbol + the full provenance chain.

The one invariant. /v1/cue is a ONE-WAY EVIDENTIARY HANDOFF — a recommendation and a Body-of-Evidence, never a command. There is no actuation token in the schema. We detect → fuse → classify → predict → warn → cue. The Title 10/50 customer jams/spoofs/hacks/intercepts. We are the brain, not the trigger.

Sample target package

loading…

The Dome(a) legal gate

In the PURIQ master operator, Yachay-Dome adds one admissible organ factor: Dome(a) ∈ [0,1]. Any action whose response_class is outside the commercial lane (jam/spoof/hack/kinetic) gets Dome(a)=0 — structurally un-selectable, like a tripped HUKLLA tripwire. The legal boundary is a multiplicative zero in the decision math itself, enforced by construction, not policy text.

Live endpoint browser: the orchestrator at /a11oy.code can draft a cue package in natural language ("show me anything within 5km of HQ that isn't an ally"), then route it through the 2-person Yuyay gate on human approval.

Source: killinchu/yachay_dome/CUED_ENGAGEMENT_API.md · A11OY_BRAIN_INTEGRATION.md