Skip to content
Lorca Labs
Live demo
Agents & policy

Escape Hatch Notarization

Not a break-glass lever, but a notarized record of why the lever was pulled.

The problem

When a policy exception is needed, you need a tamper-evident record of the reason, scope, and expiration — and optionally a sealed copy that can travel with the agent. The notarization produces a content hash and timestamp; sealing binds the hash into a carrier image for key-bound retrieval.

What it does

01

Notarizes an exception reason with optional policyId, actor, exceptionScope, expiresAt, and evidenceHash.

02

Returns a notarizationId, contentHash, and sealedAt timestamp.

03

Seals the notarization into a carrier image (imageBase64, width, height, channels, optional key).

04

Lists notarizations (notarization metadata) and fetches a full record by ID.

Who it’s for

  • SREs documenting emergency policy bypasses
  • Governance teams auditing exception reasons
  • Security reviewers verifying notarized scope bounds

In context

Complements Sovereignty (agent governance) and the Stego Audit Carrier (carrier-bound audit).

Try it live in the studio

A no-signup, in-browser experiment against an isolated demo host. Load sample data, run the flow, and see the result — nothing is stored.