LensReading which lens this session carries.

Auditor evidence pack

Change at classify

Revenue Operations · Systems & Integration · line RO10A · Integration Incident. This pack names every action taken on this unit, who or what took it, the authority that permitted it, and the model, prompt and policy versions in force at that moment.

Chain verified

Every record links to the one before it and hashes to its stored value. 2 records were re-hashed on this page load, in order, starting from the genesis value. Nothing was read from a cached verdict.

hash = sha256(prevHash + "|" + JSON{seq, unitRef, actor, action, outcome, occurredAt})

Records
2
Append-only, sequenced
Agent actions
2
Taken by software
Human actions
0
Taken by a named person
Refusals
0
Blocked by the authority register
Corrections
0
Later record supersedes an earlier one
Legal hold
None
Free to age out on schedule

The unit

What the work was, and where it sits

Reference
RO10A-1009
Subject
Callum Costa
Requested by
Jonas Raman
Value
$65k
Materiality
medium
Currently held by
Sync Failure Agent (agent)
Sub-function owner
Director, Revenue Systems
Orchestrator
Revenue Systems Orchestrator

Every action, in order

Actor, authority, versions in force, and the hash link to the record before it

1
Revenue Systems OrchestratororchestratorCleared

Cleared detect failure

2026-08-18 07:19:00ZAuthority RO10-AUTH-A1 · cap $250,000Jurisdiction SGAutonomy A3Retention CUST-5Y
Prompt
orchestrator-brief@p14
Policy
customer-commitments@v5
Tools
read-only-lookup@t12, notify-and-route@t5
in c5407dc7...eb0e16out 68efcdb3...8768dfartifact ART-RO10A-1001-1 genesis 9bdbf92f...542d1c
2
Sync Failure AgenttaskIn progress

Holding at classify

2026-08-18 08:09:00ZAuthority RO10-AUTH-A1 · cap $250,000Jurisdiction SGAutonomy A3Retention CUST-5Y
Prompt
task-execution@p21
Policy
customer-commitments@v5
Tools
document-fetch@t9, read-only-lookup@t12
in bd2aceee...dd1a55out a900e16b...c2869bartifact ART-RO10A-1001-2 9bdbf92f...542d1c 4041490b...43457c

Authority relied on

Who was allowed to do this, up to what value, in which jurisdictions

RO10-AUTH-A1ActiveRevenue Systems Orchestrator

Any unit on a systems & integration line where every intake check passed, the policy in force is current, and the value sits inside the cap below.

Cap $250,000US · UK · DE · SGDelegated from Director, Revenue SystemsExpires 2027-04-21

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelreasoner-core5.4currentPlatform model council
modelextract-lite2.9currentPlatform model council
policycustomer-commitmentsv5currentChief revenue officer
promptorchestrator-briefp14currentChief of Staff office
prompttask-executionp21currentShared service engineering
toolsetread-only-lookupt12currentPlatform engineering
toolsetnotify-and-routet5currentPlatform engineering
toolsetdocument-fetcht9currentShared service engineering

Gates on this line

The control points this unit had to clear

Escalate
Held for a named human when the unit exceeds the change decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Revenue Systems · not reached

Records schedule and holds

How long this evidence must be kept, and whether it is frozen

CUST-5Y5 years
Customer commitment and service evidence
Consumer claim windows and revenue recognition audit trail.
Deleted at five years from the last account activity.

What this pack proves, and what it does not

Read this before you rely on it

It does prove
  • Every action carries a named actor, an actor kind, and a timestamp.
  • Every action names the authority grant that permitted it and the cap that grant carries.
  • Every action stamps the model, prompt, policy and tool versions in force at that moment.
  • Corrections are additive. A later record supersedes an earlier one and says why; the earlier record is never edited or deleted.
  • The chain is re-hashed live on this page, so a single altered field is detected immediately.
It does not prove
  • It is not tamper-proof against an attacker with write access to the store, who could rewrite the whole chain from genesis. Making that impossible requires publishing chain tips to a store this application cannot write to. That anchor is not built, and this page does not claim it.
  • The evidence in this demonstration is modeled from a simulated estate, not captured from production systems.
  • Identity here is the actor name recorded on the action. Cryptographic agent identity and signed attestation are a separate piece of work.