📖About

Home: System Services (Hagrid). The four platform primitives every estate-bound track consumes - the registry (schema + accessors), the scheduler (trigger authority), the run-audit store, and the backlog/initiatives store with its status machinery - exist today only as THIS estate, smeared across Governance, Process Monitoring and Build Initiatives. Package them as the ESTATE KERNEL: one installable unit that stands up a project's own registry, scheduler, run-audit and backlog from empty schemas, driven by the instance-config seam established in the backups refactor. Kernel-first ordering is already law in the blueprint enablement: estate-bound and clone-archetype enablement refuse until the kernel exists - this initiative turns that refusal into a deploy. Scope: (1) kernel install script creating the four stores from empty, config-driven; (2) the seam gains a project-sink mode - a foreign instance writes run-audit and alerts to ITS OWN kernel instead of running bare; (3) the blueprint enablement kernel check reads real kernel presence instead of returning false for every project; (4) the Service Track Handbook documents the kernel as the named prerequisite in every estate-bound entry; (5) the estate itself remains the default instance with zero behaviour change. This is the prerequisite the sixteen remaining reusability refactors point at (topic tag service-reusability).

⚖️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)
• Arc sequencing: phase 3 (kernel), step 1/1 — Estate kernel packaging — Sequence: PHASE 3 of 5 (The estate kernel — the pivot), position 1 of 1. First in the phase. phase 2 must be complete first Why this phase: Packages the platform primitives (registry, scheduler, run-audit, backlog) as one deployable unit. Every phase-4 and phase-5 track needs an instance-side kernel to point at; without it they can only be estate-bound. (orion)
• [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

• One install command creates a project kernel - registry schema, scheduler store, run-audit store, backlog store - from empty, driven only by an instance config, with the created stores passing the same schema checks the estate stores pass. (must_have)
• The instance-config seam gains a project-sink mode: a foreign instance emits run-audit and alerts into its own kernel stores, proven by a sandbox run whose audit rows land in the sandbox kernel and nowhere else. (must_have)
• The blueprint enablement kernel check detects a real kernel: an estate-bound service that refused on the sandbox project before the kernel deploys after it, end-to-end on the record. (must_have)
• Every estate-bound Service Track Handbook entry names the kernel as its prerequisite and its reuse steps start from the kernel install. (must_have)
• The estate remains the default instance with zero behaviour change - full regression suite green. (must_have)