docs(spec): add four-layer intro paragraph per PRESERVATION-DESIGN §12.6#261
Open
hyperpolymath wants to merge 1 commit into
Open
docs(spec): add four-layer intro paragraph per PRESERVATION-DESIGN §12.6#261hyperpolymath wants to merge 1 commit into
hyperpolymath wants to merge 1 commit into
Conversation
Executes `formal/PRESERVATION-DESIGN.md` §12.6 — the canonical-spec rollout. Adds the prescribed intro paragraph (one paragraph each) 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 names the four orthogonal disciplines (L1 region capabilities / L2 modality / L3 echo / L4 dyadic mode), explicitly labels the normative scope (L1 + L2) vs forward-looking scope (L3 + L4), and cross-references the vision doc and the design doc. The full L1 sibling-safety theorem statement and the L3 "Echo Types: future extension, not normative" subsection prescribed by §12.6's bullet list are out of scope for this PR — they require substantive spec edits that should each be reviewed individually per the per-document rollout pattern §12 establishes. No proof, code, workflow, or schema changes. Pure documentation rollout. Companion to README #256 / EXPLAINME #257 / vision #258 / ROADMAP #259 / ephapax-linear #260. 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.6 — 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:
EPHAPAX-VISION.adocandPRESERVATION-DESIGN.md.Out of scope (deliberately)
§12.6's bullet list also calls for:
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
== The four layerssection per PRESERVATION-DESIGN §12.2 + L4 truth fix #256 — README §12.2== The Dyad and the Layersper PRESERVATION-DESIGN §12.4 #258 — vision §12.4Four-layer redesignsection per PRESERVATION-DESIGN §12.5 #259 — ROADMAP §12.5Test plan
🤖 Generated with Claude Code