LensReading which lens this session carries.

Auditor evidence pack

Prototype at build

Research & Development · Prototype & Pilot · line RD6A · Prototype Cycle. 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. 3 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
3
Append-only, sequenced
Agent actions
3
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
RD6A-1019
Subject
Amara Ito
Requested by
Maeve Ferreira
Value
$26k
Materiality
low
Currently held by
Iteration Tracking Agent (agent)
Sub-function owner
Director, Product Development
Orchestrator
Prototype Orchestrator

Every action, in order

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

1
Build Planning AgenttaskCleared

Cleared define target

2026-08-18 08:19:00ZAuthority RD6-AUTH-A1 · cap $25,000Jurisdiction USAutonomy A3Retention TECH-3Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in 5355250d...304406out 271c7424...7af5a8artifact ART-RD6A-1002-1 genesis c21459fd...49e961
2
Test Plan AgenttaskCleared

Cleared plan build

2026-08-18 08:33:00ZAuthority RD6-AUTH-A1 · cap $25,000Jurisdiction USAutonomy A3Retention TECH-3Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in c3295062...584814out 433b9673...61d2caartifact ART-RD6A-1002-2 c21459fd...49e961 40cc943f...7e7239
3
Iteration Tracking AgenttaskIn progress

Holding at build

2026-08-18 08:46:00ZAuthority RD6-AUTH-A1 · cap $25,000Jurisdiction USAutonomy A3Retention TECH-3Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in 4bc9422a...c91104out 74d19bb8...00a585artifact ART-RD6A-1002-3 40cc943f...7e7239 b63ced01...333ff1

Authority relied on

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

RD6-AUTH-A1ActivePrototype Orchestrator

Any unit on a prototype & pilot 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, Product DevelopmentExpires 2026-09-30

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelextract-lite2.9currentPlatform model council
policysegregation-of-dutiesv4currentInternal audit
prompttask-executionp21currentShared service engineering
toolsetread-only-lookupt12currentPlatform engineering
toolsetdocument-fetcht9currentShared service engineering

Gates on this line

The control points this unit had to clear

Readiness review
Held for a named human when the unit exceeds the prototype decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Product Development · 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.