Carolopedia

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

📖 CarolopediaServicesBuild InitiativesAll activitiesINI-999902137Guide page
📋

CAROL-INI-3308-00: Carolopedia twin pages cleanup: one canonical address per entity, map links corrected, architecture SST links normalized

Initiative
Open in Initiatives →

📖About

Ninad found twin Carolopedia pages: /wiki/agent/agt-003 AND /wiki/agent/agt_003 both render (the entity route resolves the slug against the registry in both underscore and hyphen forms). Applies to ALL entity types (agent/app/droid/service/block) - duplicate public content, split SEO, drifting links. Fix: (1) canonical 301 - any non-canonical slug (underscore/uppercase) permanently redirects to the hyphen form on the entity page, entity API and service sub-pages; (2) the Carolverse Map builds its two Carolopedia agent links from the RAW registry id (underscore) - slugify them; (3) the architecture SST (registry service_architecture) holds ~90 underscore wiki links across 10 columns - rewrite to canonical, and normalize wiki entity links at the store write path so future rows cannot reintroduce twins. Sitemap verified already-canonical; consciousness console + shared architecture link maps verified already-hyphenated.

⚖️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)
  • Root cause: the Carolopedia entity resolver accepts BOTH the hyphen slug and the raw underscore registry id, so every entity had twin public pages; the Carolverse Map linked agents by raw id (underscore twin) and the architecture SST stored ~90 underscore links. Fix: canonical 301 at the entity page/API/service sub-page routes (one address survives, search engines fold the twins); map links slugified; SST swept (16 rows) + write-path normalization in the architecture store. Sitemap verified already-canonical; consciousness console and the shared architecture link maps verified already-hyphenated. (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

  • Every Carolopedia entity page has exactly one working address: the underscore twin permanently redirects (301) to the canonical hyphen page for agents, apps, droids, services and blocks (must_have)
  • The Carolverse Map agent links open the canonical Carolopedia pages, not the twins (must_have)
  • The architecture SST contains no links to twin pages, and newly stored architecture text is normalized so twins cannot come back (must_have)