Break the Chain (staging)
Agent: Proofroom Security Agent · Operated by Proofroom · Accountable human: Proofroom Operator
Scope confirmed by Proofroom Operator on 2026-09-15.
Last verified 2026-10-01 00:31:07 UTC · Last evidence 2026-09-15 16:10:01 UTC
Chain verified ✓, 1 events · Receipts: 1 recorded / 1 expected · Integrity incidents: 0 · Evidence altered: no · Public verify JSON · Site integrity log
This is one of Proofroom's own internal agents. The company runs on the product it sells: this room is the live, public audit trail of that claim.
Declared scope
Public staging target for forge/tamper/idempotency challenge attempts. Recognition only; no cash bounty.
Allowed actions
- accept challenge attempt records
- publish hall-of-fame chain events
- verify chain integrity for challenge demos
Declared but never recorded: accept challenge attempt records; publish hall-of-fame chain events; verify chain integrity for challenge demos.
Prohibited actions
- accept production customer evidence
- pay cash bounties
- rewrite stored hashes
Oversight model
operator review of accepted findings
| Action | Tier |
|---|---|
| security.rotate_key | approval |
| security.dependency_upgrade | approval |
| security.send_report | autonomous |
| security.disable_logging | forbidden |
| security.modify_rls | forbidden |
Active playbook: version 3, SHA-256 f005f10e7a104f2f…
Trust signals
Three independent signals — not one score. A perfect bar in one column cannot hide a caveat in another. Interpreted under capture grade Instrumented (SDK middleware wraps actions).
Integrity
Chain intact
1 events recomputed; 0 integrity incidents on record.
1 events · 0 incidents
Evidence strength
Operator-confirmed evidence present
operator confirmed: 1
operator confirmed
Coverage
0 of 3 declared behaviours observed
Not yet observed: accept challenge attempt records; publish hall-of-fame chain events; verify chain integrity for challenge demos.
0/3 declared
Legacy coverage rubric (checklist detail · not a single verdict)
- Declaration completeness10/10
Scope summary, allowed actions, prohibited actions and oversight model declared on the passport.
- Chain integrity20/20
All 1 events recomputed successfully.
- Evidence freshness15/15
Last event 368 hours ago against a 90-day decay window.
- Activity depth0/15
1 events recorded (full marks at 50 or more).
- Material action coverage15/15
1 of 1 material actions carry receipts.
- Source strength bonus2/5
Evidence includes confirmation beyond self-reporting.
- Configuration provenance declared5/5
Provenance level: externally anchored.
- Identity and accountability15/15
Scope confirmed on 2026-09-15.
Chain integrity
Checked under verifier v1.2. We never rewrite evidence to heal a chain.
Receipts: 1 · First 2026-09-15 16:10:01 UTC · Last 2026-09-15 16:10:01 UTC
By type: system updated (1)
By authority: in scope (1)
By evidence level: operator confirmed (1)
Every event hash covers the previous event's hash. Editing any past event breaks every hash after it.
Chain head last anchored externally: 2026-09-30 02:02:20 UTC (anchor file). See also how to verify independently.
Integrity history
Every change in reported chain state is recorded here, in both directions. Free on every plan. Never hidden after resolution.
No integrity incidents recorded.
Action Receipts
1 receipts across the full history. Dates, receipt ids, event types and authority statuses stay visible on every plan.
Room history
Claim, scope versions, configuration changes, integrity incidents and corrections in one timeline. Scope covers what is permitted; configuration covers how it works.
No claim, scope, configuration, integrity or correction entries yet.
Configuration history
Structural facts only: when the declared configuration fingerprint changed.
No configuration changes recorded yet.
Framework crosswalk
Framework references indicate topical mapping between this evidence trail and themes in the named frameworks. They do not indicate certification, attestation or compliance with any framework.
ISO 42001
- A.6.2 (AI system life cycle)
Defined scope and intended use of the AI system
Mapped by: Use case passport: scope summary, allowed and prohibited actions
- A.9.2 (Processes for responsible use)
Human oversight of AI system operation
Mapped by: Oversight model and executable decision-rights tiers with approval trail
- A.6.2.8 (Event logging)
Recording of AI system activity
Mapped by: Append-only, hash-chained evidence events with sequence integrity verification
- A.8.2 (System documentation)
Information available to interested parties
Mapped by: Live proof room, Action Receipts and Evidence Pack with declared evidence levels
SIG
- AI module: governance
Inventory and ownership of AI agents
Mapped by: Agent passport with accountable human and registered use cases
- AI module: operations
Monitoring and exception handling for automated agents
Mapped by: Run ledger, spend caps, exception events and operator escalation receipts
CAIQ
- AIS (Application and Interface Security)
Audit trail of application actions
Mapped by: Action Receipts with authority status and tamper-evident chain
- GRC (Governance, Risk and Compliance)
Documented risk boundaries for automated systems
Mapped by: Prohibited actions, forbidden decision tiers and kill-switch evidence
NIST
- AI RMF: Govern
Accountability structures for AI systems
Mapped by: Accountable human on every internal agent; approvals resolved by named operators
- AI RMF: Measure
Tracking of AI system behaviour over time
Mapped by: Evidence Coverage Score with component breakdown and status decay
- AI agent guidance: least privilege
Constraining agent capabilities to declared scope
Mapped by: Tool allowlists, decision-rights tiers and out-of-scope receipt flagging
What this room does not verify
- The score measures the presence, integrity and freshness of an evidence trail, not agent quality.
- It does not certify accuracy, bias, legality or fitness for purpose.
- Self-reported events depend on the honesty of the submitting system.
- Configuration provenance records that the agent's declared configuration changed and when. A self-declared fingerprint does not evidence that the declared configuration is what actually ran. Only externally anchored identifiers, confirmed against their source system, approach that.
- External anchoring proves this chain head existed at the anchor time. It bounds any retrospective alteration to the period since the last anchor. It does not prove that events recorded before an anchor were genuine at the moment they were reported.
- This trail evidences what was recorded. It cannot evidence actions the agent did not report. Evidence completeness depends on the agent's instrumentation, not on this record.
- We never rewrite evidence. Where stored evidence was wrong, we append a correction and the original remains visible. A chain may therefore show a permanent, explained discontinuity. We regard that as more credible than a chain that appears to heal.
- A chain's verification state can change because stored evidence changed, or because our verification code changed. These are entirely different events and we record which one occurred, in both directions, permanently. Where an externally anchored chain head predates an incident, we compare against it and publish the result.
- Evidence sources: system (1). Evidence levels: operator confirmed (1). Declared but never recorded: accept challenge attempt records; publish hall-of-fame chain events; verify chain integrity for challenge demos.
Proofroom provides evidence of declared agent scope and submitted activity events for a specific use case. Verification status indicates the presence, source level and integrity of an evidence trail. It does not certify that the agent is accurate, unbiased or suitable for all uses. Evidence completeness depends on the sources connected and events submitted. Framework references indicate topical mapping, not certification.
Live room: status decays without fresh evidence. Generated by Proofroom.