Greene source-described flow

A historical/source-described counter-UAS decision-support walkthrough built around killinchu and the a11oy Λ-gate. It models a path from a raw broadcast signal to a receipted recommendation; it is not evidence that this end-to-end path ran on the current hosted revision.

The flow

1. Ingest (source-described) a broadcast self-ID shape (Remote-ID, ADS-B, or MAVLink) through a documented /v1/*/decode route.
2. Geofence (source-described) — haversine breach check against the protected volume.
3. Λ-gate (source-described) — fuse the geofence result with the 13-axis yuyay_v3 score; conjunctive AND, no compensation.
4. Receipt (source-described) — form a Khipu receipt in an in-memory Merkle DAG; signature status remains PLACEHOLDER.
5. Recommendation (source-described) — return decision-support output for operator review.

What the source flow demonstrates

Source inspection can audit the intended protocol parse, haversine calculation, 13-entry score vector, and receipt-chain construction. The docs-site observation did not invoke the decode, evaluation, or receipt routes, so hosted end-to-end reproducibility is UNAVAILABLE here. It would require an exact-revision action-route response plus payload, authorization, dependency, receipt, and independent readback evidence; the successful health response supplies none of those bindings.

Honest boundaries

• Decision support only — no autonomous engagement, no effector control.
• Broadcast signals are unauthenticated and spoofable; every decoded field is a claim.
• DSSE signatures are PLACEHOLDER; the receipt's SHA-256 chain is real (see Compliance).
• Hosted evidence is health-only: GET /api/killinchu/healthz returned HTTP 200 at exact revision 83142da9526e2c0ddfe1e78eb99a20940cde0cf3 during the dated observation. No /v1/* route was witnessed.

This flow is a source-described historical companion to the Quickstart killinchu health step. Recheck /status; health does not establish action-route availability.