📖About

FOLLOW-ON to CAROL-INI-3592 (another lane, in reviewing - its transfer and skill are NOT touched here). 3592 created the transfer-app-ownership skill; this initiative gives it a HOME and a sharper access chapter. Scope: (1) the skill becomes a registry citizen - a skills-catalogue row with Sage (agt_025) as keeper, kind operational, plus the agent_skills mapping, mirroring how app-stewardship and manage-daily-budget are recorded; (2) the access chapter gains what 3592 could not have known: the service-scope audience derives from the OWNER (a transfer swaps the audience, or strands it when the new owner owns no service), the private-scope audience is the owner plus every SUPERVISOR above them (boss-sees-below, P.01.03.05.09), confidential reach is unchanged but rows re-attribute by owner (CLI-195), and write is a recorded grant (CAROL-INI-3459 accessors, with a reason) that ownership alone never confers; (3) the verify chapter becomes a runnable recipe - before/after reachable-agent diff - replacing the empty placeholder. Regression: catalogue row exists and names Sage.

⚖️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): CAROL-INI-3592 created the transfer-app-ownership skill, but the filing asserts it still lacks a skills-catalogue home under Sage and that its access and verify chapters are incomplete. The daily-budget app is registered; Mirror is retired but is not the subject of this filing. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (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

• The registry skills catalogue lists transfer-app-ownership with keeper Sage (agt_025) and an agent_skills mapping row, consistent with the app-stewardship convention (must_have)
• The skill states that write access is a recorded grant moved via the CAROL-INI-3459 accessors with a reason, and that ownership alone never confers write (must_have)
• The skill documents the private-scope supervisor rule, the service-scope owner-derived audience trap, and the confidential own-rows re-attribution (must_have)
• The verify chapter is a runnable before/after reachable-agent diff, not a placeholder (must_have)
• A regression test confirms the catalogue row exists and names Sage as keeper (must_have)