📖About

Ninad (CLI-272): the Carolopedia landing hero is a dark photoreal painting, while everything around it - the Carol and Orion portraits, the Carolverse Map, and the world-in-words page - is hand-drawn on cream paper. Two changes. First, redraw the SAME scene (the Carolverse gateway arch of named building blocks, a figure looking through it to the capital) in the Carolopedia house style: pencil and ink, warm sepia graphite, cream paper, so the landing page reads as one drawing set. Second, the existing painting is not discarded - it goes in AS IS as the hero image at the top of the world-in-words page, which today opens on text with no picture at all.

⚖️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)
• [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 Carolopedia landing hero is a hand-drawn pencil-and-ink image on cream paper in warm sepia, sitting comfortably beside the Carol and Orion portraits and the parchment map rather than against them. (must_have)
• The redrawn hero shows the SAME subject as the original - a gateway arch built of named blocks, opening onto the capital, with a figure regarding it. (must_have)
• Any lettering in the redrawn hero reads as real words; a garbled or invented label is a fail and the image is regenerated. (must_have)
• The original painting is preserved unchanged and serves as the hero image at the top of the world-in-words page. (must_have)
• The world page hero spans the page width, is responsive at narrow and wide viewports, and does not push the page title off the first screen. (must_have)
• Both pages are LOOKED AT rendered at desktop and mobile widths before the work is called done. (must_have)
• The image generation is billed to the service whose work asked for it, not to an unnamed caller. (must_have)