📖About

Bilbo's Carolopedia page generator writes every entity the same way. It does not know that Carolopedia has two classes of page - a MAIN page for an agent, app, droid or service, and a GUIDE page for everything else, which exists only to be referenced. So it restates on a main page what a guide page already says, and it has no instruction to link out instead. Teach the writer the classes: which class it is writing, what belongs on each, and that a main page REFERENCES its guides rather than repeating them. Teach it the new page kinds it must now write - track, shared system service and concept - and that a concept page never names a database table, a column or a file path. The refresher and the change detector inherit the same instruction set from one place, so the writer and the sweepers can never drift apart.

⚖️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] 5 must-have criteria remain pending at bypass_end — delivery FAILED live re-performance; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): test test_ini3601.py: FAIL (no tests ran in 0.46s) (orion)
• [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

• The writer's instruction set states, per entity type, which page class it is writing and what belongs on that class (must_have)
• A main page written by the generator links to its guide pages instead of restating their content (must_have)
• The generator can write a track page, a shared system service page and a concept page, each from its live record (must_have)
• No generated concept page names a database table, a column or a file path (must_have)
• The refresher and the change detector read the same instruction set as the writer, from one place, so they cannot drift (must_have)