LensReading which lens this session carries.

Auditor evidence pack

Sourcing event at compare

Procurement & Source-to-Pay · Sourcing & RFx · line PR3B · Rapid Sourcing.

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
Held
HOLD-003

The unit

What the work was, and where it sits

Reference
PR3B-1001
Subject
Jonas Whitfield
Requested by
Clara Nakamura
Value
$69k
Materiality
medium
Currently held by
S2P spine (gbs)
Sub-function owner
Director, Strategic Sourcing
Orchestrator
Sourcing Orchestrator

Every action, in order

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

1
Requirement Capture AgentgbsCleared

Cleared capture

2026-08-18 06:39:00ZAuthority PR3-AUTH-A1 · cap $250,000Jurisdiction SGAutonomy A3Retention PROC-7YLegal hold HOLD-003
Prompt
task-execution@p21
Policy
supplier-onboarding@v6
Tools
ledger-write@t7, document-fetch@t9
in c091e708...a2a3dcout f45e5da5...d5d13cartifact ART-PR3B-1000-1 genesis → 6fa207ed...ac0c08
2
Requirement Capture AgentgbsCleared

Cleared match framework

2026-08-18 07:26:00ZAuthority PR3-AUTH-A1 · cap $250,000Jurisdiction SGAutonomy A3Retention PROC-7YLegal hold HOLD-003
Prompt
task-execution@p21
Policy
supplier-onboarding@v6
Tools
ledger-write@t7, document-fetch@t9
in e4b94fa9...ab687fout 0ec378aa...7e6d34artifact ART-PR3B-1000-2 6fa207ed...ac0c08 → b8a27d0f...930e23
3
Requirement Capture AgentgbsIn progress

Holding at compare

2026-08-18 08:13:00ZAuthority PR3-AUTH-A1 · cap $250,000Jurisdiction SGAutonomy A3Retention PROC-7YLegal hold HOLD-003
Prompt
task-execution@p21
Policy
supplier-onboarding@v6
Tools
ledger-write@t7, document-fetch@t9
in bb56678d...e7d8fcout 20fb2e64...2dbb6eartifact ART-PR3B-1000-3 b8a27d0f...930e23 → e7e5489b...56f01d

Authority relied on

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

PR3-AUTH-A1ActiveSourcing Orchestrator

Any unit on a sourcing & rfx 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 · AUDelegated from Director, Strategic SourcingExpires 2026-12-05

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelextract-lite2.9currentPlatform model council
policysupplier-onboardingv6currentChief procurement officer
prompttask-executionp21currentShared service engineering
toolsetledger-writet7currentFinance systems
toolsetdocument-fetcht9currentShared service engineering

Gates on this line

The control points this unit had to clear

Escalate
Held for a named human when the unit exceeds the sourcing event decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Strategic Sourcing · not reached

Records schedule and holds

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

PROC-7Y7 years
Supplier and contract evidence
Contract limitation periods and public-sector supplier audit rights.
Deleted at seven years from contract expiry, not from record creation.
HOLD-003active
Supplier dispute — award challenge
An unsuccessful supplier has challenged an award on process grounds.
Custodian Head of Commercial Law · requested by Chief Procurement Officer

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 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.
  • 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.