Skip to content

docs(ROADMAP): add Four-layer redesign section per PRESERVATION-DESIGN §12.5#259

Open
hyperpolymath wants to merge 1 commit into
mainfrom
docs/roadmap-four-layer-section
Open

docs(ROADMAP): add Four-layer redesign section per PRESERVATION-DESIGN §12.5#259
hyperpolymath wants to merge 1 commit into
mainfrom
docs/roadmap-four-layer-section

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

Executes formal/PRESERVATION-DESIGN.md §12.5 — the ROADMAP rollout.

Inserts a new top-level section between the status snapshot and the formal-proof-status section titled == Four-layer redesign (2026-05-26 → ), structuring the L1/L2/L3/L4 implementation order with a per-layer current status.

What this provides that the existing file lacked

The pre-existing [#preservation-closure-plan] section is already correctly labelled "superseded by four-layer redesign", but it only provides negative orientation (what was). This new section provides the positive organising structure (what is + what's next + per-layer status) the spec asks for.

Per-layer status snapshot

Companion PRs

Test plan

  • Diff is purely additive (54 insertions, 0 deletions).
  • GPG-signed commit.
  • All claims back-cite the proof artefact or design doc.

🤖 Generated with Claude Code

…IGN §12.5

Executes `formal/PRESERVATION-DESIGN.md` §12.5 — the ROADMAP rollout.

Insert a new top-level section between the status snapshot and the
formal-proof-status section titled `== Four-layer redesign
(2026-05-26 → )`. The section structures the L1/L2/L3/L4
implementation order with a per-layer status:

- L1 — Region capability threading: landed (judgment + step
  relation in `TypingL1.v` + `Semantics_L1.v`); 9 admits remain.
- L2 — Modality parameter: landed (PRs #176 + #177); `linear_to_affine`
  Qed zero axioms.
- L3 — Echo residue: calculus mechanised (`Echo.v`); typing-rule
  integration is next-block work.
- L4 — Mode declaration: mechanical scaffold landed (`L4.v`); surface
  syntax not yet wired.

Per the spec's §12.5 prescription, the previous "Preservation
closure plan" framing is acknowledged as archived (pointing to
`PRESERVATION-HANDOFF.md` for the historical record). The
pre-existing `[#preservation-closure-plan]` section was already
labelled superseded by a prior commit — this new top section
provides the *forward-looking* organisation that the old framing
lacked.

No proof, code, workflow, or schema changes. Pure documentation
rollout. Companion to README #256 (§12.2), EXPLAINME #257 (§12.3),
and vision #258 (§12.4).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant