Keep a record of why the gateway allowed or blocked a request.
Record important allow, deny, redaction and review decisions so security teams or customers can inspect them later without access to the gateway's private logs.
- Allow
- Forwarded, with the policy that applied bound to the record.
- Deny
- Refused, with the reason code and policy digest bound.
- Redact
- Changed in transit, with produced and delivered digests bound.
- Metered
- Allowed against a paid endpoint, with the observed payment context.
A customer cannot check your gateway logs.
Gateway logs help you debug a routing or policy decision, but you cannot hand them to a customer, auditor or counterparty to check for themselves. A signed record answers what they will want to know:
- Which policy version applied at that moment?
- Was the request allowed, denied, or modified?
- What content was actually delivered, versus what was produced?
- Which agent or workload spent what through the gateway?
- Can any of this be verified later, without access to our systems?
What the record of one gateway decision contains.
- Issuer
- https://gateway.vendor.example
- Request
- tools.call market_data
- Decision
- allow
- Policy
- tool-policy:v2 sha256:4e21b8...
- Produced
- sha256:9a3c1d...
- Delivered
- sha256:9a3c1d...
- Time
- 2026-07-02T09:14:31Z
- Signature
- Ed25519 30cf81d6... kid 2026-07-key1
"_meta": {
"org.peacprotocol/receipt_ref": "sha256:f04d11...",
"org.peacprotocol/receipt_jws": "eyJhbGciOiJFZERTQSIs..."
}In front of MCP servers the record rides the tool result's _meta. HTTP gateways carry it in the PEAC-Receipt response header. Records can also export as bundles.
A refused or redacted request is still an event.
A signed deny records what was refused, when and why. The reason code, policy digest and timestamp are all covered by the signature.
When the gateway redacts rather than blocks, the record binds the issuer-reported produced and delivered representations. A separate delivery observation is required to establish what the recipient received.
- Issuer
- https://gateway.vendor.example
- Request
- tools.call export_billing
- Decision
- denied - policy_violation
- Policy
- tool-policy:v2 sha256:4e21b8...
- Time
- 2026-07-02T09:16:04Z
- Signature
- Ed25519 e02d7f15... valid
Records connect to the tools around your gateway.
- OpenTelemetry trace correlation: records carry W3C trace context, so a gateway decision links to the same trace in your OpenTelemetry backend via the
peac.record.refspan attribute. - In front of MCP servers: per-tool-call records travel alongside the gateway decision. See MCP tools.
- In front of paid or metered endpoints: x402-style payment observation binds the decision to the call it metered. See agent payments.
- Evidence bundles: export a set of decision records for a review, verifiable without access to the gateway.
What Originary does not do here.
- It does not route or proxy traffic.
- It does not enforce or decide policy.
- It does not rate-limit or gate anything.
- It does not replace your gateway, WAF, or observability stack.
- It does not move or settle money.
- It does not score or rank counterparties.
It records the decisions your gateway already makes.
Start with one gateway route.
Pick the route a security team or customer already asks about, and we will define its record with you.
npx -y @peac/cli@0.16.4 verify ./gateway-decision.jws --public-key ./jwks.json