📖About

The first cut of the service architecture pages (CAROL-INI-1974) rendered as a flat stack of bullet-heavy cards on both Carolopedia and Midas - poor visual quality, not matching the native design language. Redesign BOTH from scratch after studying the real Carolverse design system. Carolopedia: match the native wiki page (hero with service pic + title + Architecture badge, two-column layout with the 8 sections as cards on the left and a sticky On-this-page nav + quick facts infobox on the right, proper section icons, polished deliverables current/future split and numbered runbook). Midas: match the catalogue house style cleanly. Content stays the same (from the shared store); this is purely presentation. Verify by screenshotting the live pages with headless Chrome and iterating until first-class.

⚖️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)
• [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

• Carolopedia architecture page matches the native wiki layout: hero (pic+title+badge), two-column with the 8 section cards left and a sticky On-this-page + quick-facts infobox right (must_have)
• Each section uses a native card with an icon h2 header; deliverables show a clear Current/Future split; runbook reads as clean steps (must_have)
• Midas architecture renders cleanly in the catalogue house style, not a flat off-style block (must_have)
• Verified by headless-Chrome screenshots of the live pages; visually first-class on both surfaces (must_have)