docs(ROADMAP): add Four-layer redesign section per PRESERVATION-DESIGN §12.5#259
Merged
Merged
Conversation
…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>
This was referenced May 30, 2026
hyperpolymath
added a commit
that referenced
this pull request
May 31, 2026
…2.6 (#261) ## Summary Executes [`formal/PRESERVATION-DESIGN.md` §12.6](../blob/main/formal/PRESERVATION-DESIGN.md) — the canonical-spec rollout. ### What changed One-paragraph intro added to both spec documents: - `spec/SPEC.md` (formal versioned spec) — inserted after §1.1 Overview. - `spec/ephapax-spec.md` (complete-language spec v0.1) — inserted after the Purpose block. The paragraph: 1. Names the four orthogonal disciplines (L1 / L2 / L3 / L4). 2. Explicitly labels the normative scope (L1 + L2) vs forward-looking scope (L3 + L4) — directly from the §12.6 spec. 3. Cross-references `EPHAPAX-VISION.adoc` and `PRESERVATION-DESIGN.md`. ### Out of scope (deliberately) §12.6's bullet list also calls for: - Full L1 sibling-safety **theorem** statement in the spec. - Marking L3 (Echo) as "future extension; not normative" in a dedicated subsection. Those are substantive spec edits that should each be reviewed individually per the per-document rollout pattern §12 establishes. Filing them as separate follow-up PRs. ## Companion PRs - #256 — README §12.2 - #257 — EXPLAINME §12.3 - #258 — vision §12.4 - #259 — ROADMAP §12.5 - #260 — ephapax-linear §12.7 ## Test plan - [x] GPG-signed commit. - [x] Both spec files get identical intro paragraph (verified by diff). - [x] Cross-references point to existing files in this repo. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hyperpolymath
added a commit
that referenced
this pull request
May 31, 2026
…odalities" per PRESERVATION-DESIGN §12.7 (#260) ## Summary Executes [`formal/PRESERVATION-DESIGN.md` §12.7](../blob/main/formal/PRESERVATION-DESIGN.md) — the ephapax-linear sublanguage docs rollout. ### What changed 1. **Naming-note banner** added at the top of the README content (after the existing first-read disambiguation), explaining that the crate name `ephapax-linear` is historical and that it implements **both** L2 modalities (Linear + Affine). Two admissible-derivation regimes over the same syntax/semantics, not two languages. 2. **Section heading rename**: "Dual Grammars" → "Two L2 Modalities" per the spec. 3. Banner links to `EPHAPAX-VISION.adoc` (dyad framing) and `PRESERVATION-DESIGN.md §5` (L2 layer). ### What is NOT changed - The existing AffineScript disambiguation block at the top is untouched. - The grammar-comparison table contents are unchanged (just the heading). ## Companion PRs - #256 — README §12.2 - #257 — EXPLAINME §12.3 - #258 — vision §12.4 - #259 — ROADMAP §12.5 ## Test plan - [x] GPG-signed commit. - [x] All cross-references point to existing files in this repo. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
linear_to_affineQed zero axioms.Echo.v); typing-rule integration is next-block work.L4.v); surface syntax not yet wired.Companion PRs
== The four layerssection per PRESERVATION-DESIGN §12.2 + L4 truth fix #256 — README §12.2 four-layers section== The Dyad and the Layersper PRESERVATION-DESIGN §12.4 #258 — vision §12.4 dyad-and-layersTest plan
🤖 Generated with Claude Code