📖About

Root cause: palantir_record_activity assigns sequence=MAX+1 at the moment of the code call and the wall renders ORDER BY sequence, so report order == code-call order, with no link to when work actually happened. Any post placed before/after its real work desyncs the wall (the Forge-at-start bug was a symptom). Structural fix for ALL agents: (1) order the wall by real event time (created_at) with sequence/id as tiebreak so display is time-driven not counter-driven; (2) codify the contract in cookbook 228 — every agent posts AT COMPLETION (the post is the completion record, never a pre-announcement), emitted through the shared activity recorder, wall is time-ordered. Future step: render the wall directly from the canonical activity log (droid_runs/session_events) so order cannot drift.

⚖️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 -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Root cause of report-order drift: Palantir assigned sequence=MAX+1 at insert and the wall rendered ORDER BY sequence, so report order == code-call order with no link to real event time. Fix: wall now ORDER BY created_at (real time) then sequence/id tiebreak; cookbook 228 amended with the report-at-completion + time-ordered + single-emit-point contract for all agents. Verified: initiative 14 wall renders in time order. INCIDENT during this work: data/registry.db was found clobbered to a 12KB stub (only incoming_requests); restored from a complete copy (42 agents/230 droids), re-registered 3 session droids, safety backup saved. Clobberer not statically pinpointed — same class as the initiatives-db stray-writer stub; registry has no single-writer guard. (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)

✅Success criteria

• Palantir wall renders posts ordered by real event time (created_at) with sequence/id tiebreak, not by insert-counter alone (must_have)
• Cookbook 228 codifies the report-at-completion timing contract (post is the completion record; emitted via the shared recorder; wall is time-ordered) (must_have)