📖About

Follow-on to CAROL-INI-2100. The step owner (Forge) and orchestrator (Merlin) now post to Palantir, but the in-step specialist phases do not: Sage spec author, Archon design author, Argus post-exec evaluator, Merlin task reviewer. Every agent that performs a task must record a Palantir activity regardless of task size. Fix in Merlin orchestrator po_s1.py: add a phase-post helper (resolve initiative from step, resolve agent from droid via registry owner with a prefix fallback) and call it from _record_phase_run (on completed/failed) and _run_argus_evaluation. Also register the unregistered in-process droids (Sage spec, Archon design, Merlin task reviewer) so attribution resolves cleanly and they are accountable. Albus review-time posting tracked separately.

⚖️Decisions

• Auto-detected remediation target INI-999900333 from title/description scan (matched CAROL-INI-2100 -> row id 999900333 (CAROL-INI-2100-00: Palantir wall shows only Elrond — per-step activity not recor)); override by setting remediates_initiative_id explicitly at bypass_start. (system-auto-detect)
• 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)
• Added a phase-post helper in Merlin orchestrator po_s1.py hooked into the phase recorder (covers Sage spec, Archon design, Merlin task reviewer) and into Argus post-exec evaluator; resolves initiative via the step and agent via registry-owner (prefix fallback). Registered the 3 previously-unregistered in-step droids (Sage spec, Archon design, Merlin task reviewer). Verified live on initiative 14: wall now shows Sage, Archon, Argus, Forge, Merlin + Elrond. Albus review-time posting is a separate path, tracked next. (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

• Sage spec, Archon design, Argus eval, and Merlin task-reviewer phases each post a Palantir activity under their own agent when they run (must_have)
• The previously-unregistered in-process droids (Sage spec, Archon design, Merlin task reviewer) are registered in the registry (must_have)
• Verified live: a phase post resolves to the correct agent (e.g. Sage->agt_025, Archon->agt_002, Argus->agt_003) (must_have)