LensReading which lens this session carries.

Auditor evidence pack

Model at assess dependency

Research & Development · Data Science & Modeling · line RD5C · Model Retirement. 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
RD5C-1017
Subject
Clara Costa
Requested by
Farrah Costa
Value
$40k
Materiality
medium
Currently held by
Validation Agent (agent)
Sub-function owner
Director, Data Science
Orchestrator
Modeling Orchestrator

Every action, in order

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

1
Modeling OrchestratororchestratorCleared

Cleared detect obsolescence

2026-08-18 05:03:00ZAuthority RD5-AUTH-A1 · cap $250,000Jurisdiction AUAutonomy A3Retention TECH-3Y
Prompt
orchestrator-brief@p14
Policy
segregation-of-duties@v4
Tools
read-only-lookup@t12, notify-and-route@t5
in 7704e04a...c71c37out e3e4b7fa...d704acartifact ART-RD5C-1002-1 genesis 4c0e6e44...cc18e9
2
Model Training AgenttaskIn progress

Holding at assess dependency

2026-08-18 07:01:00ZAuthority RD5-AUTH-A1 · cap $250,000Jurisdiction AUAutonomy A3Retention TECH-3Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in 05a45e06...8e097eout 8693f7aa...c358f1artifact ART-RD5C-1002-2 4c0e6e44...cc18e9 a56db4ea...0871e2

Authority relied on

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

RD5-AUTH-A1ActiveModeling Orchestrator

Any unit on a data science & modeling 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 · SG · AU · FRDelegated from Director, Data ScienceExpires 2026-12-03

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

Owner approve
Held for a named human when the unit exceeds the model decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Data Science · not reached

Records schedule and holds

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

TECH-3Y3 years
Technology change and access evidence
Security review and change audit requirement.
Deleted at three years from the change closing.

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.