📖About

Ninad (CLI-272) reported two symptoms: searching 'oratorium' in Carolopedia returns No matches, and the two Oratorium blogs in Orion's Logbook carry no link to the Oratorium page. Both are ONE root cause. Carolopedia's search index is built from registry rows only (agents, apps, droids, services = 590 entries), and the Logbook's link vocabulary is built the same way plus a hand-kept concept list. Every page class Carolopedia publishes that is NOT a registry row is therefore invisible to both: the 354 dictionary terms (Oratorium among them), the places, and the standalone architecture pages (Carolverse Architecture and Oratorium). The Oratorium page returns 200 and is linked from the Carolverse Architecture page, so nothing is broken except the two ways a reader would ever find it. Fix the class, not the word: index every published page class in Carolopedia's search, and feed the dictionary plus the standalone pages into the Logbook's reference vocabulary so a concept word links to the entry that explains it. Keep the Logbook's existing per-blog link cap and its phrases-and-long-words discipline so a blog does not become a thicket.

⚖️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] 7 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [delivery-check] 7 must-have criteria remain pending at bypass_end — delivery has no mechanical re-performance lane; UAT must grade on live evidence, not checklist silence (CAROL-INI-3020): (no detail) (orion)
• [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

• Searching 'oratorium' in Carolopedia returns the Oratorium page, and the result opens it. (must_have)
• Carolopedia's search index covers every page class it publishes - registry entities, dictionary terms, places, and the standalone architecture pages - and each result opens its own correct URL, including page classes whose URL is not type/slug. (must_have)
• Searching a word from each newly indexed class (a dictionary term, a place, an architecture page) returns a working result; existing agent/app/droid/service results are unchanged in count and destination. (must_have)
• The two Oratorium blogs in Orion's Logbook each link the word Oratorium to the Carolopedia Oratorium page, verified in the rendered page, not in the stored text. (must_have)
• The Logbook's reference vocabulary resolves concept words generally, so a future blog naming any dictionary term links to its entry without hand-editing a map. (must_have)
• The per-blog Carolopedia link cap still holds and the named entities (agents, apps, droids, services) are not crowded out of the blogs that already link them. (must_have)
• Both surfaces are LOOKED AT in the rendered page before the work is called done. (must_have)