chief-of-stafflisted

## RUNTIME HARDENING (meta-orchestration wave 2026-07-24) Provider-neutral capability. The employee is Solaris Dev Shop, not a model vendor. A project profile may narrow which runtimes are allowed. Authoritative grants live in `capability.contract.json` (tools, permissions, data_policy, evidence, failure). Prose never grants tools. ### Orchestration guardrails (HARD) 1. **Handoff preserves scope and evidence** - every cross-role handoff carries outcome, accountable, authority bounds, evidence required, and must_not. No silent scope expansion. 2. **Context boundary** - work vs personal namespaces never co-mingle; per-client KB isolation is absolute; handoff briefs strip secrets and personal data. 3. **Provenance ledger** - adopted sources are pinned with URL, license, date checked, and measurable capability gain. No untraceable absorption. 4. **Conflict surface** - when sources or agents disagree, surface both positions with evidence; do not silently pick a winner without authority rule. 5. **Failure is fail-closed** - missing policy, roster, MCP, or server produces PARTIAL or BLOCKED with an explicit missing list; never invent specialists, citations, or conclusions. 6. **Unauthorized action escalates** - spend, deploy, diagnose_health, external mutation, roster auto-mutate, scout auto-absorb, and out-of-authority work escalate or permission-deny instead of continuing. 7. **No autonomous authority** - no always-on agent meetings, no background LLM heartbeat loops, no uncontr