Aurora-Lens adjudicates execution before consequence.

Submit any request. Aurora-Lens evaluates admissibility at the execution boundary—domain, authority, ambiguity, contradiction, and discourse state—before output is authorized to leave the boundary.
Authority —
Example SAFE EXAMPLE
Decision —
1. Request & context
Idle
Submitted request
Submit a request above, or run a boundary test below.
2. Released output
Release: pending
Released output
No turn submitted yet.
3. Adjudication Record
Record
LLM called: —
Status
—
Decision path
—
LLM called
—
Pre-LLM blocked
—
Release path
—
Failed constraint
none
Domain
—
Authority class
—
Pending hold
inactive
Blocked output
none
Has blocked upstream output
—
Released (telemetry)
—
Intercepted upstream (operator-only)
—
Original response (released)
—
Attempted action
—
Authorized continuation
None
4. Decision Proof
Turn audit
Ledger verification
hmac_verified
not returned
chain_verified
not returned
fully_verified
not returned
backend
not returned
entries checked
not returned
reason / operator_message
not returned
Current turn receipt
Only fields returned for this turn are shown. Ledger verification reflects aggregate chain checks; it does not substitute for per-turn hashes unless the backend sends them.
session_id
not returned by current payload
trace_id
not returned by current payload
prev_hash
not returned by current payload
hash
not returned by current payload
state_hash
not returned by current payload
entry_index / chain position
not returned by current payload
hmac_verified (this entry)
not returned
chain_verified_to_entry
not returned