LensReading which lens this session carries.

Auditor evidence pack

Forecast item at diagnose

Supply Chain · Demand Planning · line SC1B · Demand Signal 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
SC1B-1008
Subject
Pierre Ferreira
Requested by
Naomi Lindqvist
Value
$24k
Materiality
low
Currently held by
Planning Policy Agent (agent)
Sub-function owner
Director, Demand Planning
Orchestrator
Demand Planning Orchestrator

Every action, in order

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

1
Demand Planning OrchestratororchestratorCleared

Cleared detect deviation

2026-08-18 07:50:00ZAuthority SC1-AUTH-A1 · cap $25,000Jurisdiction SGAutonomy A3Retention OPS-3Y
Prompt
orchestrator-brief@p14
Policy
materiality-bands@v9
Tools
read-only-lookup@t12, notify-and-route@t5
in 9a85b92e...64eab8out 00ef576f...663d4aartifact ART-SC1B-1001-1 genesis 86ef0265...49d24d
2
Promotion Lift AgenttaskIn progress

Holding at diagnose

2026-08-18 08:25:00ZAuthority SC1-AUTH-A1 · cap $25,000Jurisdiction SGAutonomy A4Retention OPS-3Y
Prompt
task-execution@p21
Policy
materiality-bands@v9
Tools
document-fetch@t9, read-only-lookup@t12
in d37f9770...c37473out 340b094c...ceb6b7artifact ART-SC1B-1001-2 86ef0265...49d24d 94f98f90...edbcd1

Authority relied on

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

SC1-AUTH-A1ActiveDemand Planning Orchestrator

Any unit on a demand planning 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 · DE · SG · AUDelegated from Director, Demand PlanningExpires 2027-06-05

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelreasoner-core5.4currentPlatform model council
modelextract-lite2.9currentPlatform model council
policymateriality-bandsv9currentGroup controller
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 outside band
Held for a named human when the unit exceeds the forecast item decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Demand Planning · not reached

Records schedule and holds

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

OPS-3Y3 years
Operational routing and execution
Internal operating requirement. No statutory driver, so the shortest defensible period is used deliberately.
Deleted at three years. This is the only class where the estate deletes rather than retains by default.

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.