📖About

Scriber's Author writes each Logbook story straight from raw records (decisions, Palantir narration, review verdicts). He has NO investigation step, so he narrates misleading surface labels at face value - e.g. his 2818 story concluded 'the architect simply didn't wake up, an unanswerable absence' when the truth was Albus's run hit the tool-round/token wall and the real break was the developer being handed root-only work. This gives Scriber his own Albus-style investigator: a read-only root-cause dig (Read/Grep/Glob tools over the real code + logs, evidence scrubbed of the self-heal loop's own chatter, anchored on the FIRST real block cause) that separates symptom from root cause and feeds a grounded INVESTIGATION FINDINGS section into the Author's material. Fail-open: if the dig can't run, the story still composes.

⚖️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)
• [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

• Before Scriber publishes a story about a stuck initiative, a root-cause investigation runs and separates the real cause from misleading surface labels. (must_have)
• Scriber's story reflects the real root cause rather than a surface label taken at face value. (must_have)
• If the investigation cannot run, Scriber still composes and publishes a story with no regression. (must_have)