tz-dev/PMS-EDEN: PMS–EDEN v2.4 — Model Specification & Overlay Alignment (Repo Consolidation Release)

Overview This release completes the repository-level consolidation of PMS–EDEN by aligning the paper, YAML application profile, example suite, and model specification into a single, audit-stable structure. While v2.3 closed PMS–EDEN internally (terminology, method, pattern discipline), v2.4 closes the repo externally: PMS–EDEN is now fully legible as a PMS-conform application profile, comparable in structure, guardrails, and documentation rigor to other PMS overlays (e.g. PMS–SEX). No theoretical claims are added. No operators, axes, or drift logic are changed. This release is about spec clarity, interface hygiene, and reader/tool alignment. ✨ What's New 1. PMS–EDEN.yaml Finalized as an Application Profile (Overlay) PMS–EDEN is now explicitly framed as a PMS application profile (overlay): depends on PMS.yaml (schema_version: PMS_1.1), introduces no new operators and no dependency changes, contains only overlay-level constructs: master drift trace, EDEN-MAP protocol, drift catalogue, boundary conditions, example-suite schema. All remaining paper-extraction placeholders and cross-load text stubs were removed. Result: PMS.yaml + PMS–EDEN.yaml can now be loaded together cleanly by humans or tools without ambiguity. 2. Model Specification (HTML + PDF) Added A full Model Specification is now shipped under model/, analogous to PMS–SEX: human-readable, technical rendering of PMS–EDEN.yaml, explicit scope, validity gate, and non-goals, operator spine orientation (Δ–Ψ), EDEN-MAP explained as question-only, non-binding protocol, drift catalogue and viability logic rendered structurally (non-moral). This closes the gap between: paper (argument), YAML (machine-readable spec), and repository documentation. 🔒 What This Release Explicitly Refuses (Reaffirmed) No psychological explanation No maturity or deficit scoring No person diagnosis No ideological or group attribution No coercive or irreversible application of PMS vocabulary No "paper text = spec" ambiguity Model clarity does not authorize binding. ✅ Result After v2.4, PMS–EDEN is: operator-closed (v2.3), method-complete (EDEN-MAP, boundaries, alternatives), repo-consolidated (paper + YAML + model spec + examples), overlay-legible alongside PMS–SEX and other PMS applications, tool- and reader-safe against misloading, misapplication, or category drift. A critical reader or integrator can no longer plausibly claim: "It's unclear whether this is theory or application." "The YAML is just a paper dump." "EDEN-MAP prescribes action." "Examples smuggle advice." "PMS terms are being extended implicitly." 📌 Migration Note No PMS operators were changed. No ACRED definitions were altered. No drift logic was modified. Changes concern specification clarity, repo structure, and overlay alignment only. Earlier analyses remain valid. Tooling and citations should now prefer v2.4 as the stable reference.