📖About

Ninad ruling 2026-07-24: all public-facing assets - Carolopedia, Orions Logbook, videos, Carolverse web pages, denken-labs web presence, Carols bio - belong to the MARKETING service (Loki). Today marketing is a wip catalog stub with no track/blocks; Carolopedia is tagged to governance and the Logbook to nothing. Build the service properly in Midas catalog: activate it, seed the Core track + three blocks (Encyclopedia and Logbooks / Web Presence / Video Channel) with narrative roles, and tag the asset apps (carolopedia, orion-logbook, carol-bio, carolverse-map) to marketing. Scribers Logbook stays in the Build Initiatives Creative track per the standing 3188 ruling - noted, not moved.

⚖️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)
• Current state at filing (Elrond validity check): The Marketing service is a stub in Midas catalog with no tracks or blocks. Carolopedia is still tagged to Governance, and Orions Logbook, Carol Bio, and Carolverse Map are not tagged to Marketing. Scribers Logbook remains under Build Initiatives Creative track. All named apps are registered and running. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Ninad ruling: all public assets under Marketing (Loki). Seeded idempotent tools/seed_marketing_service.py; four legacy marketing blocks kept and reconciled onto the Core track; Scribers Logbook stays in the Build Initiatives Creative track per 3188. (or-bx-01)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [agt_028.mind] dispatched my droid ca-s2 (sequence next): Run the next on-demand compliance audit tranche over the refreshed reviewing docket, risk-class first. Exposure tranche: CAROL-INI-3315-00 (Marketing service under Loki owning ALL public Carolverse assets — Carolopedia, Logbook, map, bio, web presence, video channel; verify a single-owner consolidation of every public surface carries a privacy review gate before publication, that prior map-privacy findings are inherited as standing constraints, and that ownership transfer does not orphan existing audit obligations) and CAROL-INI-3316-00 (Carolopedia Refresh Utility with a budget-bounded refresh queue on DeepSeek — check the budget lane is authorised under budget policy, source-mapped change detection does not pull internal/private data into public pages, and 'freshness truth' claims are auditable). Public-map/Carolopedia hygiene tranche at lower severity: 3305 (internal topbar script 404 on the public subdomain — an internal script referenced from a public surface is a leak vector, ver — My reflective memory is explicit: when the queue turns over, prior audit coverage expires with it. Nine of the ten reviewing items plus 3315/3316 are new since my last tranche. 3315 concentrates every public-facing asset under one owner — that is an exposure and accountability question squarely in my remit, and public surfaces get privacy scrutiny first. The map cluster also lets me verify that the Albus authority retirement I audited (3293/3294) is truthfully reflected in the public architecture page, closing the loop on retired-authority verification. Dispatching my own on-demand auditor is the proportionate instrument. (agt_028.mind)
• [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 Marketing service shows ACTIVE in Midas Services Catalogue with a Core track and three asset blocks, owned by Loki (must_have)
• Carolopedia, Orions Logbook, Carols bio and the Carolverse Map are tagged to the Marketing service - Carolopedia no longer counts under Governance (must_have)