carlos / platform Public

Answers #335: a doc engine's routes are reachable from the internet. This branch carries the approved design and its first plan, a simulation; no production code yet.

Spec (docs/superpowers/specs/2026-10-21-fleet-internal-engines-design.md, rev 14, approved 2026-10-21): a route whose release declares doc_engine is refused to the public on every box; granted apps call it through a per-instance socket (or the edge door), relayed over a backhaul hop that now signs the caller. Safety rests on invariant I1 (a declaring build starts only after the edge has fenced its group internal), enforced at the launch gate, an operator-only carlos route --public, and an enforced dedicated engine box. Rulings R1-R5 in §2.1; 13 Astra review rounds, findings committed beside the spec.

Plan 1 (docs/superpowers/plans/2026-10-21-engines-1-simulation.md): internal/sim/engines, a test-only seeded model with 40 named rules, invariants INV-P/I1/AV/G/ID/ARM, one witness per review finding, and a hostlife-style mutate.sh. 3000-seed sweep: 36 caught, 4 expected-miss (each caught only with the rule that shadows it), 0 missed, unmutated clean (spec §8). The model found spec gaps, now amended in the spec as "(sim, plan 1)": a new unclassified group must be fenced before its first launch; launches and --public share a per-group lock; grant records go stale 10 minutes after signing (Paul's R5).

Next: Plans 2-5 (the internal mark; engine names and grants; the call path; docs and rollout).

🤖 Generated with Claude Code