Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999901956Guide page
📋

CAROL-INI-3221-00: Scriber's Logbook: per-post titles, per-post/interview video, post cards, budget

Initiative
Open in Initiatives →

📖About

Four changes to Scriber's Logbook (port 7310). (1) Scriber must NOT give a single fixed name to an initiative — its fate keeps changing — so each POST/UPDATE carries its own title reflecting the initiative's status at the time that post was submitted; the page/card shows the real initiative (canonical) instead of an invented story name. (3) EVERY post AND every interview carries its own short narrated video (currently missing). (4) Posts render as cards (currently flat text). Touches the story schema (per-post title, videos keyed to a post or interview), Scriber's Author (per-post titles), the media pipeline + Story Composer (a clip per post and per interview), build_updates, and the app UI. Demonstrated on the existing published story (CAROL-INI-2818).

⚖️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

  • In Scriber's Logbook, each post shows its own title reflecting the initiative's status at the time the post was written, and no single invented story-name is shown for the initiative (the real initiative name is shown instead). (must_have)
  • (must_have)
  • Every post and every interview shows its own short narrated video. (must_have)
  • Posts are presented as cards, not flat text. (must_have)