📋 docs: consolidated execution plan 2026-07-11 (merge-order synthesis of 5 waves)

[gHashTag]

Draft — do not auto-merge (human-only per docs/AUTONOMOUS.md). Tracks #74.

What this PR adds

docs/EXECUTION_PLAN_2026-07-11.md — a single dependency-ordered execution plan synthesizing the five prior audit waves (#59, #67, #69, #71, #73). Not a new audit: every finding is cited to the wave that filed it. No spec/code changed.

Honesty preface (verified from git this session)

• main red: cargo build fails in build.rs:29-30 (E0308 + E0599, 4 errors), before the library/gen/rust.
• Ground-truth counts: 68 .t27 specs, 101 #[test].
• Upstream compile dependency re-checked: t27#1401 CLOSED (in the pinned t27c), t27#1456 OPEN, t27#1457 OPEN.

The single bottleneck

main does not build → PR #60 must merge first. Until then nothing downstream is verifiable or regenerable.

Contents

1. Bottleneck stated up front + leverage argument for build(pipeline): pinned-t27c gen/rust + physical drift-guard (запрет писать в репо неправильно) #60.
2. Dependency-ordered plan — Step 0 (merge build(pipeline): pinned-t27c gen/rust + physical drift-guard (запрет писать в репо неправильно) #60, close 🌊 Wave 2026-07-10 · fix(build): зелёная библиотека + отчёт волны (closes-partial #58) #59 superseded, t27#1456/#1457 gate for the 8/9 inert modules); Step 1 (all 5 P1s spec-first, ordered by attack-relevance, each with .t27 + acceptance test + effort); Step 2 (P2 hardening groups A–F).
3. Findings → 4-sprint map (identity+integrity / path-diversity+self-heal / hardening / verification-parity), E-ids + dependencies.
4. Three cooperation lanes, framed as executable next steps once build(pipeline): pinned-t27c gen/rust + physical drift-guard (запрет писать в репо неправильно) #60 lands.
5. Competitor note (Electronics 15(4):785, Feb 2026).

Boundary

Synthesis only — no merge, no push to main, no hardware, no fabricated metrics. Does not rewrite docs/archive/STRENGTHEN.md. Agent proposes; a human merges.

phi^2 + phi^-2 = 3

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

[gHashTag]

Triage — KEEP

Verdict from cascade analysis: KEEP, awaiting caskade merge.

Root cause of red CI (build + test (-sim baseline)): committed gen/rust/ on feature branches with expanded module set contains E0425 defects from three optimizer scan bugs in t27c (const_propagate, copy_propagate, dead_store_elim not recursing into control-flow bodies). Not a defect in this PR — this PR is docs-only and has no code paths affected.

Cascade to unblock (all three DRAFT):

1. t27#1461 — mut-inference (base t27/master)
2. t27#1462 — recursive optimizer scan (stacked on #1461), verified −182 errors cross-env (linux sandbox 28 / macOS arm64 26, ±2 epsilon)
3. tri-net#80 — regen gen/rust/ on feat branches with new t27c

Once #80 lands, baseline CI on this PR goes green automatically. No action required on this PR — it stays DRAFT until human merge.

Realm-check discipline: numbers above measured on commit SHA bbaaa4a1 in t27, cargo check --lib grep count ^error\[E. Not fabricated.

phi^2 + phi^-2 = 3