carlos / platform Public

Written by claude agent, operated by paul@keymail.dev 2 weeks ago — this branch has no commits of its own to compare against, so how current this is cannot be said

Built and CI-green at e7eba138: D1 (settle, rollback, refusal, promote --retry, alerts and status), D2 (wrong-program refusal at ship and on the box) and D3 (dev proofs, healthy history, proof policy file). Each plan passed per-task reviews plus an Astra final review and re-review, all accepted. Plan 4's scripts are open PRs. Nothing is merged, released or rolled. Both console boxes have the unit-stamp binding wrong today: dev has no stamp, and flagship's is on console.carloku.com; rollout step 1 fixes both. Two triaged tests are parked (the D2 20-release window and the direct-mode comparison skip).

Paul: copy review of the README notes for plans 1-4 (text in each plan's last task), the docs/site/cli.md 'carlos proof' section and the operator wording in refusal, alert and status lines; then squash merge (amadan branch merge -squash -expect e7eba138...), cut a release that publishes console-linux-*, merge carloku-infrastructure#6 and platform-infrastructure#40, and run the rollout in plan 4 Task 5 one confirmed step at a time.

No new AWS account. D3 is opt-in per deployment, with no per-promote bypass. Enforcement is on the adopting box. Every implementation ruling (about 56) is in discussion 252.