tz-dev/PMS-LOGIC: PMS–LOGIC v1.3.0 — Calibration, Restraint, and Full Schema Alignment

What's New in This Release (v1.3.0) This release brings PMS–LOGIC to a substantially more disciplined and publication-ready state. It does not alter the core thesis of the project. Instead, it sharpens its methodological restraint, clarifies its scope boundaries, updates the full repository to PMS_1.3, and brings the paper, YAML profile, model specification, README, and example suite into much tighter alignment. The result is a stronger and more defensible articulation of PMS–LOGIC's central contribution: responsibility can become structurally readable without deriving an "ought." This release is especially important because it reduces several remaining forms of overclaim without weakening the model's actual force. PMS–LOGIC now speaks more clearly as a praxeological reconstruction, not as a final philosophical settlement. New in v1.3.0 1) Full alignment to PMS_1.3 This release updates PMS–LOGIC across the repository from PMS_1.1 dependency language to the current PMS_1.3 base specification. This includes: PMS-LOGIC.yaml model specification metadata README dependency statements example suite alignment blocks schema references across repository artifacts PMS–LOGIC remains fully dependent on the canonical PMS grammar and continues to: introduce no new operators redefine no operator meanings alter no dependency relations modify no canonical derived axes The profile remains a strict overlay/application schema, not an extension of PMS. 2) Schema upgrade to PMS-LOGIC_1.1 The canonical profile has now been stabilized as: schema_version: PMS-LOGIC_1.1 This release updates the YAML profile so that it now reflects the revised paper more faithfully and with greater methodological precision. Key profile-level improvements include: updated metadata and dependency references sharpened descriptions of the overlay scope clearer distinction between structural failure modes and PMS-internal self-binding constraints more disciplined language around responsibility, non-closure, and logic as boundary-management rather than authority explicit retention of scene-boundedness, reversibility, and Dignity-in-Practice 3) Overclaim reduction and methodological discipline This is the decisive contribution of v1.3.0. The previous state of the repository was already structurally strong, but some formulations still risked sounding too final, especially where PMS–LOGIC seemed to: settle the Hume problem once and for all, privilege carried non-closure as the only final architecture, glide too quickly from structural legibility to philosophical superiority, or treat responsibility-readability as fully capture-complete in every case. This release systematically disciplines those tendencies. Across the paper-facing and model-facing artifacts, the repository now makes much clearer that PMS–LOGIC offers: a specifically praxeological reconstruction an unusually sharp structural grammar a bounded and accountable interpretive profile but not a monopoly on philosophical settlement The revision therefore strengthens: methodological restraint rival-framing openness non-capture awareness calibration openness and the distinction between translation success and final superiority In short: PMS–LOGIC is now more explicit that structural sharpness is not the same thing as final closure. 4) Effective capacity and calibration sensitivity made explicit A major improvement in this release is the clearer articulation of the effective capacity boundary. PMS–LOGIC has always held that: abstract possibility does not generate responsibility, responsibility tracks effective, frame-bound capacity, and no responsibility arises where capacity is structurally absent. In v1.3.0, this is now expressed more precisely across the YAML profile, examples, and explanatory materials through an explicit calibration-sensitive threshold clause: PMS–LOGIC specifies the structural form of attributable capacity, but not every threshold of sufficiency in advance. This matters because it prevents two predictable distortions: moral inflation ("you were obliged to do the impossible") moral erasure ("since the thresholds are unclear, nothing is attributable") This is one of the most important methodological gains of the release. 5) Failure-mode constraints reformulated in non-command language One of the strongest revisions in this release concerns the former "Do not …" formulations. The repository now consistently avoids making the constraint layer sound like a hidden rule system or proto-ethics. Instead of command-like formulations, PMS–LOGIC now expresses these as structural self-binding or instability statements, for example: "A boundary that cannot be carried becomes structurally unstable." "Forced closure where Non-Event (Λ) persists produces structural instability." "When explanatory power is converted into sense-making authority, structural overreach occurs." "Where proximity generates power, viable praxis requires maintained distance." "Within PMS–LOGIC, stable self-binding takes the form of restraint rather than assertion." This preserves the full strength of the analysis while reducing the risk that the profile be misread as a disguised moral code. 6) Counter-readings expanded and strengthened This release improves the repository's misuse resistance by strengthening the counter-readings layer. In particular, PMS–LOGIC now more clearly addresses the concern that: a structurally elegant translation may not yet be proof of final philosophical superiority. The profile now explicitly acknowledges that PMS–LOGIC may succeed by making one structural layer unusually legible, while still leaving open: rival philosophical strengths, alternative explanatory burdens, and cases of genuine non-capture This is a major improvement in philosophical accountability and makes the project substantially harder to dismiss as covert overreach. 7) Projection onto A/C/R/E/D clarified as paper-internal localization The axes projection has also been tightened. This release clarifies that the projection onto: Awareness (A) Coherence (C) Responsibility (R) Action (E) Dignity-in-Practice (D) is not a measurement of objective system quality. It is now explicitly framed as: a paper-internal structural localization not a person-evaluation not a quality score not a universal ranking device This improves both conceptual hygiene and compatibility with the broader PMS guardrails. 8) Full revision of the five example-suite entries All five core examples have now been fully reworked into a much more rigorous and uniform schema format. The example suite now exists as a properly structured PMS–LOGIC example layer aligned with: PMS-LOGIC.yaml (PMS-LOGIC_1.1) PMS.yaml (PMS_1.3) The five examples are: Disaster Triage Without a Moral Code The Whistleblower Case: Omission as Λ Under Institutional Frame Policy Under Deep Uncertainty: When Logic Must Carry Λ Platform Moderation: Authority Capture via "We're Just Being Rational" Family Care Asymmetry: Responsibility Without Prescription Each example now includes, in full schema form: example metadata validity gate reminder model binding minimal vignette repo-usefulness statement frame validity full operator mapping tripartition tagging structural analysis by operator effective capacity boundary moral readability field logic boundary management drift markers failure-mode constraint references PMS–LOGIC output block readable and extended structural closure counter-reading relevance local derived-axes projection scene-bound conclusion and publication note This turns the examples into genuinely reusable operator-legible test vectors rather than merely illustrative case sketches. 9) Model specification and HTML alignment updated The human-readable model specification has also been revised to match the new YAML more strictly. This includes: updated schema metadata corrected PMS dependency references revised descriptions of the top-level YAML structure updated language for non-closure, responsibility, and logic stronger alignment between HTML prose and schema blocks clearer distinction between: reconstruction boundary management drift projection and example discipline In addition, the example-to-HTML conversion logic has now been pushed toward a more complete schema-faithful rendering model. 10) README fully updated The repository README has been brought onto the new standard. It now reflects: PMS_1.3 dependency PMS-LOGIC_1.1 schema status clarified description of what PMS–LOGIC is and is not improved articulation of the YAML profile and example suite updated repository structure current example-suite function stronger alignment with the revised methodological stance preserved resource table and ecosystem links The README now presents the project much more cleanly as: a PMS-conform application profile with machine-readable and human-readable artifacts plus a full stress-test example suite under explicit non-normative guardrails Why This Release Matters This release matters because PMS–LOGIC was already strong enough that its main remaining risk was no longer lack of clarity, but overstated clarity. That is a good problem to have — but it still had to be solved. v1.3.0 does that by making explicit that PMS–LOGIC: does not dissolve philosophical tension by fiat, does not claim monopoly on responsibility analysis, does not mistake structural elegance for total capture, and does not allow its own reconstruction to harden into authority At the same time, nothing essential is weakened. The release preserves and sharpens everything that makes PMS–LOGIC distinctive: responsibility vs. ought morality as readability field pre-moral / logical / post-moral tripartition non-closure as structurally carriable no sanctio