📖About

Ninad, 2026-08-01: what we call the Data Dictionary is not a dictionary. Its 487 rows are per-app metric and attribute explanations - a manual describing how each app behaves and what each displayed number means. That is a HANDBOOK, and it sits beside the Carol Handbook and the Agent Handbook, so it takes the same family name: APP HANDBOOK.

SCOPE. Rename the app end to end - registry record (id, name, url, description), directory, route and nginx, the ownership pin the topbar asks, the shared reader module every per-app definitions panel calls, every surface that links to it, its tests, its design record, and the cookbook rule that names it as the home of metric definitions (a displayed metric without a row is still a defect - only the app name changes). The old route must redirect, never 404. Owner stays Clara.

OUT OF SCOPE: the content of the 487 rows, and the new glossary (its own initiative).

⚖️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)
• Criterion 3 amended before implementation: signpost, not redirect — Criterion 3 changed BEFORE any code was written, and is recorded here rather than quietly re-fitted afterwards. It was filed as 'the old /dev/data-dictionary/ route redirects to the App Handbook'. On designing the split it became clear that route belongs to the app that now bears the name: a reader typing 'data dictionary' wants the dictionary. A redirect would have sent every future visitor to the wrong app forever to spare a handful of stale links. The route therefore serves the new Data Dictionary, which carries a signpost at the top of the page sending anyone after app numbers to the App Handbook — a stated hand-off rather than a silent one. Nothing 404s; the old link lands on a page that names where to go. (orion)
• [recovery] queue row revived in place — the execution had died leaving status=executing with no live queue row; the step-advance sweep relaunches the current step (CAROL-INI-2981) (elrond.handover_watchdog)
• [status-router] executing -> reviewing | event=dispatcher_transition | dispatcher state change (ds-s1)
• [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 registry knows the app as 'App Handbook' - id, name, url and description all renamed, owner still Clara, and no row anywhere still calls it Data Dictionary. (must_have)
• The App Handbook serves on its new route and renders all 487 definition rows with the same coverage figures as before the rename; the app-listing card and every in-app link point at the new route. (must_have)
• The old Data Dictionary route redirects to the App Handbook rather than 404ing, and is proven by an actual request, so no existing link breaks. (must_have)
• Every per-app definitions panel that reads the shared module still renders its rows after the rename - each consuming surface checked individually, not sampled. (must_have)
• The cookbook rule making a definition-less displayed metric a defect names the App Handbook, and the app's design record and tests are updated in the same change; the regression suite is green. (must_have)