Pages
Finding Disposition v1
Source: c79 finding-lifecycle — the disposition organ across its states · 2026-08-25
The working-surface organ: one finding row that expands into the verb row, mandatory-reason capture, and the seam stubs. The verbs actually work — each scenario carries its own event log; acting appends to it and the panel re-derives. Ticketing and policy are one-line stubs by design: escalate and enforce stamp a ref and change nothing else.
Detected yesterday, nobody has looked yet — the full verb row is live, acknowledge included.
API key pasted into agent prompt
S-0101highopen 0d / 30d target · due 2026-09-15
Claude Code · dana
Adjudication :
Audit record · appends live
2026-08-16 14:20detectsystem
Composition notes
- The panel owns no state machine — it renders a DerivedFinding and emits act; the page appends the event and re-derives. Same contract on the findings-to-sla centerpiece.
- Mandatory fields gate submission — ignore/reopen need a reason, exception needs reason + expiry (defaulted to +30d). Acknowledge and the system resolve are one click; they capture nothing.
- Seam discipline: escalate and enforce render one inline line and stamp one ref. The moment a stub grows a second affordance (assignee, comment, status sync) it's workflow tooling the customer already owns.
- "simulate: fix detected" is visually apart from the verb row — resolution is evidence, not judgment. It's the only green affordance on the panel.
- Verb availability by status: open findings take the five verbs; everything else offers only reopen (and evidence can still clear an excepted finding).