LensReading which lens this session carries.

Auditor evidence pack

Regulatory item at assess impact

Legal · Regulatory Affairs · line LG5A · Regulatory Change Response. 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
LG5A-1033
Subject
Maeve Sorensen
Requested by
Lukas Voss
Value
$81k
Materiality
medium
Currently held by
Change Implementation Agent (agent)
Sub-function owner
VP Regulatory Affairs
Orchestrator
Regulatory Affairs Orchestrator

Every action, in order

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

1
Regulatory Affairs OrchestratororchestratorCleared

Cleared detect change

2026-08-18 08:30:00ZAuthority LG5-AUTH-A1 · cap $250,000Jurisdiction DEAutonomy A2Retention LEG-10Y
Prompt
orchestrator-brief@p14
Policy
segregation-of-duties@v4
Tools
read-only-lookup@t12, notify-and-route@t5
in 45359443...414797out 9e613501...994ae1artifact ART-LG5A-1004-1 genesis 0c3c45cd...f8fe60
2
Impact Assessment AgenttaskIn progress

Holding at assess impact

2026-08-18 08:45:00ZAuthority LG5-AUTH-A1 · cap $250,000Jurisdiction DEAutonomy A2Retention LEG-10Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in 96b2a425...d76f65out e06bb2b3...2f305dartifact ART-LG5A-1004-2 0c3c45cd...f8fe60 22a466bd...8ea385

Authority relied on

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

LG5-AUTH-A1ActiveRegulatory Affairs Orchestrator

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

Cap $250,000US · UK · DEDelegated from VP Regulatory AffairsExpires 2027-03-04

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelreasoner-core5.4currentPlatform model council
modelextract-lite2.9currentPlatform model council
policysegregation-of-dutiesv4currentInternal audit
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

Counsel review
Held for a named human when the unit exceeds the regulatory item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: VP Regulatory Affairs · not reached

Records schedule and holds

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

LEG-10Y10 years
Legal and regulatory correspondence
Regulatory inspection windows and the outer limitation period for corporate filings.
Deleted at ten years. Never deleted while any related matter carries an open hold.

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.