Where a finding goes when it leaves the registry
Every finding the registry makes about a plate, an act refused or held, an approval or denial with its receipt, a gate dropped, the coverage lamp going red, a plate revoked, can be pushed to the systems a security team already watches. What travels is a pointer into evidence: the plate, the kind, the severity, the person, a short summary, the record hash and the receipt link. No prompt and no tool output ever leaves. The receiver holds pointers; the registry holds the proof, and anyone with the receipt can verify it offline.
The sinks
Ten sinks, one delivery contract: three retries over about twenty minutes, every attempt in a delivery log, a test-send before anything is saved so the receiver proves the wire first. The status column says what has been exercised against a real endpoint and what has only been built against the vendor's published reference; it changes as each real send lands.
| Sink | What the receiver gets | Status |
|---|---|---|
| Slack | One message per finding with a severity colour bar, the person, the receipt link and the record hash | Exercised live, 19 Oct 2026 |
| Microsoft Sentinel | A row in a custom table (XChk_CL) through the Logs Ingestion API: plate, kind, severity, person, summary, record hash, receipt URL, registry | Exercised live, 19 Oct 2026 |
| Azure Event Hubs | One event per finding on a hub, for Stream Analytics, Fabric or anything downstream | Exercised live, 19 Oct 2026 |
| Azure Blob archive | The full receipt bundle, verifiable offline, written to a container under a write-only policy: the evidence store on the customer's side | Exercised live, 19 Oct 2026 |
| Signed webhook | A CloudEvent per finding, signed with a shared secret (t=…,v1=…, Stripe-style), with a published verifier | Built; verifier published; awaiting a real receiver |
| Splunk HEC | An event per finding to the HTTP Event Collector | Built against the published reference |
| CrowdStrike Falcon NG-SIEM | An event per finding to the LogScale ingest endpoint | Built against the published reference |
| Datadog Logs | A log item per finding to the intake API | Built against the published reference |
| ServiceNow | An incident, or an ITOM event, per finding | Built against the published reference |
| Taegis XDR | An event per finding to HTTP Ingest | Built; needs a test tenant |
A sink marked "built" is believed correct from its vendor's public reference and a unit test of the request it sends; the first real send is what will say so, and the delivery log is where it says it.
What the registry talks to
Beyond the sinks, the registry connects on both sides of a gated act. Everything listed here has been exercised live.
- Microsoft Entra: a work sign-in enrols the person, and the tenant that vouched for them rides inside the signed receipt binding, verifiable offline.
- Microsoft Agent Governance Toolkit: the registry is an approval backend for its action-bound approval protocol; an agent's request stops for a person's passkey, and the signed answer carries the receipt.
- Five harness gates: Claude Code, Codex, Cursor, Hermes and Antigravity ask the registry before every gated tool call; a GitHub Copilot CLI gate shipped on 19 Oct 2026 and its first live run is pending.
- Ravencoin and OpenTimestamps: seal heads anchored on public chains, so the record's existence at a time needs nobody's word.
- AgenTrust TRACE: a Trust Record per run, with sealed receipts as approval-outcome references, and a signed revocation bundle.
The whole picture, with what comes in, what goes out and what never leaves: the connections map.
Try a sink
Sign in to the registry, open Developer → Connectors, add a sink, paste your environment file, and send a test finding before you save. The receiver proves the wire.