kami
0aefe021b0
Reasons are the auditable explanation of a pure decision, so one that describes the architecture rots the moment the architecture moves. The operational refusal asserted that manual interventions were recorded by no event type: true when written, false the day OperatorInterventionRecorded landed, and still printed under every refusal after that. It now reports the counts and the thresholds they missed. Why a count is zero is not this function's business, since no intervention happening, none being recorded, and none being migrated all read the same from here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CVbaKucEYBjMqVeUgJUsc1
orchestra ui mockups
final/ contains the nine accepted/current screen directions:
- dashboard
- task detail
- terminal live pane
- tasks
- decisions
- workers
- projects
- review
- settings
iterations/ contains every generated mockup from the design session, including superseded variants.
orchestra-ui-spec.md is the accompanying implementation/design specification.