📖About

Align Palantir posts to cookbook 108/80/228/237. THREE fixes: (1) EVIDENCE_MISSING (truthfulness gate 237): the per-phase posts and Albus conformance pass no evidence; pass a concise evidence trace (phase result_summary / Argus verdict / conformance violations) so task_evidence is populated. (2) NO_DECISION_TRACE on Elrond Filing Gate refusals: the gate posts a refusal narrative but writes no initiative_decisions row; add a decision row on refusal so the post has a trace. (3) SEQUENCE: the step-owner (Forge) post fires at step start before Sage/Archon, violating cookbook order Sage->Archon->Forge->Argus; move the Forge build post to Forge actual dispatch point (after Archon) and keep only Merlin pickup at start.

⚖️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)
• Three Palantir cookbook-alignment fixes, verified live: (1) EVIDENCE — phase posts (po_s1), Argus eval, and Albus conformance now pass an evidence trace; evidence-carrying posts no longer trip EVIDENCE_MISSING. (2) DECISION TRACE — Filing Gate now writes an initiative_decisions row (and evidence) on refusal; new refusals pass NO_DECISION_TRACE (only 2 historical pre-fix posts remain flagged). (3) SEQUENCE — moved the worker/Forge post from step-start to the actual build dispatch (after Sage+Archon), so wall order follows cookbook 108 Sage->Archon->Forge->Argus; kept only Merlin pickup at start. Cleaned 16 verification test posts off initiative 14 wall. Loads on next step spawn. (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

• Per-phase + conformance Palantir posts populate task_evidence; truthfulness audit no longer reports EVIDENCE_MISSING for new posts (must_have)
• Filing Gate refusal writes an initiative_decisions row so the refusal post passes NO_DECISION_TRACE (must_have)
• Per-step Palantir post order matches cookbook 108: Sage -> Archon -> Forge -> Argus (Forge no longer posts before Sage/Archon) (must_have)