📖About

Ninad ruling (CLI-248): each project needs to have a sandbox; Carolverse's sandbox is carol-vm itself. The registry already declares per-project OS identities (project_os, CAROL-INI-3788 jail pilot) but nothing REQUIRES one per project. This initiative: (1) promotes the ruling to the Build Cookbook, (2) adds a 'Sandbox' term to the Data Dictionary, (3) adds a regression test that every client project carries a live project_os declaration, (4) verifies current projects comply (glover=prj_glover jail, carolverse=the platform on carol-vm).

⚖️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)
• [delivery-check] 4 pending must-have criteria stamped met at bypass_end on live re-performance evidence (CAROL-INI-3020): test test_ini3801_project_sandbox.py: PASS (2 passed in 0.48s) (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

• Cookbook entry records the ruling: every project has a sandbox; a project without a declared OS identity is a defect; the platform project's sandbox is the whole carol-vm (must_have)
• Data Dictionary defines 'Sandbox' (project jail vs the platform's VM boundary), distinguished from an agent OS login (must_have)
• A regression test in the persistent runner fails if any client project lacks a live project_os declaration; it passes today (must_have)
• Both current projects verified compliant: glover jailed as its own OS user, carolverse declared as the platform on carol-vm (must_have)