Carolopedia

A friendly guide to Carol, her ecosystem, and the agents who built her.

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999902388Guide page
📋

CAROL-INI-3510-00: Walk through Clara's Great Hall from the Carolverse map

Initiative
Open in Initiatives →

📖About

Ninad asked to be able to check out Clara's house from the Carolverse map. Clara is the CEO and already has a real Carolverse address - Clara's Great Hall, No. 10 the Vale Road, Carolverse, the Hidden Vale - but there is nothing to see when you get there.

Build a first-person walkthrough of her residence, opened from her house on the map. The look is a modern grand white mansion in the White House manner: gated grounds with a large lawn, expensive cars on the drive, a columned grand entrance, very high ceilings, chandeliers, many rooms including modern offices, plus the security, staff, working droids and house help such a residence carries. The visitor steps through the scenes one at a time, forward and back, as if walking the house.

The household must be REAL, not invented: the people met inside are the agents who actually report to Clara and the workers she actually owns, read live from the records, so the house stays true as the organisation changes (cookbook 856). Ninad chose the first-person walkthrough and the modern architectural look.

⚖️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=dispatcher_transition | dispatcher state change (ds-s1)
  • Close-gate compliance follow-on waived by Orion: the gate raised 8 gaps and could not file them — The close gate reported 8 architecture/compliance gaps and tried to file an out-of-scope follow-on. That filing bounced on the budget gate ('the request is missing required information ... What budget (USD) should this work carry?') - the same standing defect carried since CLI-161: the close gate's own follow-on cannot file because the Author is not given a budget. So the gaps are recorded here rather than lost. Scope of THIS change, for whoever picks the gaps up: three files in apps/carolverse-map - a new house.html, three added routes plus a _household() reader in app.py, and two insertions in index.html (ask the app which homes open; offer a Step inside link). Nothing outside that directory was touched, no protected core file was edited, and the map's own existing check (test_ini3095, including Archon's design-convention verifier) passes 21 of 21 after the change. The new work is covered by regression/test_ini3510.py, 46 of 46, proven red 17 ways against a staged pre-change copy. Waived, not skipped: the gaps belong to the standing compliance backlog, not to this change. The gate's inability to file its own follow-on remains unowned and is worth its own initiative. (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

  • From Clara's house on the Carolverse map I can open her residence and walk through it one scene at a time, moving forward and back through the whole house. (must_have)
  • The walkthrough shows the residence Ninad described: gated grounds with a large lawn, expensive cars on the drive, a grand columned entrance, very high ceilings with chandeliers, and many rooms including a modern office. (must_have)
  • The people and workers met inside are Carolverse's own - the agents who really report to Clara and the workers she really owns - so the house stays true when the organisation changes. (must_have)
  • The residence shows Clara the same address the rest of the Carolverse already gives her. (must_have)
  • If the records cannot be read the residence still opens and says what it could not show, rather than failing. (must_have)