STD-01 Evidence Pack
Tiered evidence requirements for the Temporal Bill of Rights with anti-fraud and audit guidance.
Proof-carrying compliance
Tiered evidence for temporal rights
STD-01 proof bundles align with clause IDs so auditors can validate obligations without guesswork.
Tiered evidence model
Tier 0 to Tier 2 minimum
Start at Tier 0 for baseline proof, then scale to Tier 2 for resilience.
- Tier 0 (minimum): System outputs that prove the clause is instrumented. Event logs, UI snapshots, and receipt payloads.
- Tier 1 (operational): Evidence the control is used and reviewed. Decision logs, appeal outcomes, reviewer rosters, and clock compliance reports.
- Tier 2 (resilient): Stress-tested proof that controls survive real incidents. Incident postmortems, drill results, and remediation follow-through.
Clause evidence list
Evidence packs per clause
Each clause lists the minimum evidence bundle required for proof-carrying compliance.
-
STD-01.1.1 (§1.1) — provide a visible, universally accessible halt control when active automated process is in progress.
Evidence: ui_control, event_log -
STD-01.1.2 (§1.2) — preserve the paused state for return without penalty when a process is halted by the user.
Evidence: state_snapshot, retention_policy -
STD-01.1.3 (§1.3) — offer a permanent exit option on every screen when user is in a multi-step flow.
Evidence: ui_state, interaction_map -
STD-01.2.1 (§2.1) — allow exit with equal or less friction than entry when user seeks to end a relationship with a system.
Evidence: journey_map, time_cost_log -
STD-01.2.2 (§2.2) — exit requires no more than one step when entry required a single step.
Evidence: journey_map, ui_state -
STD-01.2.3 (§2.3) — avoid mandatory retention scripts before exit when user initiates resignation or cancellation.
Evidence: journey_map, policy -
STD-01.3.1 (§3.1) — set hard clocks for each state when process includes pending, processing, or review states.
Evidence: system_sla, event_log -
STD-01.3.2 (§3.2) — provide a failure response or human escalation when timeout threshold is reached.
Evidence: escalation_policy, event_log -
STD-01.3.3 (§3.3) — declare expected duration before commitment when user is asked to commit to a process.
Evidence: ui_copy, journey_map -
STD-01.4.1 (§4.1) — provide an undo window for reversals when user performs a consequential action.
Evidence: ui_state, policy -
STD-01.4.2 (§4.2) — use non-destructive defaults with soft-delete when system deletes or removes content.
Evidence: data_retention_policy, event_log -
STD-01.5.1 (§5.1) — show queue position and expected wait time when user is waiting in a queue or hold state.
Evidence: ui_state, queue_metrics -
STD-01.5.2 (§5.2) — avoid fake progress indicators or placebo signals when system reports progress or waiting status.
Evidence: ui_state, event_log -
STD-01.5.3 (§5.3) — offer asynchronous options when wait time exceeds five minutes.
Evidence: ui_state, journey_map -
STD-01.6.1 (§6.1) — provide a defined escalation path to a human when automated denial or escalation request occurs.
Evidence: policy, support_workflow -
STD-01.6.2 (§6.2) — operating institution accepts liability when automation impacts a user outcome.
Evidence: policy, governance_record -
STD-01.7.1 (§7.1) — measure and publish the time tax when system imposes compliance or usage burden.
Evidence: burden_report, time_cost_log -
STD-01.7.2 (§7.2) — include burden as a reportable metric when governance metrics are tracked.
Evidence: governance_dashboard
Anti-weaponization evidence
Evidence requirements for AW-01 through AW-04
Treat anti-weaponization clauses as enforceable audit requirements.
- AW-01: Burden metrics report + resourcing plan for the next window.
- AW-02: Appeal path regression tests + replacement notice evidence.
- AW-03: Receipts + clock compliance for downgrades and eligibility changes.
- AW-04: Assisted channel SLA + staffing roster for high-burden flows.
Link the constraints in Anti-weaponization to STD-01 clause evidence bundles.
How teams fake this
Common compliance theater patterns
Use these patterns to catch hollow compliance before audits do.
- Receipts exist but omit owner, clocks, or appeal path.
- UI screenshots are staged once and never updated after release.
- Event logs exist but are not tied to decision log entries or remedy outcomes.
- Kill switch drills are logged without showing the actual halt time or restoration proof.
What auditors ask
Audit questions to prepare for
Answer these with links to the clause evidence list and decision records.
- Show the last five receipts for halted flows and their remedy outcomes.
- Provide evidence that exit paths match entry friction across the top three flows.
- Demonstrate a recent kill switch drill and its time-to-halt measurement.
- Explain how exceptions are reviewed and how long they lasted.
Referenced by
Where STD-01 evidence is enforced
Cross-links keep evidence packs, examples, and bindings aligned.
Used in examples
Required by bindings
Verified by evidence packs
Search IDs: STD-01 v1.0, STD-01.1.1, STD-01.5.1, AW-01, AW-02, AW-03, AW-04, VAL-01.