📖About

Give every initiative a STATUS and a STATE; drive all monitor cards purely off STATE. STATUS: planned, dispatched, executing, reviewing, closed, blocked, redirected (rename the legacy 'active' -> 'executing' everywhere; retire 'parked'). STATE (a pure function of status, = the monitor card bucket): planned->blank (hidden); dispatched->dispatched (Dispatched Queue card); executing->executing (Current Execution card); reviewing->executed and closed->executed (Recent Executions card); blocked->escalated and redirected->escalated (Escalation card). Semantics: planned=defined; dispatched=queued for automated execution when its turn comes (placeholder, Orion-manual for now); executing=running; reviewing=successfully executed, awaiting UAT; closed=UAT passed (active sign-off or Orion-bypass auto-sweep); blocked=execution failed OR UAT failed; redirected=policy unclear or violated. The status-router becomes the single mutator that sets (status,state) together and writes a Palantir wall entry whenever the card (state) changes, attributed to Elrond. Add the state column + backfill from status. Successfully-executed-awaiting-UAT (reviewing) shows in Recent Executions (not Current). Unsuccessful (execution-fail or UAT-fail per cookbook criteria) -> blocked + Escalation. Clear today's 4 false blocks (work verified done) under the new model. Update the cookbook with the status x state x card model. Regression tests.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> active | event=bypass_active | bypass transition (or-bx-01)
• [status-router] active -> executing | event=operator_put | 1938 active->executing (orion)
• Caller audit waived by Orion: this initiative edits shared/bypass.py (initiative-status active->executing strings only) plus the status-router, monitor, watchdog, and ini128 guards; it does not change bypass-runtime call semantics. The caller-audit gate is a fleet-wide false-positive when bypass.py shows uncommitted edits (cookbook 203). — bypass.py change is limited to the initiative-status literal (active->executing); no caller contract changed. (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)
• Orion remediated: INI-999900310 bypass closed — CAROL-INI-696 close-marker: the Orion bypass INI-999900310 filed against this parent reached terminal state (closed). This row's literal prefix Orion remediated: is the canonical signal the cookbook-155 dispatcher gate looks for. (shared.bypass.bypass_end)

✅Success criteria

• every initiative has a state column that is a pure function of status (planned->blank, dispatched->dispatched, executing->executing, reviewing/closed->executed, blocked/redirected->escalated) and is backfilled for all rows (must_have)
• the legacy active status is renamed to executing across initiative code and rows; no initiative remains in active (must_have)
• the status-router is the single mutator that sets status and state together and writes a Palantir wall entry whenever the card (state) changes (must_have)
• all four monitor cards are driven purely off state: dispatched->Dispatched Queue, executing->Current Execution, executed->Recent Executions, escalated->Escalation; planned hidden (must_have)
• reviewing initiatives appear in Recent Executions (not Current); execution-fail and UAT-fail route to blocked/escalated (must_have)
• the cookbook documents the status x state x card model and a regression test covers the status->state->card mapping (must_have)