Skip to content

docs(vision): add == The Dyad and the Layers per PRESERVATION-DESIGN §12.4#258

Merged
hyperpolymath merged 1 commit into
mainfrom
docs/vision-four-layers-section
May 31, 2026
Merged

docs(vision): add == The Dyad and the Layers per PRESERVATION-DESIGN §12.4#258
hyperpolymath merged 1 commit into
mainfrom
docs/vision-four-layers-section

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

@hyperpolymath hyperpolymath commented May 30, 2026

Summary

Executes formal/PRESERVATION-DESIGN.md §12.4 — the EPHAPAX-VISION rollout.

Inserts a new section between == The Dyad and == One Language, One Feel titled == The Dyad and the Layers.

The spec's instruction is verbatim:

The vision doc already articulates the dyad beautifully (mother / child, "ephapax means once for all" double-meaning, "Linear ⊂ Affine in valid programs", "one language, one feel"). The four-layer story extends this; it does not replace it.

So this PR is purely additive — no existing content is reworded, removed, or reshaped. The new section maps each layer onto what the dyad says about it (L1: identical; L2: the dyad itself; L3: mother demands residue be observed; L4: which side you speak from), and closes with: "The dyad remains primary. The layers are how the dyad's promises are enforced."

Companion PRs

Test plan

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

🤖 Generated with Claude Code

@hyperpolymath @claude
docs(vision): add == The Dyad and the Layers per PRESERVATION-DESIG…
4ab6d45 
…N §12.4

Executes `formal/PRESERVATION-DESIGN.md` §12.4 (EPHAPAX-VISION
rollout):

Insert a new section between `== The Dyad` and
`== One Language, One Feel` titled `== The Dyad and the Layers`.

The new section extends — does not replace — the dyad framing. Per
the spec's §12.4 instruction:

> The vision doc already articulates the dyad beautifully [...].
> The four-layer story *extends* this; it does not replace it.

The new section maps each layer (L1 / L2 / L3 / L4) onto what the
dyad says about it:

- L1 (regions) — identical in both modes; same soundness story.
- L2 (modality) — the dyad itself; `linear_to_affine` mechanises
  Linear ⊆ Affine.
- L3 (echo) — mother demands the residue be observed; child may
  silently lower.
- L4 (dyadic interaction) — declaration of which side you speak
  from.

Closes with: "The dyad remains primary. The layers are how the
dyad's promises are *enforced*."

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

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@hyperpolymath hyperpolymath enabled auto-merge (squash) May 30, 2026 23:29
This was referenced May 30, 2026
Merged
Merged
Merged
@hyperpolymath hyperpolymath merged commit 26eb78a into main May 31, 2026
0 of 16 checks passed
@hyperpolymath hyperpolymath deleted the docs/vision-four-layers-section branch May 31, 2026 06:21
hyperpolymath added a commit that referenced this pull request May 31, 2026
@hyperpolymath @claude
docs(spec): add four-layer intro paragraph per PRESERVATION-DESIGN §1…
b9e3d98 
…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
@hyperpolymath @claude
docs(ephapax-linear): add L2 naming-note banner + rename to "Two L2 M…
a375986 
…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>
hyperpolymath added a commit that referenced this pull request May 31, 2026
@hyperpolymath @claude
docs(ROADMAP): add Four-layer redesign section per PRESERVATION-DES…
ff1ab29 
…IGN §12.5 (#259)

## Summary

Executes [`formal/PRESERVATION-DESIGN.md`
§12.5](../blob/main/formal/PRESERVATION-DESIGN.md) — 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

- **L1**: landed (judgment + step relation); 9 admits remain as
L2-integration debt.
- **L2**: landed (PRs #176 + #177); `linear_to_affine` Qed zero axioms.
- **L3**: calculus mechanised (`Echo.v`); typing-rule integration is
next-block work.
- **L4**: mechanical scaffold landed (`L4.v`); surface syntax not yet
wired.

## Companion PRs

- #256 — README §12.2 four-layers section
- #257 — EXPLAINME §12.3 claims
- #258 — vision §12.4 dyad-and-layers

## Test plan

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

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@hyperpolymath