Pages
Findings → SLA v1
Source: c79 finding-lifecycle — the interactive centerpiece · 2026-08-25
How a finding becomes SLA data, feelable: disposition a finding on the left and watch the audit feed append and every rollup on the right recompute — because nothing else exists to update. Advance the simulated clock to watch a finding cross its due date, and F-1022's exception lapse on 2026-10-01 and re-enter the queue mechanically.
now: 2026-08-17
Open · nearest due first
Accepted risk · clock paused
Recently closed
F-1035highToken spend anomaly — 6× baseline in one sessionresolved in 1d
F-0984lowHarness version drift — 4 minor versions behindresolved in 38d
F-1019mediumEgress to paste site blockedresolved in 0d
F-0973mediumMCP server with filesystem write outside workspaceresolved in 54d
F-0980mediumPrompt file contains customer identifiersresolved in 7d
F-0951mediumSession logs retained past policy windowresolved in 16d
Resolved within SLA
90%10 judged
4 open · 0 past target · 1 excepted
Found vs. resolved · derived from events
Quartercrithighmedilow
Q4 20251/11/11/10/1
Q1 20260/01/10/2 e11/1
Q2 20260/01/13/21/1
Q3 20260/01/21/41/1 e1
resolved / found · eN = excepted · a gap carries into next quarterAudit feed · the persisted record
2026-08-14 22:41F-1041detectsystem
2026-08-13 09:00F-1039acknowledgedanaFix merged, awaiting redeploy window
2026-08-13 08:10F-1039detectsystem
2026-08-12 16:12F-1038escalateravitracker:SEC-214
2026-08-12 16:10F-1038acknowledgeraviVendor security review scheduled 2026-08-19
2026-08-12 15:30F-1038detectsystem
2026-08-11 09:00F-1035resolvesystem
2026-08-09 14:02F-1035acknowledgefelix
2026-08-09 13:44F-1035detectsystem
Composition notes
- This page is c79's deliverable — the answer to c78's open thread ("the SLA report assumes a resolution workflow that isn't in the product"). Everything on the right rail is a fold over the event log on the left; acting appends one event, and the recompute is total because no other state exists.
- The demo arc: disposition F-1041 (exception with expiry, or escalate and watch the clock not care) → +30d to see a breach arrive and the verdict drop → keep advancing past 2026-10-01 to see F-1022's exception lapse and re-enter the queue with its remaining time preserved.
- Rubric is fixed here (Mark M's program) — the centerpiece demos lifecycle mechanics; the rubric's own knob lives on the config page. Two live knob-sets on one page splits attention.
- Simulated clock, never Date.now() — deterministic ages, SSR-safe, and the +Nd chips demonstrate more than a live clock could: due dates crossing, expiries lapsing, the verdict moving.
- Rulings and organs: anatomy · disposition panel · the SLA report this feeds. Reconciling that report onto this derived world is an open thread — its authored quarters are a bigger world than these event-derived ones.