LensReading which lens this session carries.

Auditor evidence pack

Escalated case at draft findings

Customer Service · Tier-2 Technical · line CS3C · Recurring Issue Analysis.

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-005

The unit

What the work was, and where it sits

Reference
CS3C-1011
Subject
Nadia Lindqvist
Requested by
Oscar Ito
Value
$1.3m
Materiality
high
Currently held by
Diagnostic Agent (agent)
Sub-function owner
Director, Technical Support
Orchestrator
Tier-2 Technical Orchestrator

Every action, in order

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

1
Diagnostic AgenttaskCleared

Cleared cluster cases

2026-08-17 14:23:00ZAuthority CS3-AUTH-A1 · cap $2,000,000Jurisdiction SGAutonomy A3Retention CUST-5YLegal hold HOLD-005
Prompt
task-execution@p21
Policy
customer-commitments@v5
Tools
document-fetch@t9, read-only-lookup@t12
in 8b0a93f7...e16154out bf5a3e63...fd8387artifact ART-CS3C-1001-1 genesis → d99510f6...fd2881
2
Log Analysis AgenttaskCleared

Cleared quantify impact

2026-08-17 20:35:00ZAuthority CS3-AUTH-A1 · cap $2,000,000Jurisdiction SGAutonomy A3Retention CUST-5YLegal hold HOLD-005
Prompt
task-execution@p21
Policy
customer-commitments@v5
Tools
document-fetch@t9, read-only-lookup@t12
in 801b9c5b...77c058out 4b6dfdd1...a57582artifact ART-CS3C-1001-2 d99510f6...fd2881 → 691181bf...4700f6
3
Reproduction AgenttaskIn progress

Holding at draft findings

2026-08-18 02:48:00ZAuthority CS3-AUTH-A1 · cap $2,000,000Jurisdiction SGAutonomy A3Retention CUST-5YLegal hold HOLD-005
Prompt
task-execution@p21
Policy
customer-commitments@v5
Tools
document-fetch@t9, read-only-lookup@t12
in 834cc80d...e9853fout 13b01cb4...60c476artifact ART-CS3C-1001-3 691181bf...4700f6 → 089debcb...4c5a8b

Authority relied on

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

CS3-AUTH-A1ActiveTier-2 Technical Orchestrator

Any unit on a tier-2 technical 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, Technical SupportExpires 2026-11-12

Versions in force

Exactly what was running when these actions were taken

KindIdentifierVersionStatusOwner
modelextract-lite2.9currentPlatform model council
policycustomer-commitmentsv5currentChief revenue officer
prompttask-executionp21currentShared service engineering
toolsetread-only-lookupt12currentPlatform engineering
toolsetdocument-fetcht9currentShared service engineering

Gates on this line

The control points this unit had to clear

Review
Held for a named human when the unit exceeds the escalated case decision envelope, when confidence falls below the floor, or when a policy clause is engaged.
Approver: Director, Technical Support · not reached

Records schedule and holds

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

CUST-5Y5 years
Customer commitment and service evidence
Consumer claim windows and revenue recognition audit trail.
Deleted at five years from the last account activity.
HOLD-005active
Customer complaint escalation — service credits
A pattern of service credit refusals was raised with a consumer regulator.
Custodian Head of Consumer Law · requested by Chief Customer 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.