LensReading which lens this session carries.

Auditor evidence pack

Developer request at validate

Engineering · Developer Experience · line EN9A · Environment Request. 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
EN9A-1039
Subject
Pierre Mensah
Requested by
Leila Petrov
Value
$27k
Materiality
low
Currently held by
AI-OPS spine (gbs)
Sub-function owner
Director, Developer Platform
Orchestrator
Developer Experience Orchestrator

Every action, in order

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

1
Developer Experience OrchestratororchestratorCleared

Cleared request

2026-08-18 08:50:00ZAuthority EN9-AUTH-A1 · cap $25,000Jurisdiction USAutonomy A3Retention TECH-3Y
Prompt
orchestrator-brief@p14
Policy
segregation-of-duties@v4
Tools
read-only-lookup@t12, notify-and-route@t5
in dbedfff5...cc04c8out cd12be47...b617feartifact ART-EN9A-1005-1 genesis ec16f220...0a0346
2
Build Time AgenttaskIn progress

Holding at validate

2026-08-18 08:55:00ZAuthority EN9-AUTH-A1 · cap $25,000Jurisdiction USAutonomy A4Retention TECH-3Y
Prompt
task-execution@p21
Policy
segregation-of-duties@v4
Tools
document-fetch@t9, read-only-lookup@t12
in b4fdba14...58415fout 07165abf...be3128artifact ART-EN9A-1005-2 ec16f220...0a0346 44521281...906a73

Authority relied on

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

EN9-AUTH-A1ActiveDeveloper Experience Orchestrator

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

Cap $2,000,000US · UK · DEDelegated from Director, Developer PlatformExpires 2026-11-13

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

This line runs without a formal gate.

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.