📖About

Ninad flagged the blog 'Athena, Keeper of the Agents' as imaginative rather than factual: it claims Athena defines agent identity/role/org-chart placement, which is not her sphere. Root-cause chain: (1) Athena's agent-record prose and the Agent Resources service description still carry the pre-rename HR framing (onboarding, role definition, org chart), (2) the hand-written brief was composed from that stale prose plus imagination, (3) the Author path has no factual grounding gate - it trusts the brief entirely and only pictures get a review. Scope: add a registry-facts grounding gate to the Author path (subject agent/service facts injected; record outranks brief on ownership/scope claims); reconcile Athena's record and service description to her real sphere (service + tracks + objectives, guardian mandate per CAROL-INI-3746 retained); rewrite the Athena blog via the Author path from an honest grounded brief (operator-approved replace of a factually wrong story); regression test for the gate.

⚖️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)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] reviewing -> blocked | event=reviewer_verdict | bypass twin reviewer verdict != pass (CAROL-INI-2039) (orion)
• [status-router] blocked -> reviewing | event=operator_reopen | CAROL-INI-3752: the fail verdict graded a leaked 0-check probe row (exec 1369), not the real work; probe quarantined, re-review of standing attempt 1368 is PASS (3 checks, 0 failing) -> back to reviewing, awaiting UAT (orion)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=dispatcher_transition | dispatcher state change (ds-s1)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] reviewing -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [status-router] executing -> reviewing | event=dispatcher_transition | dispatcher state change (ds-s1)
• [delivery-check] 4 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (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

• author_blog.py grounds every agent/service-centred brief with the subject's live registry facts (agent record, owned service, tracks with objectives, droids) and instructs the Author that the registry outranks the brief on any ownership/scope claim (must_have)
• Athena's agent record (roles/duties/character/doctrine) and the Agent Resources service description no longer claim agent-identity/onboarding/org-chart authority; they state her real sphere: the Agent Resources service and its tracks (staff records and wellbeing, consciousness, chat, protocols), with the CAROL-INI-3746 guardian mandate retained (must_have)
• The Athena blog (Logbook session 361) is replaced through the Author path; every ownership/scope claim in the new posts matches the registry, and no post claims Athena defines agent identity (must_have)
• A regression test proves the grounding gate injects registry facts and flags a brief that contradicts them (must_have)