Albus's bypass execution lane — the Albus Bypass Runner picks the oldest abandoned planner initiative, flips it to bypass mode, claims it and completes it end-to-end on Claude Fable.

Archon's imagery, video, portrait, gallery and design-alignment droids serving the build pipeline.

Estimating effort: Elrond reads an initiative attempt's own record and estimates the tokens it needs to complete, recorded on the attempt with its source.

Executing the step — the build itself: analysis and spec-writing, design and dev work, and the executor/runner orchestration that turns plans into delivered code, with each role submitting its deliverable.

Filing an initiative — turning a request into a well-formed initiative: drafting it, authoring its requirements and initiative-level design, and running the filing-invariant and pre-flight validity gates before it goes active.

Scriber's creative track: turns the real incident history of planner initiatives into funny, honest, philosophical stories (hero image + narrated video) published to Scriber's Logbook. Opinion, not verdict - Elrond owns the verdict. Planner-mode initiatives only.

Judging the initiative — aggregating all gate signals into a stance (continue / replan / close / escalate) and running the close decision and its post-commit hooks.

Monitoring the execution — watching pipeline health: detecting dead or stuck processes, checking agent-droid wellbeing, and verifying the watchers themselves.

Orion's bypass execution lane — the operator CLI claims an initiative, works it through the bypass methodology (template, design, code, test, twin review) and closes it into UAT. Runs on the Claude Max subscription.

Planning an initiative — producing the initial whole-initiative plan and the compiled planning artifact before step work begins.

Planning the execution of a step — detailed per-step planning against the S-checklists, plus review of those step plans for accuracy and policy compliance.

The pipeline's self-improvement machinery: the RSI loop, collectors, pattern watcher, success and uptime measures.

Replanning the initiative — re-planning blocked or changed steps mid-flight and running the review-fail rework and cross-group redirect loop. Optional block.

The escalation-ladder rung where Albus takes a failed planner family to completion as a bypass, and Elrond's urgent escalations. The work DECLARES itself (planner_escalated work kind) so the money lands here whoever runs it.

Reviewing the initiative — judging the whole initiative once its steps are done, inferring the reviewing transition and grading bypass work against its success criteria.

Reviewing the step — verifying the delivered step against its plan, success criteria, design standards and the regression gate before it advances.

Generates the hero image and the narrated video for a Logbook post. Renamed from 'Media Generation' (Ninad, 2026-08-02): it is named for where the work lands, and it lands in SCRIBER'S Logbook, not Orion's.

Deciding which filed initiatives the build pipeline works on next, and when. Sprint Planning turns the backlog of filed-but-unstarted planner initiatives into daily sprints (SPR-yyyy-mm-dd) ordered by ETA, packed. Urgency is filed by the initiator; effort and ETA are derived and maintained by Elrond. Unfinished work rolls into the next day with a fresh ETA. Planner-mode only.

Support — the always-on backbone that serves every other block: the dispatch/orchestration engine, the bypass engine, admin and deployment, shared template and design libraries, app-stewards, and cross-stage activity reporters. Not part of the file->...->uat chain.

Troubleshooting the initiative — triaging pipeline failures and auto-remediating them, including frontend fixes, resume/escalation of parked work, and retriggering fixed initiatives. Optional block.

User Acceptance Testing is the final gate that confirms an initiative's reviewing work actually does what was asked — and crucially, WHO performs it depends on WHO triggered the initiative. Manual lane (today): initiatives Orion drives — both his planner runs and his bypass work — are accepted by Ninad himself. Operator-directed work has no deterministic failing trigger to replay, so a human signs it off; nothing closes until Ninad confirms it. Automated lane (today): when an initiative was triggered by a concrete, replayable failure, UAT is the act of re-exercising that exact failure and confirming it now passes — no human needed. For Albus's bypass work, which is always triggered by a specific pipeline failure, UAT means the triggering failure is rectified and then the failed execution is RE-RUN as part of acceptance — it passes only if that rerun now succeeds. For Hermione's planner executions, which arise from a failed scheduled process, UAT means the process that failed is RE-RUN — the initiative is accepted only if that rerun completes successfully. Future autonomous lanes: as more agents gain authority to trigger initiatives, they will own their own UAT the same way — if Leo or Noah triggers an initiative, that agent performs the UAT autonomously, replaying whatever it was that triggered the work and confirming the fix holds. The principle is uniform: automated UAT re-runs the precise thing that caused the initiative and accepts only on a clean rerun; manual UAT is reserved for operator-directed work that has no such trigger to replay. UAT currently has no droids of its own — it is performed by the triggering agent (or by Ninad).

Albus's bypass lane: the Albus Bypass Runner picks up planner initiatives the self-heal loop abandoned and completes them as bypasses on Claude Fable. Owned by Albus.

Elrond's line: the governance of the estate's one build pipeline - intake and filing (the filing gate, topic tagging, initiative creation, sizing), review gates and verdicts (the security gate, review and validation), acceptance (UAT), effort sizing, the pipeline's watch and measurement droids, and the register of the build's outcomes that he answers for (designs, specs, tests and build reports produced under his tasks, by whichever agent's droid served them). Every task Elrond owns folds here (design 510). Palantir stories stay on the audit line and his estate-wide duties (chat, mind, wellbeing, status reports, App Steward, Unmeasured Call Watch) on their shared tracks, by standing ruling.

Writing Scriber's Logbook: choosing the story, digging out what really happened, interviewing the agents who touched it, and authoring the post. Text only — the pictures and videos are their own track. Runs on Codex (Ninad, 2026-08-02).

Scriber's still-image generation. Stays on Gemini: the video work moved to its own LTX track because LTX makes no still images.

Scriber's video generation. Runs on the LTX API — a video-only lane, which is why it is a track apart from the still images beside it.

The operator CLI lane: Orion claims an initiative and executes it directly as a bypass on the Claude Max subscription. Owned by Orion.

The autonomous build pipeline lane: filing, planning, executing, reviewing, monitoring and self-improving initiatives on the fleet lane. Owned by Merlin.

Repair of the build pipeline itself, performed while an initiative executes on the rung being repaired. Separate from the planner's DELIVERY track because it is a different activity, and the activity decides the track (rule 1035): troubleshooting retries must never consume the budget meant for delivering initiatives. Work bills here only while its family is an operator-selected supervised troubleshooting target; the moment the selection is withdrawn, billing returns to the planner track.

Albus's bypass rescue of FAILED planner initiatives: Elrond's urgent escalations and the escalation-ladder pickups of abandoned planner families. Separated from the Albus Bypass track by Ninad's ruling so rescue money and Albus's other bypass money can never mix.