📖About

Ninad (2026-07-19 ~04:45, CLI-059): SECOND same-day case of an initiative family reaching all-terminal with the objective undelivered, silently. Case 1: 2982 (block completion — 6310 loop). Case 2: 2735 — the refile (-02) was auto-closed as no-longer-relevant because the relevance judge saw the closed -00 twin BY TITLE ONLY, not knowing that close was a UAT rejection with the outcome unmet; the family then died with 1 of 2 real blueprint requests half-converted, 1 untouched, and a junk project created. Fix A: the relevance and filing-validity judges annotate same-family closed/reviewing entries with the Outcome Oracle verdict (outcome MET vs OUTCOME NOT MET) and both prompts carry the rule that a not-met close never makes a refile stale or already-met. Fix B (protected core, operator lane): after the status router takes a family member terminal via a plumbing event (stale_irrelevant, filing_validity_reject, attempt_superseded, premise_dead), if NO live family member remains and the Outcome Oracle says the objective is unmet, the router posts a decision + an escalation so the death is VISIBLE on the queue — never silent. No auto-refile (loop safety); visibility first.

⚖️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)
• Current state at filing (Elrond validity check): The filing-validity and relevance judges currently use title-only matching and do not consult the Outcome Oracle verdict to distinguish a UAT rejection from a successful close. When the last live family member is taken terminal by a plumbing event and the objective is unmet, no escalation is posted — families die silently. The fixes described in the filing have not been implemented in any completed initiative. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• CLI-060 induction evidence (Orion, 2026-07-19): CAROL-INI-2993 (ringfence v2) is a SECOND live family-death case for this rule. Sequence: Leo's agent-UAT rejected -00 round 2 with criteria NOT met (policy scans not zero-violation; Fable replies outside the chat lanes) -> blocked -> Albus RSI GROUP diagnosis attached the unrelated 2735 blueprint findings to it -> the next attempt was rejected at filing as already_met (claiming the policies ARE enforced, contradicting Leo's live verdict) -> family discarded with the objective unmet, before this rule's guard shipped. Needs an operator ruling: refile the ringfence verification or accept the discard. (orion)
• [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

• A refile of work whose earlier attempt closed with the outcome NOT met is no longer auto-closed as duplicate or already-met — the judges see the outcome verdict and let it build. (must_have)
• When plumbing takes the last live member of a family terminal while the objective is unmet, Ninad sees an escalation naming the family and the unmet objective — no family dies silently anymore. (must_have)