# AUTO-ACTIVATION-01

Implement the owner's 30 October activation request in the existing isolated tooling worktree. Stop before execution or signing. Preserve the existing key/authentication, seven workstream order and all later gates.

- [x] Resolve published handoff 5cb903b and its direct parent candidate fc5b9d3; keep their identities separate.
- [x] Check existing authentication and native real-key isolation. Docker pipe access is correctly denied; no system .NET SDK. Do not widen service access.
- [x] Inspect source-bound evidence using the existing handoff verifier, exact native report membership and frozen source hashes. Retain conditional/security/human dispositions. Evidence inspection is explicitly prevented from substituting for the mandatory command-running composite adapter.
- [x] Add a restricted P10-00 policy, report-only filesystem permissions and independent write-set verification. Reject P10-01 regardless of a generic roadmap signature. Test missing approvals and the protected stop using disposable Git remotes.
- [x] Prepare a clean execution checkout at fc5b9d3, exact unsigned disabled-policy request and an owner command for preparing successive eligible entry requests without launching a worker.
- [x] Run existing controller tests, new adapter/scope tests and native assessment probes; preserve their distinct evidence. Document remaining owner actions.
- [ ] AUTO-ADAPTER-01 remains BLOCKED: command-running application/service runtime not isolated and qualified. Stop before activation; do not expose general Docker/socket or widen worker access to bypass this barrier.

Ruling: the evidence-reuse inspector cannot satisfy the owner's explicit real composite runtime gate. Keep proposed and installed policies disabled, retain configured:false, and do not generate eligible environment/entry grants. The 81-test final run and native probes qualify control-plane changes only, not actual roadmap readiness. See ACTIVATION_01.md.

Changes reach controller and installed packaging, local filesystem policy, manifest schema, evidence adapter, PowerShell command dispatch, tests and operator documentation. Product files, existing acceptance evidence and the signing key remain outside the change scope. The adapter uses the existing trusted handoff verifier to prepare a receipt, then verifies exact immutable evidence/source bytes; this avoids a second report parser and unnecessary product reruns. Fresh provider runtime qualification remains a separate barrier to implementation.