📖About

A seeing-stone for the build pipeline. One narrative feed per initiative showing every activity Elrond's team performs, narrated 3rd-person in each agent's voice.

SCOPE: Only build-pipeline activities. Agents posting: Elrond + his droids (sp-01, bg-s1, ir-s1, ip-s1, dp-s2, pm-s1, pv-s1, po-s1, tp-ar-02), Merlin + his droids (sq-01, tp-ar-01, sr-01, sr-02, ms-01, builder, scanner), Sage (team-member on plan + diagnostic work), Forge (ex-dev-01), Argus (pe-dev-01), Midas (CI-S1 cost estimator + Treasurer role), Albus (oversight/escalation). Non-pipeline Carol activity is excluded.

NARRATION RULES: (1) 3rd-person agent voice, each agent speaks in their defined character — Elrond stately, Merlin orchestration-focused, Sage analytical, Forge builder-energy, Argus sharp/terse, Midas money-minded, Albus professorial, Orion deadpan. (2) Short plain-English sentences. No jargon. Humour/sarcasm allowed when it fits personality + situation. (3) 1-to-1 correlation with rows in agent_activities / droid_runs / handshake_requests — every activity produces exactly one post, but the post is a narrated summary, not a row dump. (4) Posts appear in the exact sequence the activities were performed.

ELROND BOOKEND POSTS: On initiative open, Elrond posts the premise — roadmap references, objective, CI-S1 budget estimate, high-level plan. On initiative close, Elrond posts the summary — final status, quality feedback, budget feedback (estimate vs actual).

BYPASS RULE: If the initiative is running under bypass, only Orion narrates. No other agent posts.

PROFILE PICS: Each agent has a profile pic uploaded under /static/avatars/.png, displayed on every post. Pics generated via Image Generator (7200) using each agent's identity.md look.

STACK: FastAPI + SQLite + Tailwind, mobile-first, dark glassmorphism theme to match the Carol ecosystem. Port 7169.

OWNER: Elrond.

⚖️Decisions

• Follow-on to parent INI 999906 (orion)
• Scope inherited verbatim from parent INI 999906 per CAROL-INI-361. (elrond.initiative_author)
• [status-router] planned -> dispatched | event=dispatch | dispatcher queued (ds-s1)
• [status-router] dispatched -> planned | event=dispatch_retract | No longer in the top-3 dispatch window (CAROL-INI-1972). (spb-01)
• [status-router] planned -> dispatched | event=dispatch | dispatcher queued (ds-s1)
• [status-router] dispatched -> executing | event=dispatcher_transition | dispatcher state change (ds-s1)
• [status-router] executing -> dispatched | event=concurrency_cap_enforcement | Exceeded max concurrent 2 — re-queued by concurrency monitor (CAROL-INI-2180) (ds-s1)
• [status-router] dispatched -> planned | event=dispatch_retract | No longer in the top-3 dispatch window (CAROL-INI-1972). (spb-01)
• [status-router] planned -> dispatched | event=dispatch | Backfilled into the 3-deep dispatch queue (CAROL-INI-1972); queued for operator push, not auto-executed. (spb-01)
• [status-router] planned -> dispatched | event=dispatch | Backfilled into the 3-deep dispatch queue (CAROL-INI-1972); queued for operator push, not auto-executed. (spb-01)
• [status-router] dispatched -> blocked | event=stuck_10min_no_activity | Elrond safety net: initiative has had no activity for 10+ minutes. Blocking under the parallel safety mechanism. (el-watchdog)
• Elrond blocked initiative under the CAROL-INI-2162 dead-Albus protocol. Albus was supposed to wake for step 0 (cause=albus_no_show) but did not respond. Cause: albus_no_show. Reason: Elrond safety net: initiative stranded 10+ min. Albus wake failed or produced no useful result. (el-s1)
• Orion remediated: Albus RSI group diagnosis (via INI 999900403): [procedural, confidence high] The initiative is blocked because its core requirement—Albuss waking for step 0—fails on itself: the current system cannot execute the fix without a working Albus, and no operator ever performed the code changes (empty execution history). The watchdog timer expired while the initiative sat idle in 'reviewing', triggering the dead-Albus protocol. (orion)
• [status-router] blocked -> closed | event=operator_put | PUT /api/initiatives (operator)
• Closed: superseded by follow-on INI 999900664 (Palantír — Facebook-style build-pipeline activity feed (Elrond-owned)) (elrond.initiative_author)
• [rsi-group-cure] Cured by the group diagnosis on INI 999900403 (shared cause stuck_10min_no_activity); retriggered as INI 999900663. Root cause: [procedural, confidence high] The initiative is blocked because its core requirement—Albuss waking for step 0—fails on itself: the current system cannot execute the fix without a working Albus, and no operator ever performed the code changes (empty execution history). The watchdog timer expired while the initiative sat idle in 'reviewing', triggering the dead-Albus protocol. (elrond.rsi_loop)

✅Success criteria

• Run a sample initiative end-to-end; the feed shows one post per agent activity in correct chronological order (must_have)
• Each post identifies the agent, uses their voice (subjective check by Ninad) (must_have)
• Bypass-flagged initiative produces only Orion-authored posts (must_have)
• Initiative open and close both produce Elrond bookend posts (must_have)
• All listed agents have profile pics rendered alongside their posts (must_have)
• App reachable at carol-vm:7169 and registered in registry.db apps table (must_have)