📖About

Ninad (2026-07-03): the close-time Initiative Auditor finds unresolved findings but its Follow-on Filer (and the sibling out-of-scope filer) hand-build raw create POSTs whose auto-derived criteria the INI-2205 gate can reject as process-only - findings then land only as decisions and never become initiatives. Fix: route BOTH filers through Elronds Author (the Initiative Assembly droid), which drafts outcome-style success criteria that pass the gates - the same proven path the RSI loop and the retrigger use. Update cookbook 151 contract accordingly.

⚖️Decisions

• Auto-detected remediation target INI-999900446 from title/description scan (matched CAROL-INI-2205 -> row id 999900446 (CAROL-INI-2205-00: LLM-based criteria quality gate: reject process-only success )); 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)
• [HYGIENE GATE apps_registered] skip: work_type=None does not require app registration (orion.bypass)
• [HYGIENE GATE design_filed] skip: no design_id provided (orion.bypass)
• [HYGIENE GATE architecture_compliance] pass: references architecture design #146 (agent-centric modular architecture) (orion.bypass)
• [HYGIENE GATE policy_check] pass: considered: P.03.01.01.08 (orion.bypass)
• [HYGIENE GATE constitution_aligned] pass: soft-default pass; caller responsible for asserting via decision row (orion.bypass)
• [HYGIENE GATE cookbook_entry] pass: cookbook 151: Auto-file follow-on initiatives for actionable close-audit findings — via the Author (CAROL-INI-623/2250) (orion.bypass)
• [HYGIENE GATE logbook_entry] pass: logbook session 137: (orion.bypass)
• [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

• When an initiative closes with unresolved medium/high audit findings, a reader sees a NEW planner follow-on initiative in the initiatives list, drafted by the Author with gate-passing outcome criteria (must_have)
• Out-of-scope review findings likewise produce a visible planner initiative instead of a rejected-filing warning in the logs (must_have)