📖About

Extends Ninads one-process-one-service ruling (2976 UAT r7) to the remaining two surfaces. Today the shared blocks module admits droids into process_type blocks irrespective of owner, so the Services Catalogue and Carolopedia render Process Monitoring blocks with 138/126/5 fleet-spanning members while Carol Intelligence (fixed today) shows only Hermiones 17. Fix at the root: owner-scope the process_type membership resolution in the shared blocks module (member lists AND counts); verified safe - Hermiones process liveness queries the droids table directly and no operational consumer uses block membership. Update the module docs and the SST Block concept if it codifies the old fleet-spanning semantics.

⚖️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): Today the shared blocks module admits droids into process_type blocks irrespective of owner, causing Services Catalogue and Carolopedia to show fleet-spanning members (138/126/5) for Process Monitoring blocks, while Carol Intelligence correctly shows only Hermiones 17. No prior initiative has owner-scoped the process_type membership resolution for these two surfaces. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• [delivery-check] 3 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3022.py: PASS (3 passed in 0.57s) (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 Services Catalogue shows Process Monitoring blocks with only Hermiones own droids as members (no fleet droids from other services), matching the Carol Intelligence app (must_have)
• Carolopedia block pages and service cards show the same owner-scoped membership - the same member counts as the catalogue and Carol Intelligence for every service (must_have)
• A regression test asserts every rendered block members owner belongs to the parent services agents, so the three surfaces can never drift apart again (must_have)