Gatehouse — Live Console

The guarded front door of an autonomous vendor-review pipeline. Both buttons hit the real production endpoint.

Pick a document. The response below is the live system's actual answer.

responses appear here

What you're looking at

1Intake — this page. Model Armor screens every document inline, fail-closed; the verdict is ledgered (digest only, never the text).

2Review fleet — three agents on Agent Engine ground findings in temporally-valid evidence; stale evidence is pruned and flagged, not trusted.

3Approval gate — risk ≤ 0.7 publishes vendor-approved; otherwise held for a human. Fail-closed.

4Enablement — recalls the findings from Memory Bank and onboards the vendor with training conditioned on the exact gaps found. approve_vendor is not a registered action — attempts become REFUSAL nodes.

Reading the receipt

intake_run: this request's run in the evidence ledger (root id)
screen_node: the Model Armor verdict as a content-addressed node
seal: rolling SHA-256 over the run + custody entry — tamper with one byte and verification names the node
verdict: the raw filter results (which filter matched, and how)
message_id: the Pub/Sub event that wakes the fleet (clean docs only)

Verify it yourself

Our sealed review replays offline from a clean clone — zero credentials, model and database provably unreached:
pytest --pollard-mode=replay
Full instructions in the repo README (linked on Devpost).