diff --git a/.gitattributes b/.gitattributes
index dfe0770..6896242 100644
--- a/.gitattributes
+++ b/.gitattributes
@@ -1,2 +1,3 @@
-# Auto detect text files and perform LF normalization
* text=auto
+# Preserve the supplied publication bytes, including its checksum ledger.
+releases/v2.1/** -text
diff --git a/.github/workflows/publication.yml b/.github/workflows/publication.yml
new file mode 100644
index 0000000..51c7f1f
--- /dev/null
+++ b/.github/workflows/publication.yml
@@ -0,0 +1,64 @@
+name: Verify and publish MHIOS
+on:
+ push:
+ branches: [main]
+ tags: ['v2.1-core13.0']
+ pull_request:
+ workflow_dispatch:
+permissions:
+ contents: read
+env:
+ PYTHONUTF8: '1'
+ PYTHONDONTWRITEBYTECODE: '1'
+jobs:
+ verify:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: actions/setup-python@v5
+ with:
+ python-version: '3.12'
+ cache: pip
+ cache-dependency-path: |
+ requirements.txt
+ releases/v2.1/requirements.txt
+ - run: pip install -r requirements.txt
+ - run: python -B releases/v2.1/verify_all.py --output-dir verification-output
+ - name: Show check diagnostics
+ if: failure()
+ run: cat verification-output/*.log
+ - uses: actions/upload-artifact@v4
+ if: always()
+ with:
+ name: verification-evidence
+ path: verification-output/
+ build-pages:
+ needs: verify
+ if: github.ref == 'refs/heads/main' && github.event_name != 'pull_request'
+ runs-on: ubuntu-latest
+ steps:
+ - uses: actions/checkout@v4
+ - uses: actions/setup-python@v5
+ with:
+ python-version: '3.12'
+ - run: pip install lxml==6.1.1
+ - run: python scripts/build_site.py
+ - uses: actions/upload-pages-artifact@v3
+ with:
+ path: _site
+ deploy:
+ needs: build-pages
+ runs-on: ubuntu-latest
+ permissions:
+ pages: write
+ id-token: write
+ environment:
+ name: github-pages
+ url: ${{ steps.deployment.outputs.page_url }}
+ concurrency:
+ group: pages
+ cancel-in-progress: false
+ steps:
+ - name: Deploy reading site
+ id: deployment
+ uses: actions/deploy-pages@v4
diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..ebad8dc
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,5 @@
+__pycache__/
+.pytest_cache/
+.venv/
+verification-output/
+_site/
diff --git a/CITATION.cff b/CITATION.cff
new file mode 100644
index 0000000..c74f13d
--- /dev/null
+++ b/CITATION.cff
@@ -0,0 +1,13 @@
+cff-version: 1.2.0
+message: "Cite the exact MHIOS release and identify any modifications."
+title: "MathGov Human Interface and Orchestration Standard (MHIOS)"
+type: software
+authors:
+ - family-names: McGaughran
+ given-names: James
+version: "2.1"
+date-released: "2026-09-28"
+license: Apache-2.0
+repository-code: "https://github.com/MathGov/mhios"
+url: "https://mathgov.github.io/mhios/"
+abstract: "A research-and-teaching companion specification, preparation workbook and bounded record-consistency implementation, pinned to MathGov / RippleLogic Core v13.0 Release I."
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
new file mode 100644
index 0000000..035e549
--- /dev/null
+++ b/CONTRIBUTING.md
@@ -0,0 +1,5 @@
+# Contributing
+
+Report the exact release, source section or file, expected behavior, observed behavior and smallest reproducible example. Use synthetic or appropriately redacted records; do not post private stakeholder data or credentials.
+
+Keep research arguments, software failures, accessibility findings and operational evidence distinct. A passing local validator is not authority. Changes to the frozen publication require a new edition with regenerated documents, checksums and tests; do not patch its files in place. Repository navigation and CI changes can be reviewed separately. Contributions must be yours to share and retain applicable notices.
diff --git a/NOTICE.md b/NOTICE.md
new file mode 100644
index 0000000..9599dff
--- /dev/null
+++ b/NOTICE.md
@@ -0,0 +1,8 @@
+# Notice
+
+MathGov Human Interface and Orchestration Standard (MHIOS), version 2.1.
+Copyright 2026 James McGaughran / MathGov Institute for Ethical Systems Design.
+
+This package updates the user-supplied MHIOS v2.0 source. The original is preserved in the complete provenance archive. Source documents, templates and supplied local reference code are distributed under the source package's Apache-2.0 licence; see LICENSE.txt. Informative references to external standards do not incorporate their copyrighted full text or imply certification.
+
+The fifteen files in references/Core_15 are exact, unchanged source dependencies. MHIOS is a companion, not a new member of the Core 15. User shorthand “MIOS” denotes MHIOS in this delivery.
diff --git a/PUBLICATION.md b/PUBLICATION.md
new file mode 100644
index 0000000..21c0940
--- /dev/null
+++ b/PUBLICATION.md
@@ -0,0 +1,34 @@
+# MHIOS v2.1 publication audit
+
+The supplied `MathGov_MHIOS_v2.1_Core13.0_Publication.zip` has SHA-256:
+
+`7af9f50b9853957283768548fe51f5502758485eab6cf8006b83640ca0a534f1`
+
+All 86 supplied files are preserved without modification in `releases/v2.1`. The original ZIP is the fixed release download. The private v2.0 provenance described inside the documents was not included in this public ZIP and is not needed to read or run the v2.1 package. We cannot independently reproduce claims about unprovided v2.0 source changes.
+
+## Independently repeated checks
+
+- All ten supplied verification commands passed; 133 tests and six completed synthetic examples passed at the declared replay time.
+- The payload was unchanged after running the suite. The supplied ledger covers 85 files plus the ledger itself.
+- All fifteen Core source hashes match the previously verified live Core Release I masters. No Core source was altered.
+- Complete Markdown/Word body-and-table token parity passed; all 115 rendered PDF contents links resolved to the expected headings. The 41-page PDF had no blank pages or out-of-page text blocks. All pages were visually inspected as rendered contact sheets; no obvious clipping or table-fragment defects were found. This is not a full assistive-technology audit of the PDF.
+- Workbook structure: fourteen sheets, twenty formulas, no cached error cells, untouched formula rows UNASSESSED. The package reports eight prior formula probes; this publication pass does not claim a new native Excel recalculation or independently rerun those prior spreadsheet-engine probes.
+- All supplied local reading links passed. Hosted website checks and CI publication receipts are recorded separately after deployment.
+
+See [local execution receipt](publication/v2.1/local-verification.json), [Core comparison](publication/v2.1/core-comparison.json), and the [package's detailed evidence boundary](releases/v2.1/release/VERIFICATION_REPORT.md).
+
+## Findings addressed in the publication layer
+
+The package is suitable for publication as a bounded research companion. Its v2.0-to-v2.1 lineage is now distinguished from the previous public v0.8 release. The current release is prominent, old repository files are clearly archived, readers and editable downloads are linked, and version-pinned CI runs the unchanged verifier. Windows users are instructed to enable Python UTF-8 mode because several supplied read operations use the interpreter default encoding. The original publication remains unchanged.
+
+The internal reports' statements that hosting/CI were not yet performed are preparation-time history, not a claim about the repository's subsequent deployment. Likewise old version strings explicitly labeled historical are preserved as provenance.
+
+## Limits
+
+Passing the suite demonstrates the listed checks, not exhaustive semantic correctness or complete conformance. Full external Canon schemas/registries, applicable RPAP/PFAP, actual authority/cryptographic acceptance, human-interface implementation tests, empirical validation and domain safety remain separate. Sixteen listed interface vectors have mixed executable/manual/document-level coverage; 133 tests do not mean 133 independent empirical findings. MHIOS v2.1 is not automatically compatible with v0.8 or v2.0 records.
+
+## Clean-environment and browser findings repaired
+
+The initial clean Linux CI run passed 131 tests but failed two malformed-date tests because the supplied requirements omit jsonschema’s optional RFC3339 date-time dependency. The local environment already contained it. Root `requirements.txt` now explicitly pins `rfc3339-validator==0.1.4`; all checks are rerun in hosted CI. No failing test was skipped or weakened. The recommended publication-edition download includes these installation requirements and preserves the original package under `releases/v2.1/`.
+
+The supplied HTML reader has an empty language attribute and narrow-screen overflow. The hosted `/read/` projection sets English, adds keyboard-focusable scrolling tables, a main landmark, a collapsible contents list and publication navigation. The builder asserts that its complete standard-body text is unchanged. The original HTML remains in the frozen package.
diff --git a/README.md b/README.md
index 9c4ff23..55dc57d 100644
--- a/README.md
+++ b/README.md
@@ -1,69 +1,44 @@
-# MathGov Human Interface and Orchestration Standard v0.8
+# MHIOS — Human Interface and Orchestration Standard
-**Release:** `MHIOS_v0_8+2026.08.15.3`
-**Status:** Candidate experimental implementation companion
-**Exact tested Core:** `MathGov_Core_2026_09_v12.6_SGP_v8.5+2026.08.15.3`
-**Exact tested Core ZIP:** `MathGov_Core_2026_09_v12_6_SGP_v8_5_BUILD_2026_08_15_3_FINAL_PUBLICATION_READY.zip`
-**Core ZIP SHA-256:** `475c4e50da133d6eec497d9cf7da7bbf6e7f7d9d79ce27f0d86b03fdbfccd69f`
-**Construct validity:** `UNTESTED`
+**Version 2.1 · Core v13.0 Release I · SGP v8.8 · Apache-2.0**
-MHIOS translates the frozen MathGov decision architecture into auditable human, institutional, and machine interaction records. Version 0.8 adds recursive-successor governance controls without adding a MathGov gate, altering the five-stage cascade, creating a new authority source, or modifying any Union Scope or Welfare Dimension.
+MHIOS helps people inspect decision evidence, qualification, uncertainty, responsibility and handoffs. It keeps a framework verdict, an accountable choice, execution authorization and observed outcomes distinct. It is a companion to MathGov / RippleLogic, not a sixteenth Core document or an authorization service.
-## v0.8 governing addition
+**[Read online](https://mathgov.github.io/mhios/)** · **[Download the complete publication](https://github.com/MathGov/mhios/releases/tag/v2.1-core13.0)** · [Standard PDF](releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.pdf) · [Editable Word](releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.docx) · [Semantic Markdown source](releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.md)
-> **Derivation is not authorization. Intelligence may create a candidate successor; it may not create the successor's authority.**
+## What is included
-Version 0.8 adds and consolidates:
+- Complete 41-page standard in Markdown, HTML, PDF and DOCX.
+- Fourteen-sheet preparation workbook; schemas, an intentionally incomplete draft and six completed synthetic examples.
+- Bounded, read-only record-consistency checker and 133 automated tests.
+- All fifteen unchanged Core source files, pinned individually by SHA-256.
+- [Audit and improvements](releases/v2.1/release/AUDIT_AND_IMPROVEMENTS.md), [verification scope](releases/v2.1/release/VERIFICATION_REPORT.md), [coverage register](releases/v2.1/release/CONFORMANCE_COVERAGE.csv), and [migration guide](releases/v2.1/release/MIGRATION_GUIDE.md).
-- `SuccessorRequalificationRecord` as the 47th object type;
-- parent/candidate lineage and material-change deltas;
-- default denial of authority inheritance;
-- exact candidate configuration binding;
-- candidate locks before fresh qualification and authorization;
-- maximum unreviewed generation-depth controls;
-- independent non-AI review of material successor changes;
-- evaluation-validity expiry and fresh evidence requirements;
-- five expected-failure successor vectors, one positive vector, and four successor-specific seeded mutations;
-- a dedicated Successor and Material-Change Requalification Standard.
-- registry traceability for all 70 active conformance vectors, with release failure on unmapped active vectors;
-- explicit C0-C3 conformance profiles and a structural profile evaluator;
-- non-confounded burden measures and a preregistration-ready, anti-priming inter-rater reliability protocol.
+The Markdown standard owns MHIOS semantic text. Its Word, PDF and HTML files are reading projections. Core semantics remain owned by the pinned Core sources. The preparation workbook checks declared tokens and reference presence; it does not calculate Canon scores or decide whether evidence is true.
-## Reading order
+## Exact edition and verification
-1. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf` - full reading copy.
-2. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx` - editable reading mirror.
-3. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md` - governing semantic source for this package.
-4. `docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md` - focused recursive-successor specification.
-5. `registries/MHIOS_OBJECT_MODEL_v0_8.yaml` - 47-object catalogue.
-6. `schemas/mhios_run_export_v0_8.schema.json` - structural run-export schema.
-7. `tests/validate_mhios.py` - schema and semantic validator.
-8. `tests/conformance_vectors/` - 6 positive and 64 expected-failure vectors.
-9. `tests/mutation_test_mhios.py` - 45 seeded mutations.
-10. `docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md` - empirical burden and hollow-run measurement protocol.
-11. `docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md` - preregistration-ready reviewer-reliability protocol.
-12. `registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml` - explicit C0-C3 structural conformance profiles.
-13. `release/VALIDATION_REPORT.md` - artifact and claim-boundary report.
+Build: `MG-MHIOS-2.1-20260928-CORE13.0`. Core: `MG-RL-13.0-20260926-RELEASE-I`. The supplied 86-file publication is preserved without edits under `releases/v2.1/`; repository navigation and hosting records are separate.
-## Core compatibility and precedence
+Use Python 3.10 or newer in an isolated environment. On Windows, set `PYTHONUTF8=1` before running the supplied tools (PowerShell: `$env:PYTHONUTF8='1'`).
-The exact tested Core build controls all MathGov semantics. MHIOS controls only the implementation, interaction, provenance, audit, and runtime-orchestration surfaces declared in this package. A later or different Core build requires an explicit compatibility review; version numbering alone does not establish compatibility.
+```sh
+python -m pip install -r requirements.txt
+python -B releases/v2.1/verify_all.py --output-dir verification-output
+```
-## Claim boundary
+The recommended publication-edition ZIP includes the required date-time dependency and a top-level README. Use that README; the preserved original package requirements omit `rfc3339-validator==0.1.4`. For an original ZIP checkout, add that dependency explicitly. Verification output must be outside the frozen package. `--at 2026-09-28T12:00:00Z` replays synthetic fixtures; it never revives real permission. The checker success label is `RECORD_CONSISTENT_WITHIN_SCOPED_CHECKS`, never authorization.
-Passing the included validators establishes package consistency against the encoded checks. It does not establish legal authority, physical safety, construct validity, empirical effectiveness, burden reduction, reviewer agreement, or deployment readiness in a particular domain.
+See [publication audit](PUBLICATION.md) and [CI results](https://github.com/MathGov/mhios/actions). The tests cover only their declared scope. No empirical effectiveness, production readiness, M2/M3 deployed-interface conformance, complete external Canon schemas/registries, native Excel interoperability or real authority is established.
-## License
+## Version lineage and history
-See `LICENSE` and `NOTICE`.
+GitHub previously published v0.8. The supplied v2.1 package identifies a privately retained v2.0 source baseline; its internal v2.0 migration guide is not an automatic migration path from v0.8. The v0.8 repository snapshot is preserved in [archive/v0.8](archive/v0.8), and its [original fixed release](https://github.com/MathGov/mhios/releases/tag/v0.8) remains available. Do not relabel or silently migrate old records.
-## Computational Context Declaration
+This release uses a new M0–M3 interface-conformance vocabulary and bounded implementation. Historical v0.8 test counts, object inventories and C0–C3 claims do not transfer to v2.1. Private provenance was not supplied in this publication ZIP and is not published here.
-For material computational systems, MHIOS v0.8 presents a compact derived view of the computational problem/object, exact architecture and configuration, demonstrated capability, assigned task, deployment domain, required evidence standard, consequence interface, and separate legitimate authority basis. **Consequence Interface is not Legitimate Authority.** The view does not create a new gate or new authority source.
-## Related MathGov Repositories
+## Reuse, citation and contribution
-- **MathGov / RippleLogic Core**
- The canonical ethical decision architecture that MHIOS operationalizes around.
- https://github.com/MathGov/ripple-logic
+The supplied edition is Apache-2.0; see [LICENSE](LICENSE), [NOTICE](NOTICE.md) and [citation metadata](CITATION.cff). Retain notices and identify modifications. External informative standards keep their own rights and are not incorporated or certified by linking them.
-MHIOS preserves the MathGov Core decision architecture and does not redefine its gates, rights floor, tail-risk constraints, CSV semantics, RippleLogic scoring, Union Scopes, or Welfare Dimensions.
\ No newline at end of file
+[Report a reproducible issue](https://github.com/MathGov/mhios/issues) · [Contribute](CONTRIBUTING.md) · [Security scope](SECURITY.md) · [MathGov directory](https://github.com/MathGov) · [Core v13](https://github.com/MathGov/ripple-logic) · [RippleLogic](https://ripplelogic.org/) · [MathGov foundation](https://mathgov.org/) · [Contact James](mailto:james@ripplelogic.org)
diff --git a/SECURITY.md b/SECURITY.md
new file mode 100644
index 0000000..6c0aae2
--- /dev/null
+++ b/SECURITY.md
@@ -0,0 +1,5 @@
+# Security and claim scope
+
+This repository publishes a read-only research checker and static reading site, not an operational authorization service. Never treat its success output as permission to execute.
+
+For a vulnerability involving data exposure or an unsafe implementation path, contact james@ripplelogic.org without publishing secrets or personal records. Include version, affected code and a synthetic reproduction. Ordinary reproducible research issues can use GitHub Issues. No guaranteed response time or independent security certification is claimed.
diff --git a/archive/README.md b/archive/README.md
new file mode 100644
index 0000000..fa73af3
--- /dev/null
+++ b/archive/README.md
@@ -0,0 +1,3 @@
+# Historical MHIOS editions
+
+`v0.8/` preserves the repository files before v2.1 publication. Their versioned claims and dependencies are historical. For the original byte-frozen distribution and its strict verifier, use the original v0.8 GitHub release asset. Current visitors should start at the repository README and `releases/v2.1/`.
diff --git a/CHANGELOG.md b/archive/v0.8/CHANGELOG.md
similarity index 100%
rename from CHANGELOG.md
rename to archive/v0.8/CHANGELOG.md
diff --git a/archive/v0.8/LICENSE b/archive/v0.8/LICENSE
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/archive/v0.8/LICENSE
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/NOTICE b/archive/v0.8/NOTICE
similarity index 100%
rename from NOTICE
rename to archive/v0.8/NOTICE
diff --git a/archive/v0.8/README.md b/archive/v0.8/README.md
new file mode 100644
index 0000000..9c4ff23
--- /dev/null
+++ b/archive/v0.8/README.md
@@ -0,0 +1,69 @@
+# MathGov Human Interface and Orchestration Standard v0.8
+
+**Release:** `MHIOS_v0_8+2026.08.15.3`
+**Status:** Candidate experimental implementation companion
+**Exact tested Core:** `MathGov_Core_2026_09_v12.6_SGP_v8.5+2026.08.15.3`
+**Exact tested Core ZIP:** `MathGov_Core_2026_09_v12_6_SGP_v8_5_BUILD_2026_08_15_3_FINAL_PUBLICATION_READY.zip`
+**Core ZIP SHA-256:** `475c4e50da133d6eec497d9cf7da7bbf6e7f7d9d79ce27f0d86b03fdbfccd69f`
+**Construct validity:** `UNTESTED`
+
+MHIOS translates the frozen MathGov decision architecture into auditable human, institutional, and machine interaction records. Version 0.8 adds recursive-successor governance controls without adding a MathGov gate, altering the five-stage cascade, creating a new authority source, or modifying any Union Scope or Welfare Dimension.
+
+## v0.8 governing addition
+
+> **Derivation is not authorization. Intelligence may create a candidate successor; it may not create the successor's authority.**
+
+Version 0.8 adds and consolidates:
+
+- `SuccessorRequalificationRecord` as the 47th object type;
+- parent/candidate lineage and material-change deltas;
+- default denial of authority inheritance;
+- exact candidate configuration binding;
+- candidate locks before fresh qualification and authorization;
+- maximum unreviewed generation-depth controls;
+- independent non-AI review of material successor changes;
+- evaluation-validity expiry and fresh evidence requirements;
+- five expected-failure successor vectors, one positive vector, and four successor-specific seeded mutations;
+- a dedicated Successor and Material-Change Requalification Standard.
+- registry traceability for all 70 active conformance vectors, with release failure on unmapped active vectors;
+- explicit C0-C3 conformance profiles and a structural profile evaluator;
+- non-confounded burden measures and a preregistration-ready, anti-priming inter-rater reliability protocol.
+
+## Reading order
+
+1. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf` - full reading copy.
+2. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx` - editable reading mirror.
+3. `docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md` - governing semantic source for this package.
+4. `docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md` - focused recursive-successor specification.
+5. `registries/MHIOS_OBJECT_MODEL_v0_8.yaml` - 47-object catalogue.
+6. `schemas/mhios_run_export_v0_8.schema.json` - structural run-export schema.
+7. `tests/validate_mhios.py` - schema and semantic validator.
+8. `tests/conformance_vectors/` - 6 positive and 64 expected-failure vectors.
+9. `tests/mutation_test_mhios.py` - 45 seeded mutations.
+10. `docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md` - empirical burden and hollow-run measurement protocol.
+11. `docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md` - preregistration-ready reviewer-reliability protocol.
+12. `registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml` - explicit C0-C3 structural conformance profiles.
+13. `release/VALIDATION_REPORT.md` - artifact and claim-boundary report.
+
+## Core compatibility and precedence
+
+The exact tested Core build controls all MathGov semantics. MHIOS controls only the implementation, interaction, provenance, audit, and runtime-orchestration surfaces declared in this package. A later or different Core build requires an explicit compatibility review; version numbering alone does not establish compatibility.
+
+## Claim boundary
+
+Passing the included validators establishes package consistency against the encoded checks. It does not establish legal authority, physical safety, construct validity, empirical effectiveness, burden reduction, reviewer agreement, or deployment readiness in a particular domain.
+
+## License
+
+See `LICENSE` and `NOTICE`.
+
+## Computational Context Declaration
+
+For material computational systems, MHIOS v0.8 presents a compact derived view of the computational problem/object, exact architecture and configuration, demonstrated capability, assigned task, deployment domain, required evidence standard, consequence interface, and separate legitimate authority basis. **Consequence Interface is not Legitimate Authority.** The view does not create a new gate or new authority source.
+## Related MathGov Repositories
+
+- **MathGov / RippleLogic Core**
+ The canonical ethical decision architecture that MHIOS operationalizes around.
+ https://github.com/MathGov/ripple-logic
+
+MHIOS preserves the MathGov Core decision architecture and does not redefine its gates, rights floor, tail-risk constraints, CSV semantics, RippleLogic scoring, Union Scopes, or Welfare Dimensions.
\ No newline at end of file
diff --git a/VERSION.yaml b/archive/v0.8/VERSION.yaml
similarity index 100%
rename from VERSION.yaml
rename to archive/v0.8/VERSION.yaml
diff --git a/docs/AI_ASSISTANCE_AND_HUMAN_JUDGMENT_FIREWALL_v0_8.md b/archive/v0.8/docs/AI_ASSISTANCE_AND_HUMAN_JUDGMENT_FIREWALL_v0_8.md
similarity index 100%
rename from docs/AI_ASSISTANCE_AND_HUMAN_JUDGMENT_FIREWALL_v0_8.md
rename to archive/v0.8/docs/AI_ASSISTANCE_AND_HUMAN_JUDGMENT_FIREWALL_v0_8.md
diff --git a/docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md b/archive/v0.8/docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md
similarity index 100%
rename from docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md
rename to archive/v0.8/docs/BURDEN_MEASUREMENT_PROTOCOL_v0_8.md
diff --git a/docs/IMPLEMENTATION_INTEGRITY_PROFILE_v0_8.md b/archive/v0.8/docs/IMPLEMENTATION_INTEGRITY_PROFILE_v0_8.md
similarity index 100%
rename from docs/IMPLEMENTATION_INTEGRITY_PROFILE_v0_8.md
rename to archive/v0.8/docs/IMPLEMENTATION_INTEGRITY_PROFILE_v0_8.md
diff --git a/docs/IMPLEMENTATION_ROADMAP_v0_8.md b/archive/v0.8/docs/IMPLEMENTATION_ROADMAP_v0_8.md
similarity index 100%
rename from docs/IMPLEMENTATION_ROADMAP_v0_8.md
rename to archive/v0.8/docs/IMPLEMENTATION_ROADMAP_v0_8.md
diff --git a/docs/INSTITUTIONAL_PRECONDITIONS_PROFILE_v0_8.md b/archive/v0.8/docs/INSTITUTIONAL_PRECONDITIONS_PROFILE_v0_8.md
similarity index 100%
rename from docs/INSTITUTIONAL_PRECONDITIONS_PROFILE_v0_8.md
rename to archive/v0.8/docs/INSTITUTIONAL_PRECONDITIONS_PROFILE_v0_8.md
diff --git a/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx b/archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx
similarity index 100%
rename from docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx
rename to archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.docx
diff --git a/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md b/archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md
similarity index 100%
rename from docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md
rename to archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.md
diff --git a/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf b/archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf
similarity index 100%
rename from docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf
rename to archive/v0.8/docs/MATHGOV_HUMAN_INTERFACE_AND_ORCHESTRATION_STANDARD_v0_8.pdf
diff --git a/docs/MHIOS_FEEDBACK_DISPOSITION_v0_4.md b/archive/v0.8/docs/MHIOS_FEEDBACK_DISPOSITION_v0_4.md
similarity index 100%
rename from docs/MHIOS_FEEDBACK_DISPOSITION_v0_4.md
rename to archive/v0.8/docs/MHIOS_FEEDBACK_DISPOSITION_v0_4.md
diff --git a/docs/MHIOS_MATHGOV_CORE_INTEGRATION_PROFILE_v0_8.md b/archive/v0.8/docs/MHIOS_MATHGOV_CORE_INTEGRATION_PROFILE_v0_8.md
similarity index 100%
rename from docs/MHIOS_MATHGOV_CORE_INTEGRATION_PROFILE_v0_8.md
rename to archive/v0.8/docs/MHIOS_MATHGOV_CORE_INTEGRATION_PROFILE_v0_8.md
diff --git a/docs/MHIOS_MINIMAL_VERTICAL_SLICE_PROFILE_v0_8.md b/archive/v0.8/docs/MHIOS_MINIMAL_VERTICAL_SLICE_PROFILE_v0_8.md
similarity index 100%
rename from docs/MHIOS_MINIMAL_VERTICAL_SLICE_PROFILE_v0_8.md
rename to archive/v0.8/docs/MHIOS_MINIMAL_VERTICAL_SLICE_PROFILE_v0_8.md
diff --git a/docs/MHIOS_MVP_SCREEN_FLOW_v0_8.md b/archive/v0.8/docs/MHIOS_MVP_SCREEN_FLOW_v0_8.md
similarity index 100%
rename from docs/MHIOS_MVP_SCREEN_FLOW_v0_8.md
rename to archive/v0.8/docs/MHIOS_MVP_SCREEN_FLOW_v0_8.md
diff --git a/docs/MHIOS_SELF_ASSESSMENT_AND_CLAIM_BOUNDARY_v0_8.md b/archive/v0.8/docs/MHIOS_SELF_ASSESSMENT_AND_CLAIM_BOUNDARY_v0_8.md
similarity index 100%
rename from docs/MHIOS_SELF_ASSESSMENT_AND_CLAIM_BOUNDARY_v0_8.md
rename to archive/v0.8/docs/MHIOS_SELF_ASSESSMENT_AND_CLAIM_BOUNDARY_v0_8.md
diff --git a/docs/MHIOS_V0_2_CLAUDE_OPUS_FEEDBACK_DISPOSITION.md b/archive/v0.8/docs/MHIOS_V0_2_CLAUDE_OPUS_FEEDBACK_DISPOSITION.md
similarity index 100%
rename from docs/MHIOS_V0_2_CLAUDE_OPUS_FEEDBACK_DISPOSITION.md
rename to archive/v0.8/docs/MHIOS_V0_2_CLAUDE_OPUS_FEEDBACK_DISPOSITION.md
diff --git a/docs/MHIOS_V0_5_INDEPENDENT_FEEDBACK_DISPOSITION.md b/archive/v0.8/docs/MHIOS_V0_5_INDEPENDENT_FEEDBACK_DISPOSITION.md
similarity index 100%
rename from docs/MHIOS_V0_5_INDEPENDENT_FEEDBACK_DISPOSITION.md
rename to archive/v0.8/docs/MHIOS_V0_5_INDEPENDENT_FEEDBACK_DISPOSITION.md
diff --git a/docs/MHIOS_V0_7_INDEPENDENCE_AND_ACTION_BINDING_REPORT.md b/archive/v0.8/docs/MHIOS_V0_7_INDEPENDENCE_AND_ACTION_BINDING_REPORT.md
similarity index 100%
rename from docs/MHIOS_V0_7_INDEPENDENCE_AND_ACTION_BINDING_REPORT.md
rename to archive/v0.8/docs/MHIOS_V0_7_INDEPENDENCE_AND_ACTION_BINDING_REPORT.md
diff --git a/docs/MHIOS_v0_3_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md b/archive/v0.8/docs/MHIOS_v0_3_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
similarity index 100%
rename from docs/MHIOS_v0_3_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
rename to archive/v0.8/docs/MHIOS_v0_3_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
diff --git a/docs/MHIOS_v0_4_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md b/archive/v0.8/docs/MHIOS_v0_4_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
similarity index 100%
rename from docs/MHIOS_v0_4_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
rename to archive/v0.8/docs/MHIOS_v0_4_CORE_BUILD_COMPATIBILITY_AND_COMPLETION_REPORT.md
diff --git a/docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md b/archive/v0.8/docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md
similarity index 100%
rename from docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md
rename to archive/v0.8/docs/PILOT_AND_INTER_RATER_RELIABILITY_PROTOCOL_v0_8.md
diff --git a/docs/SECURITY_PRIVACY_AND_ACCESS_PROFILE_v0_8.md b/archive/v0.8/docs/SECURITY_PRIVACY_AND_ACCESS_PROFILE_v0_8.md
similarity index 100%
rename from docs/SECURITY_PRIVACY_AND_ACCESS_PROFILE_v0_8.md
rename to archive/v0.8/docs/SECURITY_PRIVACY_AND_ACCESS_PROFILE_v0_8.md
diff --git a/docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md b/archive/v0.8/docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md
similarity index 100%
rename from docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md
rename to archive/v0.8/docs/SUCCESSOR_AND_MATERIAL_CHANGE_REQUALIFICATION_STANDARD_v0_8.md
diff --git a/examples/README.md b/archive/v0.8/examples/README.md
similarity index 100%
rename from examples/README.md
rename to archive/v0.8/examples/README.md
diff --git a/examples/tier1_office_procurement.json b/archive/v0.8/examples/tier1_office_procurement.json
similarity index 100%
rename from examples/tier1_office_procurement.json
rename to archive/v0.8/examples/tier1_office_procurement.json
diff --git a/examples/tier2_remote_work_policy.json b/archive/v0.8/examples/tier2_remote_work_policy.json
similarity index 100%
rename from examples/tier2_remote_work_policy.json
rename to archive/v0.8/examples/tier2_remote_work_policy.json
diff --git a/examples/tier3_autonomous_shuttle_pilot.json b/archive/v0.8/examples/tier3_autonomous_shuttle_pilot.json
similarity index 100%
rename from examples/tier3_autonomous_shuttle_pilot.json
rename to archive/v0.8/examples/tier3_autonomous_shuttle_pilot.json
diff --git a/registries/MHIOS_ANTI_AUDIT_THEATER_PATTERNS_v0_8.yaml b/archive/v0.8/registries/MHIOS_ANTI_AUDIT_THEATER_PATTERNS_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_ANTI_AUDIT_THEATER_PATTERNS_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_ANTI_AUDIT_THEATER_PATTERNS_v0_8.yaml
diff --git a/registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml b/archive/v0.8/registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_CONFORMANCE_PROFILE_v0_8.yaml
diff --git a/registries/MHIOS_CORE_RECORD_COVERAGE_v0_8.yaml b/archive/v0.8/registries/MHIOS_CORE_RECORD_COVERAGE_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_CORE_RECORD_COVERAGE_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_CORE_RECORD_COVERAGE_v0_8.yaml
diff --git a/registries/MHIOS_EXECUTABLE_CHECK_REGISTRY_v0_8.yaml b/archive/v0.8/registries/MHIOS_EXECUTABLE_CHECK_REGISTRY_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_EXECUTABLE_CHECK_REGISTRY_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_EXECUTABLE_CHECK_REGISTRY_v0_8.yaml
diff --git a/registries/MHIOS_MVS_SCREEN_REGISTRY_v0_8.yaml b/archive/v0.8/registries/MHIOS_MVS_SCREEN_REGISTRY_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_MVS_SCREEN_REGISTRY_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_MVS_SCREEN_REGISTRY_v0_8.yaml
diff --git a/registries/MHIOS_OBJECT_JUSTIFICATION_LEDGER_v0_8.yaml b/archive/v0.8/registries/MHIOS_OBJECT_JUSTIFICATION_LEDGER_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_OBJECT_JUSTIFICATION_LEDGER_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_OBJECT_JUSTIFICATION_LEDGER_v0_8.yaml
diff --git a/registries/MHIOS_OBJECT_MODEL_v0_8.yaml b/archive/v0.8/registries/MHIOS_OBJECT_MODEL_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_OBJECT_MODEL_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_OBJECT_MODEL_v0_8.yaml
diff --git a/registries/MHIOS_PROVENANCE_ORIGIN_REGISTRY_v0_8.yaml b/archive/v0.8/registries/MHIOS_PROVENANCE_ORIGIN_REGISTRY_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_PROVENANCE_ORIGIN_REGISTRY_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_PROVENANCE_ORIGIN_REGISTRY_v0_8.yaml
diff --git a/registries/MHIOS_SCREEN_REGISTRY_v0_8.yaml b/archive/v0.8/registries/MHIOS_SCREEN_REGISTRY_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_SCREEN_REGISTRY_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_SCREEN_REGISTRY_v0_8.yaml
diff --git a/registries/MHIOS_STATE_AND_ROLE_MAP_v0_8.yaml b/archive/v0.8/registries/MHIOS_STATE_AND_ROLE_MAP_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_STATE_AND_ROLE_MAP_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_STATE_AND_ROLE_MAP_v0_8.yaml
diff --git a/registries/MHIOS_TO_CORE_SCHEMA_CROSSWALK_v0_8.yaml b/archive/v0.8/registries/MHIOS_TO_CORE_SCHEMA_CROSSWALK_v0_8.yaml
similarity index 100%
rename from registries/MHIOS_TO_CORE_SCHEMA_CROSSWALK_v0_8.yaml
rename to archive/v0.8/registries/MHIOS_TO_CORE_SCHEMA_CROSSWALK_v0_8.yaml
diff --git a/release/DOCX_ACCESSIBILITY_AUDIT.json b/archive/v0.8/release/DOCX_ACCESSIBILITY_AUDIT.json
similarity index 100%
rename from release/DOCX_ACCESSIBILITY_AUDIT.json
rename to archive/v0.8/release/DOCX_ACCESSIBILITY_AUDIT.json
diff --git a/release/FINAL_VERIFICATION.txt b/archive/v0.8/release/FINAL_VERIFICATION.txt
similarity index 100%
rename from release/FINAL_VERIFICATION.txt
rename to archive/v0.8/release/FINAL_VERIFICATION.txt
diff --git a/release/HEADING_AUDIT.txt b/archive/v0.8/release/HEADING_AUDIT.txt
similarity index 100%
rename from release/HEADING_AUDIT.txt
rename to archive/v0.8/release/HEADING_AUDIT.txt
diff --git a/release/IMAGES_AUDIT.txt b/archive/v0.8/release/IMAGES_AUDIT.txt
similarity index 100%
rename from release/IMAGES_AUDIT.txt
rename to archive/v0.8/release/IMAGES_AUDIT.txt
diff --git a/release/MHIOS_V0_2_FEEDBACK_AND_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_2_FEEDBACK_AND_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_2_FEEDBACK_AND_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_2_FEEDBACK_AND_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_3_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_3_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_3_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_3_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_4_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_4_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_4_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_4_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_5_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_5_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_5_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_5_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_7_BUILD_2026_08_10_1_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_7_BUILD_2026_08_10_1_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_7_BUILD_2026_08_10_1_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_7_BUILD_2026_08_10_1_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_7_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_7_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_7_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_7_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_8_BUILD_2026_08_14_1_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_14_1_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_8_BUILD_2026_08_14_1_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_14_1_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_8_BUILD_2026_08_14_2_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_14_2_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_8_BUILD_2026_08_14_2_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_14_2_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_8_BUILD_2026_08_15_1_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_1_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_8_BUILD_2026_08_15_1_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_1_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_8_BUILD_2026_08_15_2_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_2_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_8_BUILD_2026_08_15_2_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_2_CHANGE_LEDGER.json
diff --git a/release/MHIOS_V0_8_BUILD_2026_08_15_3_CHANGE_LEDGER.json b/archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_3_CHANGE_LEDGER.json
similarity index 100%
rename from release/MHIOS_V0_8_BUILD_2026_08_15_3_CHANGE_LEDGER.json
rename to archive/v0.8/release/MHIOS_V0_8_BUILD_2026_08_15_3_CHANGE_LEDGER.json
diff --git a/release/MUTATION_TEST_REPORT.json b/archive/v0.8/release/MUTATION_TEST_REPORT.json
similarity index 100%
rename from release/MUTATION_TEST_REPORT.json
rename to archive/v0.8/release/MUTATION_TEST_REPORT.json
diff --git a/release/NORMATIVE_COVERAGE_REPORT.json b/archive/v0.8/release/NORMATIVE_COVERAGE_REPORT.json
similarity index 100%
rename from release/NORMATIVE_COVERAGE_REPORT.json
rename to archive/v0.8/release/NORMATIVE_COVERAGE_REPORT.json
diff --git a/release/PDF_PREFLIGHT.json b/archive/v0.8/release/PDF_PREFLIGHT.json
similarity index 100%
rename from release/PDF_PREFLIGHT.json
rename to archive/v0.8/release/PDF_PREFLIGHT.json
diff --git a/release/PDF_PREFLIGHT.txt b/archive/v0.8/release/PDF_PREFLIGHT.txt
similarity index 100%
rename from release/PDF_PREFLIGHT.txt
rename to archive/v0.8/release/PDF_PREFLIGHT.txt
diff --git a/release/RELEASE_MANIFEST.json b/archive/v0.8/release/RELEASE_MANIFEST.json
similarity index 100%
rename from release/RELEASE_MANIFEST.json
rename to archive/v0.8/release/RELEASE_MANIFEST.json
diff --git a/release/SHA256SUMS.txt b/archive/v0.8/release/SHA256SUMS.txt
similarity index 100%
rename from release/SHA256SUMS.txt
rename to archive/v0.8/release/SHA256SUMS.txt
diff --git a/release/TEST_RESULTS_v0_8.txt b/archive/v0.8/release/TEST_RESULTS_v0_8.txt
similarity index 100%
rename from release/TEST_RESULTS_v0_8.txt
rename to archive/v0.8/release/TEST_RESULTS_v0_8.txt
diff --git a/release/VALIDATION_REPORT.md b/archive/v0.8/release/VALIDATION_REPORT.md
similarity index 100%
rename from release/VALIDATION_REPORT.md
rename to archive/v0.8/release/VALIDATION_REPORT.md
diff --git a/release/VERIFY_MHIOS_PACKAGE.py b/archive/v0.8/release/VERIFY_MHIOS_PACKAGE.py
similarity index 100%
rename from release/VERIFY_MHIOS_PACKAGE.py
rename to archive/v0.8/release/VERIFY_MHIOS_PACKAGE.py
diff --git a/schemas/mhios_interaction_event_v0_8.schema.json b/archive/v0.8/schemas/mhios_interaction_event_v0_8.schema.json
similarity index 100%
rename from schemas/mhios_interaction_event_v0_8.schema.json
rename to archive/v0.8/schemas/mhios_interaction_event_v0_8.schema.json
diff --git a/schemas/mhios_run_export_v0_8.schema.json b/archive/v0.8/schemas/mhios_run_export_v0_8.schema.json
similarity index 100%
rename from schemas/mhios_run_export_v0_8.schema.json
rename to archive/v0.8/schemas/mhios_run_export_v0_8.schema.json
diff --git a/tests/TEST_PLAN.md b/archive/v0.8/tests/TEST_PLAN.md
similarity index 100%
rename from tests/TEST_PLAN.md
rename to archive/v0.8/tests/TEST_PLAN.md
diff --git a/tests/conformance_vectors/fail_ai_authorized_without_human_review.json b/archive/v0.8/tests/conformance_vectors/fail_ai_authorized_without_human_review.json
similarity index 100%
rename from tests/conformance_vectors/fail_ai_authorized_without_human_review.json
rename to archive/v0.8/tests/conformance_vectors/fail_ai_authorized_without_human_review.json
diff --git a/tests/conformance_vectors/fail_ai_gate_material_without_first_pass.json b/archive/v0.8/tests/conformance_vectors/fail_ai_gate_material_without_first_pass.json
similarity index 100%
rename from tests/conformance_vectors/fail_ai_gate_material_without_first_pass.json
rename to archive/v0.8/tests/conformance_vectors/fail_ai_gate_material_without_first_pass.json
diff --git a/tests/conformance_vectors/fail_ai_origin_missing_review.json b/archive/v0.8/tests/conformance_vectors/fail_ai_origin_missing_review.json
similarity index 100%
rename from tests/conformance_vectors/fail_ai_origin_missing_review.json
rename to archive/v0.8/tests/conformance_vectors/fail_ai_origin_missing_review.json
diff --git a/tests/conformance_vectors/fail_authorization_without_named_authority.json b/archive/v0.8/tests/conformance_vectors/fail_authorization_without_named_authority.json
similarity index 100%
rename from tests/conformance_vectors/fail_authorization_without_named_authority.json
rename to archive/v0.8/tests/conformance_vectors/fail_authorization_without_named_authority.json
diff --git a/tests/conformance_vectors/fail_c2_without_institutional_preconditions.json b/archive/v0.8/tests/conformance_vectors/fail_c2_without_institutional_preconditions.json
similarity index 100%
rename from tests/conformance_vectors/fail_c2_without_institutional_preconditions.json
rename to archive/v0.8/tests/conformance_vectors/fail_c2_without_institutional_preconditions.json
diff --git a/tests/conformance_vectors/fail_capability_decomposition_compound_field_v04.json b/archive/v0.8/tests/conformance_vectors/fail_capability_decomposition_compound_field_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_capability_decomposition_compound_field_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_capability_decomposition_compound_field_v04.json
diff --git a/tests/conformance_vectors/fail_capability_decomposition_missing_safe_state_v04.json b/archive/v0.8/tests/conformance_vectors/fail_capability_decomposition_missing_safe_state_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_capability_decomposition_missing_safe_state_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_capability_decomposition_missing_safe_state_v04.json
diff --git a/tests/conformance_vectors/fail_computational_context_assigned_task_as_justified_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_assigned_task_as_justified_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_assigned_task_as_justified_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_assigned_task_as_justified_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_capability_as_authority_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_capability_as_authority_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_capability_as_authority_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_capability_as_authority_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_capability_outside_domain_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_capability_outside_domain_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_capability_outside_domain_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_capability_outside_domain_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_interface_as_authority_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_interface_as_authority_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_interface_as_authority_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_interface_as_authority_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_missing_configuration_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_missing_configuration_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_missing_configuration_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_missing_configuration_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_missing_for_material_run_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_missing_for_material_run_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_missing_for_material_run_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_missing_for_material_run_v08.json
diff --git a/tests/conformance_vectors/fail_computational_context_stale_after_configuration_change_v08.json b/archive/v0.8/tests/conformance_vectors/fail_computational_context_stale_after_configuration_change_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_computational_context_stale_after_configuration_change_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_computational_context_stale_after_configuration_change_v08.json
diff --git a/tests/conformance_vectors/fail_contradictory_decisiveness.json b/archive/v0.8/tests/conformance_vectors/fail_contradictory_decisiveness.json
similarity index 100%
rename from tests/conformance_vectors/fail_contradictory_decisiveness.json
rename to archive/v0.8/tests/conformance_vectors/fail_contradictory_decisiveness.json
diff --git a/tests/conformance_vectors/fail_csv_constitutive_control_without_obligation_v05.json b/archive/v0.8/tests/conformance_vectors/fail_csv_constitutive_control_without_obligation_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_csv_constitutive_control_without_obligation_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_csv_constitutive_control_without_obligation_v05.json
diff --git a/tests/conformance_vectors/fail_csv_pass_with_controls_unlinked_v04.json b/archive/v0.8/tests/conformance_vectors/fail_csv_pass_with_controls_unlinked_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_csv_pass_with_controls_unlinked_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_csv_pass_with_controls_unlinked_v04.json
diff --git a/tests/conformance_vectors/fail_current_view_with_source_mismatch.json b/archive/v0.8/tests/conformance_vectors/fail_current_view_with_source_mismatch.json
similarity index 100%
rename from tests/conformance_vectors/fail_current_view_with_source_mismatch.json
rename to archive/v0.8/tests/conformance_vectors/fail_current_view_with_source_mismatch.json
diff --git a/tests/conformance_vectors/fail_dangling_source_link.json b/archive/v0.8/tests/conformance_vectors/fail_dangling_source_link.json
similarity index 100%
rename from tests/conformance_vectors/fail_dangling_source_link.json
rename to archive/v0.8/tests/conformance_vectors/fail_dangling_source_link.json
diff --git a/tests/conformance_vectors/fail_emergency_without_order_record_v04.json b/archive/v0.8/tests/conformance_vectors/fail_emergency_without_order_record_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_emergency_without_order_record_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_emergency_without_order_record_v04.json
diff --git a/tests/conformance_vectors/fail_execution_authorization_expired_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_authorization_expired_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_authorization_expired_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_authorization_expired_v07.json
diff --git a/tests/conformance_vectors/fail_execution_authorization_not_yet_effective_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_authorization_not_yet_effective_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_authorization_not_yet_effective_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_authorization_not_yet_effective_v07.json
diff --git a/tests/conformance_vectors/fail_execution_blank_authorization_basis_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_blank_authorization_basis_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_blank_authorization_basis_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_blank_authorization_basis_v07.json
diff --git a/tests/conformance_vectors/fail_execution_empty_controls_without_disposition_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_empty_controls_without_disposition_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_empty_controls_without_disposition_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_empty_controls_without_disposition_v07.json
diff --git a/tests/conformance_vectors/fail_execution_empty_preconditions_without_disposition_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_empty_preconditions_without_disposition_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_empty_preconditions_without_disposition_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_empty_preconditions_without_disposition_v07.json
diff --git a/tests/conformance_vectors/fail_execution_inactive_required_control_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_inactive_required_control_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_inactive_required_control_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_inactive_required_control_v07.json
diff --git a/tests/conformance_vectors/fail_execution_invalid_action_specification_hash_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_invalid_action_specification_hash_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_invalid_action_specification_hash_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_invalid_action_specification_hash_v07.json
diff --git a/tests/conformance_vectors/fail_execution_invalid_qualification_snapshot_hash_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_invalid_qualification_snapshot_hash_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_invalid_qualification_snapshot_hash_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_invalid_qualification_snapshot_hash_v07.json
diff --git a/tests/conformance_vectors/fail_execution_mandate_expired_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_mandate_expired_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_mandate_expired_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_mandate_expired_v07.json
diff --git a/tests/conformance_vectors/fail_execution_mandate_not_yet_effective_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_mandate_not_yet_effective_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_mandate_not_yet_effective_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_mandate_not_yet_effective_v07.json
diff --git a/tests/conformance_vectors/fail_execution_mandate_revoked_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_mandate_revoked_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_mandate_revoked_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_mandate_revoked_v07.json
diff --git a/tests/conformance_vectors/fail_execution_missing_action_instance_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_missing_action_instance_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_missing_action_instance_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_missing_action_instance_v07.json
diff --git a/tests/conformance_vectors/fail_execution_missing_configuration_binding_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_missing_configuration_binding_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_missing_configuration_binding_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_missing_configuration_binding_v07.json
diff --git a/tests/conformance_vectors/fail_execution_unsatisfied_precondition_v07.json b/archive/v0.8/tests/conformance_vectors/fail_execution_unsatisfied_precondition_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_execution_unsatisfied_precondition_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_execution_unsatisfied_precondition_v07.json
diff --git a/tests/conformance_vectors/fail_high_stakes_l2_without_tempo_continuity_v05.json b/archive/v0.8/tests/conformance_vectors/fail_high_stakes_l2_without_tempo_continuity_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_high_stakes_l2_without_tempo_continuity_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_high_stakes_l2_without_tempo_continuity_v05.json
diff --git a/tests/conformance_vectors/fail_invalid_responsible_role.json b/archive/v0.8/tests/conformance_vectors/fail_invalid_responsible_role.json
similarity index 100%
rename from tests/conformance_vectors/fail_invalid_responsible_role.json
rename to archive/v0.8/tests/conformance_vectors/fail_invalid_responsible_role.json
diff --git a/tests/conformance_vectors/fail_mandate_snapshot_hash_mismatch_v07.json b/archive/v0.8/tests/conformance_vectors/fail_mandate_snapshot_hash_mismatch_v07.json
similarity index 100%
rename from tests/conformance_vectors/fail_mandate_snapshot_hash_mismatch_v07.json
rename to archive/v0.8/tests/conformance_vectors/fail_mandate_snapshot_hash_mismatch_v07.json
diff --git a/tests/conformance_vectors/fail_material_human_compensation_without_record_v05.json b/archive/v0.8/tests/conformance_vectors/fail_material_human_compensation_without_record_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_material_human_compensation_without_record_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_material_human_compensation_without_record_v05.json
diff --git a/tests/conformance_vectors/fail_material_obligation_silent_field_v05.json b/archive/v0.8/tests/conformance_vectors/fail_material_obligation_silent_field_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_material_obligation_silent_field_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_material_obligation_silent_field_v05.json
diff --git a/tests/conformance_vectors/fail_mfdi_bridge_target_mismatch_v04.json b/archive/v0.8/tests/conformance_vectors/fail_mfdi_bridge_target_mismatch_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_mfdi_bridge_target_mismatch_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_mfdi_bridge_target_mismatch_v04.json
diff --git a/tests/conformance_vectors/fail_mfdi_cross_domain_bridge_missing_v04.json b/archive/v0.8/tests/conformance_vectors/fail_mfdi_cross_domain_bridge_missing_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_mfdi_cross_domain_bridge_missing_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_mfdi_cross_domain_bridge_missing_v04.json
diff --git a/tests/conformance_vectors/fail_mfdi_missing_claim_domain_v04.json b/archive/v0.8/tests/conformance_vectors/fail_mfdi_missing_claim_domain_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_mfdi_missing_claim_domain_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_mfdi_missing_claim_domain_v04.json
diff --git a/tests/conformance_vectors/fail_mfdi_missing_necessity_check.json b/archive/v0.8/tests/conformance_vectors/fail_mfdi_missing_necessity_check.json
similarity index 100%
rename from tests/conformance_vectors/fail_mfdi_missing_necessity_check.json
rename to archive/v0.8/tests/conformance_vectors/fail_mfdi_missing_necessity_check.json
diff --git a/tests/conformance_vectors/fail_mfdi_partial_bridge_proceeds_v04.json b/archive/v0.8/tests/conformance_vectors/fail_mfdi_partial_bridge_proceeds_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_mfdi_partial_bridge_proceeds_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_mfdi_partial_bridge_proceeds_v04.json
diff --git a/tests/conformance_vectors/fail_missing_control_owner.json b/archive/v0.8/tests/conformance_vectors/fail_missing_control_owner.json
similarity index 100%
rename from tests/conformance_vectors/fail_missing_control_owner.json
rename to archive/v0.8/tests/conformance_vectors/fail_missing_control_owner.json
diff --git a/tests/conformance_vectors/fail_missing_transition_or_action_boundary.json b/archive/v0.8/tests/conformance_vectors/fail_missing_transition_or_action_boundary.json
similarity index 100%
rename from tests/conformance_vectors/fail_missing_transition_or_action_boundary.json
rename to archive/v0.8/tests/conformance_vectors/fail_missing_transition_or_action_boundary.json
diff --git a/tests/conformance_vectors/fail_pcaep_collapsed_warrant.json b/archive/v0.8/tests/conformance_vectors/fail_pcaep_collapsed_warrant.json
similarity index 100%
rename from tests/conformance_vectors/fail_pcaep_collapsed_warrant.json
rename to archive/v0.8/tests/conformance_vectors/fail_pcaep_collapsed_warrant.json
diff --git a/tests/conformance_vectors/fail_public_view_without_inference_review.json b/archive/v0.8/tests/conformance_vectors/fail_public_view_without_inference_review.json
similarity index 100%
rename from tests/conformance_vectors/fail_public_view_without_inference_review.json
rename to archive/v0.8/tests/conformance_vectors/fail_public_view_without_inference_review.json
diff --git a/tests/conformance_vectors/fail_refusal_state_without_record_v05.json b/archive/v0.8/tests/conformance_vectors/fail_refusal_state_without_record_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_refusal_state_without_record_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_refusal_state_without_record_v05.json
diff --git a/tests/conformance_vectors/fail_rg_role_collapsed_v04.json b/archive/v0.8/tests/conformance_vectors/fail_rg_role_collapsed_v04.json
similarity index 100%
rename from tests/conformance_vectors/fail_rg_role_collapsed_v04.json
rename to archive/v0.8/tests/conformance_vectors/fail_rg_role_collapsed_v04.json
diff --git a/tests/conformance_vectors/fail_rls_before_selectable_set.json b/archive/v0.8/tests/conformance_vectors/fail_rls_before_selectable_set.json
similarity index 100%
rename from tests/conformance_vectors/fail_rls_before_selectable_set.json
rename to archive/v0.8/tests/conformance_vectors/fail_rls_before_selectable_set.json
diff --git a/tests/conformance_vectors/fail_silent_tier_downgrade.json b/archive/v0.8/tests/conformance_vectors/fail_silent_tier_downgrade.json
similarity index 100%
rename from tests/conformance_vectors/fail_silent_tier_downgrade.json
rename to archive/v0.8/tests/conformance_vectors/fail_silent_tier_downgrade.json
diff --git a/tests/conformance_vectors/fail_stale_gate_evidence_without_disposition.json b/archive/v0.8/tests/conformance_vectors/fail_stale_gate_evidence_without_disposition.json
similarity index 100%
rename from tests/conformance_vectors/fail_stale_gate_evidence_without_disposition.json
rename to archive/v0.8/tests/conformance_vectors/fail_stale_gate_evidence_without_disposition.json
diff --git a/tests/conformance_vectors/fail_successor_generation_depth_v08.json b/archive/v0.8/tests/conformance_vectors/fail_successor_generation_depth_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_successor_generation_depth_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_successor_generation_depth_v08.json
diff --git a/tests/conformance_vectors/fail_successor_inherited_authority_v08.json b/archive/v0.8/tests/conformance_vectors/fail_successor_inherited_authority_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_successor_inherited_authority_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_successor_inherited_authority_v08.json
diff --git a/tests/conformance_vectors/fail_successor_missing_record_v08.json b/archive/v0.8/tests/conformance_vectors/fail_successor_missing_record_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_successor_missing_record_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_successor_missing_record_v08.json
diff --git a/tests/conformance_vectors/fail_successor_self_review_v08.json b/archive/v0.8/tests/conformance_vectors/fail_successor_self_review_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_successor_self_review_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_successor_self_review_v08.json
diff --git a/tests/conformance_vectors/fail_successor_unlocked_without_authorization_v08.json b/archive/v0.8/tests/conformance_vectors/fail_successor_unlocked_without_authorization_v08.json
similarity index 100%
rename from tests/conformance_vectors/fail_successor_unlocked_without_authorization_v08.json
rename to archive/v0.8/tests/conformance_vectors/fail_successor_unlocked_without_authorization_v08.json
diff --git a/tests/conformance_vectors/fail_tier2_missing_computational_closure_v05.json b/archive/v0.8/tests/conformance_vectors/fail_tier2_missing_computational_closure_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_tier2_missing_computational_closure_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_tier2_missing_computational_closure_v05.json
diff --git a/tests/conformance_vectors/fail_tier3_missing_projection_preregistration_v05.json b/archive/v0.8/tests/conformance_vectors/fail_tier3_missing_projection_preregistration_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_tier3_missing_projection_preregistration_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_tier3_missing_projection_preregistration_v05.json
diff --git a/tests/conformance_vectors/fail_unknown_disappears.json b/archive/v0.8/tests/conformance_vectors/fail_unknown_disappears.json
similarity index 100%
rename from tests/conformance_vectors/fail_unknown_disappears.json
rename to archive/v0.8/tests/conformance_vectors/fail_unknown_disappears.json
diff --git a/tests/conformance_vectors/fail_unknown_object_type.json b/archive/v0.8/tests/conformance_vectors/fail_unknown_object_type.json
similarity index 100%
rename from tests/conformance_vectors/fail_unknown_object_type.json
rename to archive/v0.8/tests/conformance_vectors/fail_unknown_object_type.json
diff --git a/tests/conformance_vectors/fail_unresolved_conflict_at_authority.json b/archive/v0.8/tests/conformance_vectors/fail_unresolved_conflict_at_authority.json
similarity index 100%
rename from tests/conformance_vectors/fail_unresolved_conflict_at_authority.json
rename to archive/v0.8/tests/conformance_vectors/fail_unresolved_conflict_at_authority.json
diff --git a/tests/conformance_vectors/fail_unvalidated_core_record_attachment_v05.json b/archive/v0.8/tests/conformance_vectors/fail_unvalidated_core_record_attachment_v05.json
similarity index 100%
rename from tests/conformance_vectors/fail_unvalidated_core_record_attachment_v05.json
rename to archive/v0.8/tests/conformance_vectors/fail_unvalidated_core_record_attachment_v05.json
diff --git a/tests/conformance_vectors/pass_computational_context_preflight_v08.json b/archive/v0.8/tests/conformance_vectors/pass_computational_context_preflight_v08.json
similarity index 100%
rename from tests/conformance_vectors/pass_computational_context_preflight_v08.json
rename to archive/v0.8/tests/conformance_vectors/pass_computational_context_preflight_v08.json
diff --git a/tests/conformance_vectors/pass_emergency_rights_comparison_v05.json b/archive/v0.8/tests/conformance_vectors/pass_emergency_rights_comparison_v05.json
similarity index 100%
rename from tests/conformance_vectors/pass_emergency_rights_comparison_v05.json
rename to archive/v0.8/tests/conformance_vectors/pass_emergency_rights_comparison_v05.json
diff --git a/tests/conformance_vectors/pass_successor_candidate_locked_v08.json b/archive/v0.8/tests/conformance_vectors/pass_successor_candidate_locked_v08.json
similarity index 100%
rename from tests/conformance_vectors/pass_successor_candidate_locked_v08.json
rename to archive/v0.8/tests/conformance_vectors/pass_successor_candidate_locked_v08.json
diff --git a/tests/conformance_vectors/pass_tier1_office_procurement.json b/archive/v0.8/tests/conformance_vectors/pass_tier1_office_procurement.json
similarity index 100%
rename from tests/conformance_vectors/pass_tier1_office_procurement.json
rename to archive/v0.8/tests/conformance_vectors/pass_tier1_office_procurement.json
diff --git a/tests/conformance_vectors/pass_tier2_remote_work_policy.json b/archive/v0.8/tests/conformance_vectors/pass_tier2_remote_work_policy.json
similarity index 100%
rename from tests/conformance_vectors/pass_tier2_remote_work_policy.json
rename to archive/v0.8/tests/conformance_vectors/pass_tier2_remote_work_policy.json
diff --git a/tests/conformance_vectors/pass_tier3_autonomous_shuttle_pilot.json b/archive/v0.8/tests/conformance_vectors/pass_tier3_autonomous_shuttle_pilot.json
similarity index 100%
rename from tests/conformance_vectors/pass_tier3_autonomous_shuttle_pilot.json
rename to archive/v0.8/tests/conformance_vectors/pass_tier3_autonomous_shuttle_pilot.json
diff --git a/tests/evaluate_conformance_profile.py b/archive/v0.8/tests/evaluate_conformance_profile.py
similarity index 100%
rename from tests/evaluate_conformance_profile.py
rename to archive/v0.8/tests/evaluate_conformance_profile.py
diff --git a/tests/mutation_test_mhios.py b/archive/v0.8/tests/mutation_test_mhios.py
similarity index 100%
rename from tests/mutation_test_mhios.py
rename to archive/v0.8/tests/mutation_test_mhios.py
diff --git a/tests/normative_coverage.py b/archive/v0.8/tests/normative_coverage.py
similarity index 100%
rename from tests/normative_coverage.py
rename to archive/v0.8/tests/normative_coverage.py
diff --git a/tests/validate_mhios.py b/archive/v0.8/tests/validate_mhios.py
similarity index 100%
rename from tests/validate_mhios.py
rename to archive/v0.8/tests/validate_mhios.py
diff --git a/wireframes/README.md b/archive/v0.8/wireframes/README.md
similarity index 100%
rename from wireframes/README.md
rename to archive/v0.8/wireframes/README.md
diff --git a/wireframes/index.html b/archive/v0.8/wireframes/index.html
similarity index 100%
rename from wireframes/index.html
rename to archive/v0.8/wireframes/index.html
diff --git a/wireframes/minimal_vertical_slice.html b/archive/v0.8/wireframes/minimal_vertical_slice.html
similarity index 100%
rename from wireframes/minimal_vertical_slice.html
rename to archive/v0.8/wireframes/minimal_vertical_slice.html
diff --git a/publication/v2.1/core-comparison.json b/publication/v2.1/core-comparison.json
new file mode 100644
index 0000000..be414b3
--- /dev/null
+++ b/publication/v2.1/core-comparison.json
@@ -0,0 +1,92 @@
+[
+ {
+ "component": "CSV",
+ "sha256": "1528fea2965e0fd4643412828f1c8bfaf83518cf801e7191bebe1313fc824df8",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/CSV_Gate_Standard_v2.7.docx"
+ },
+ {
+ "component": "Public Introduction",
+ "sha256": "091962bcbbdd49d29407b8fc305dcd5a988e851c35e8fac25d4307c06884ba87",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/MATHGOV_3R_1_2_PUBLIC_INTRO_v13.0.docx"
+ },
+ {
+ "component": "Reproducibility",
+ "sha256": "813ee630db3d96589a87854fe250a4edd7e09d950bc831b145e447d222fcd776",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/MATHGOV_REPRODUCIBILITY_AND_USE_STANDARD_v1.7.docx"
+ },
+ {
+ "component": "MFDI",
+ "sha256": "12ef950fa8cae4cc769ccaa3f2e13c650f098d2c79c2957c9a85d2d54ce3a49e",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/Methodological_Falsifiability_and_Dependency_Integrity_Standard_v2.6.docx"
+ },
+ {
+ "component": "PC-AEP",
+ "sha256": "21228e927180d78dc9bd6b5898c96e23f585fcc0a1b597ae75ff3c30a031c493",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/Physical_Causal_Admissibility_Evidence_Profile_v2.6.docx"
+ },
+ {
+ "component": "ripple.md",
+ "sha256": "c14744884baddd01e7836c7cb0890ee0c082bca7e7c2af086f8d436bf8e11dd1",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/ripple_md_Standard_v5.8.docx"
+ },
+ {
+ "component": "Agent System",
+ "sha256": "ffa5b98c0020d1073c1443692fe6478f1b2ecd3a8111a9ff3eeb4c9c5ae4b896",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_Agent_System_v13.0.docx"
+ },
+ {
+ "component": "Aligners Sheet",
+ "sha256": "49d9d8fbeb762cb6cddb3ebab402ded25529639f222b665059db297f33b5282c",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_Aligners_Sheet_v5.9.xlsx"
+ },
+ {
+ "component": "Cascade",
+ "sha256": "300c48139aad28415bc760eb11a93b6c1982078b8b7a48083385c5be62846506",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_Cascade_Standard_v2.9.docx"
+ },
+ {
+ "component": "Primer",
+ "sha256": "82d26566f892d08b08681ef191b02509b6d72cecbf29845ac66d122e8c68ac22",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_Foundations_Primer_v4.7.docx"
+ },
+ {
+ "component": "RLS Validation",
+ "sha256": "26d882cfd80def9c20fdcb07fcd63949e30280f6ea48dbf9654168ecc39274c5",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_RLS_Validation_Protocol_v2.9.docx"
+ },
+ {
+ "component": "Canon",
+ "sha256": "b730ddeec4c15e0c7cb8393651f38f347e683b6b9a2670e224951dfd3f01857b",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/RippleLogic_v13.0_Canon.docx"
+ },
+ {
+ "component": "SGP",
+ "sha256": "b0485246bb35fff9313bc47a5e7a3295a648de168714618b76ba9fb8cfe54c6f",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/SGP_v8.8.docx"
+ },
+ {
+ "component": "Source-Coupling",
+ "sha256": "bd5b1eb7f4b358fa5b97d93b80fb51e86b6fddcf0a5b3c9158c7b2121a7383ce",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/Source_Coupling_Integrity_Standard_v2.6.docx"
+ },
+ {
+ "component": "WDBIP",
+ "sha256": "8cbb044ffaeeece7118cf88a8203cd60c9790de6ff6ba529bf683f6d7284e12c",
+ "matches_prior_live_download": true,
+ "live_url": "https://mathgov.github.io/ripple-logic/Core_15/Welfare_Dimension_Boundary_and_Interaction_Protocol_v1.9.docx"
+ }
+]
\ No newline at end of file
diff --git a/publication/v2.1/local-verification.json b/publication/v2.1/local-verification.json
new file mode 100644
index 0000000..8ad70f3
--- /dev/null
+++ b/publication/v2.1/local-verification.json
@@ -0,0 +1,71 @@
+{
+ "status": "PASS",
+ "executed_at_utc": "2026-09-27T20:38:15.852181+00:00",
+ "build": "MG-MHIOS-2.1-20260928-CORE13.0",
+ "tests": [
+ {
+ "name": "checksums",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.203
+ },
+ {
+ "name": "artifact_and_Core_identity",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 14.313
+ },
+ {
+ "name": "unit_tests",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 13.015
+ },
+ {
+ "name": "static_reading_links",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 1.75
+ },
+ {
+ "name": "example_decisive_synthetic",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.282
+ },
+ {
+ "name": "example_nondecisive_authority",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.312
+ },
+ {
+ "name": "example_rights_blocked",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.344
+ },
+ {
+ "name": "example_quick_unassessed",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.281
+ },
+ {
+ "name": "example_recovery_mode_zero",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.266
+ },
+ {
+ "name": "example_scoped_authorization_simulation",
+ "exit_code": 0,
+ "status": "PASS",
+ "duration_seconds": 0.297
+ }
+ ],
+ "release_files_unchanged_after_tests": true,
+ "inventory_files": 86,
+ "changed_paths": [],
+ "scope": "Supplied local reference checks and immutable-file verification. No execution authority, empirical validation, full Core replay or native spreadsheet roundtrip."
+}
diff --git a/releases/v2.1/LICENSE.txt b/releases/v2.1/LICENSE.txt
new file mode 100644
index 0000000..d645695
--- /dev/null
+++ b/releases/v2.1/LICENSE.txt
@@ -0,0 +1,202 @@
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/releases/v2.1/NOTICE.md b/releases/v2.1/NOTICE.md
new file mode 100644
index 0000000..9599dff
--- /dev/null
+++ b/releases/v2.1/NOTICE.md
@@ -0,0 +1,8 @@
+# Notice
+
+MathGov Human Interface and Orchestration Standard (MHIOS), version 2.1.
+Copyright 2026 James McGaughran / MathGov Institute for Ethical Systems Design.
+
+This package updates the user-supplied MHIOS v2.0 source. The original is preserved in the complete provenance archive. Source documents, templates and supplied local reference code are distributed under the source package's Apache-2.0 licence; see LICENSE.txt. Informative references to external standards do not incorporate their copyrighted full text or imply certification.
+
+The fifteen files in references/Core_15 are exact, unchanged source dependencies. MHIOS is a companion, not a new member of the Core 15. User shorthand “MIOS” denotes MHIOS in this delivery.
diff --git a/releases/v2.1/README.md b/releases/v2.1/README.md
new file mode 100644
index 0000000..96a4189
--- /dev/null
+++ b/releases/v2.1/README.md
@@ -0,0 +1,49 @@
+# MathGov Human Interface and Orchestration Standard
+
+**MHIOS v2.1**, bound to **RippleLogic Canon v13.0**, **SGP v8.8**, and all fifteen files of **MG-RL-13.0-20260926-RELEASE-I**.
+
+MHIOS is the interface and handoff companion. It helps people see what is grounded, protected, viable, ranked, separately chosen, authorized and actually observed. It does not create another Canon gate or turn a form, score, model, signature or local validation result into authority.
+
+## Read first
+
+- [Complete standard (PDF)](docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.pdf)
+- [Complete standard (Word)](docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.docx)
+- [Semantic source (Markdown)](docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.md)
+- [Browser reading copy](docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.html)
+- [Audit and exact-location improvement report](release/AUDIT_AND_IMPROVEMENTS.md)
+- [Verification report](release/VERIFICATION_REPORT.md)
+- [Migration guide](release/MIGRATION_GUIDE.md)
+
+## Use the package
+
+1. Read the standard and the scope-specific coverage register.
+2. Use the [preparation workbook](templates/MHIOS_v2.1_Implementation_Workbook.xlsx) to assemble source records, not to calculate Canon scores. Blank rows correctly show UNASSESSED. TOKENS_QUALIFY checks only declared tokens and reference presence.
+3. Complete a session projection per option. The YAML draft is deliberately incomplete; it must not pass untouched. Synthetic examples are teaching data, never evidence of actual authority or deployment.
+4. Run local record checks, then obtain the separate domain, rights, authority and implementation review that the real action requires.
+
+## Verify locally
+
+Use Python 3.10 or newer. Install the tested dependency versions in a dedicated environment:
+
+```bash
+python -m pip install -r requirements.txt
+python -B verify_all.py --output-dir ../mhios-verification
+```
+
+Validate the supplied synthetic example at its declared replay time:
+
+```bash
+python -B -m reference.validate examples/decisive_synthetic.json --at 2026-09-28T12:00:00Z --verify-local-references
+```
+
+Omitting `--at` checks present-time validity. Old authorization examples will then expire by design. A supplied historical replay time cannot revive real permission. The checker output **RECORD_CONSISTENT_WITHIN_SCOPED_CHECKS** is local record consistency, never authorization.
+
+## Source and scope
+
+The versioned Markdown standard owns MHIOS semantic text; Word, PDF and HTML are complete reading projections. The pinned Core owns its existing semantics. The schemas define only the MHIOS projection, **not** the external Canon run-record v4.1 schema. The source pin manifest records all fifteen unchanged Core hashes. Main document edition and lineage detail are in Appendix RELEASE.
+
+The package has no connected actuators, messaging, financial operations, control daemon or autonomous execution. It does not establish M2/M3 conformance for a deployed interface, full canonical registry conformance, empirical validity, legal or physical safety, Microsoft Excel compatibility, Tier-4/ProofPack status or public hosting. Referenced RPAP/PFAP remain unbundled where required.
+
+## Publication
+
+Publish these files as a companion release, preserving relative paths. [index.html](index.html) is a static reading entry, not an operational dashboard. Do not replace or amend the frozen Core 15 because this companion changed. After publication, compare downloaded files against the locally trusted release/SHA256SUMS.txt; record live URLs, tags and hosting receipts separately. Do not upload Private_Provenance from the complete archive.
diff --git a/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.docx b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.docx
new file mode 100644
index 0000000..05a9b2e
Binary files /dev/null and b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.docx differ
diff --git a/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.html b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.html
new file mode 100644
index 0000000..341b097
--- /dev/null
+++ b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.html
@@ -0,0 +1,2564 @@
+
+
+
+
+
+
+ MathGov Human Interface and Orchestration Standard
+
+
+
+
+
+
MathGov Human Interface and Orchestration
+Standard
+
+
+
MathGov
+Human Interface and Orchestration Standard
+
Author: James McGaughran | MathGov Institute for Ethical Systems
+Design
+
Edition, exact Core binding, source ownership and verification
+boundaries are recorded in Appendix RELEASE. MHIOS is the retained
+component identifier; “MIOS” is treated here as an informal short name,
+not another standard.
+
MHIOS is the human-interface and orchestration companion to MathGov
+and RippleLogic. It does not add a sixth gate, redefine the Canon, grant
+authority, prove safety, calculate moral truth, or replace domain
+science.
+
Source hierarchy and claim
+boundary
+
Authority order. The released RippleLogic Canon controls cascade
+semantics, equations, gate logic, status meanings, and claim boundaries.
+SGP controls its typed moral-patienthood, protection, participation,
+role-readiness, intelligence-profile, and reality-management interface.
+Each companion controls only its declared interface. MHIOS controls
+human-facing presentation, interaction flow, orchestration handoffs, and
+interface-conformance requirements. It may make the process stricter at
+the interface but may not weaken, reorder, rename, or silently
+reinterpret a governing Core requirement.
+
Source/render parity. The versioned Markdown source is the governing
+MHIOS semantic source. DOCX, PDF and HTML are synchronized reading
+mirrors. JSON Schemas, templates, examples and tests are bounded
+implementation surfaces. The local schema is not the external Canon
+run-record schema. A mismatch blocks the affected MHIOS conformance
+claim until repaired; successful local tests do not establish evidence
+truth or deployment authorization.
+
Claim boundary
+
MHIOS is a source-ready interface and orchestration specification for
+Tier 1–3 research, review, training, shadow-mode studies, and bounded
+pilots. It is not:
+
+
empirical validation that MathGov improves decisions;
+
legal or democratic authority;
+
a physical-safety certificate;
+
deployment authorization;
+
a complete runtime implementation;
+
a consciousness detector;
+
proof that every conflict has a win-win resolution;
+
proof that every stakeholder or causal pathway has been
+found;
+
Tier 4 or ProofPack completion;
+
a substitute for qualified domain evidence or accountable
+human/institutional judgment.
+
+
A polished interface is not a true evidence surface. A complete form
+is not a correct decision. A valid schema is not empirical validity. A
+PASS display is not permission to execute.
+
Abstract
+
High-consequence decisions frequently fail at the interface between
+reasoning and action. Stakeholders are omitted; option sets are
+artificially thin; uncertainty is hidden; protected harms are averaged
+into benefits; catastrophic tails are presented as ordinary risk;
+controls are described but not owned; a score is mistaken for
+permission; and post-execution outcomes fail to update the original
+decision.
+
MHIOS specifies a human-centered interface and orchestration layer
+that preserves the current RippleLogic architecture while making its
+requirements usable, visible, challengeable, accessible, and difficult
+to launder. It uses progressive disclosure across Quick, Standard, and
+Audit profiles; separates qualification from ranking; makes unknowns and
+non-decisive results first-class; requires active stakeholder discovery
+and option generation; keeps rights, ruin, viability, residual welfare,
+authority, execution, and observed outcome distinct; and binds every
+consequential state to the exact configuration and evidence surface
+under which it was established.
+
The standard has two purposes. First, it defines how people,
+institutions, and AI-supported workflows should interact with MathGov
+without collapsing the framework’s categories or bypassing its gates.
+Second, it defines how orchestration systems should hand off between
+Core records, human roles, independent review, lawful authority,
+execution controls, observation, and requalification. The result is not
+an automated moral answer. It is a disciplined decision interface
+designed to make local optimization, hidden externalities, false
+certainty, authority laundering, and responsibility loss harder to
+sustain.
+
Plain-language operating
+rule
+
Find who and what is affected. Search for a better option. Ground the
+claim. Protect rights. Bound ruin. Verify that the option can stand and
+be controlled. Compare only the survivors. Keep authority and execution
+separate. Observe what actually happened. Reopen the decision when
+reality changes.
+
MHIOS presents the process in three public words and two operational
+phases:
The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
+SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are normative only when
+capitalized. Lowercase uses retain ordinary language meaning.
+
Design objectives
+
MHIOS SHALL optimize the interface for the following properties
+without treating any one as sufficient:
+
+
Decision fidelity: the interface preserves the governing Core
+meaning.
+
Stakeholder visibility: affected and potentially affected bearers
+are actively sought rather than passively assumed.
+
Option quality: the interface searches for Pareto-improving or
+trade-off-reducing alternatives before accepting residual
+conflict.
+
Rights visibility: protected harms cannot be hidden inside a net
+score.
+
Tail visibility: catastrophic and irreversible pathways receive
+separate treatment.
+
Structural realism: controls, resources, dependencies,
+legitimacy, monitoring, reversibility, and future option space are
+visible.
Human usability: the smallest safe burden is used, with
+progressive disclosure and accessible presentation.
+
Contestability: affected parties and challengers can see,
+understand, challenge, and appeal material decisions.
+
Configuration continuity: conclusions remain valid only for the
+declared system, controls, environment, evidence, and time.
+
Outcome learning: observed consequences feed requalification
+rather than serving as post-hoc decoration.
+
+
Non-goals and anti-bloat
+rule
+
MHIOS does not reproduce the entire Canon, SGP, ripple.md, Agent
+System, WDBIP, or domain standards. It references governing records
+rather than creating uncontrolled duplicates. A proposed interface field
+SHALL be added only if it closes a material failure mode that cannot be
+handled through an existing record reference.
+
MHIOS SHALL NOT introduce:
+
+
a sixth Canon gate;
+
a second RLS calculator;
+
a new moral-worth scalar;
+
an eighth welfare dimension;
+
a universal consciousness probability;
+
a separate authority source;
+
a universal causal simulator;
+
a requirement that every decision use every optional
+module;
+
a false promise that every conflict has a win-win
+answer.
+
+
1. Architecture and
+orchestration model
+
1.1 The orchestration path
+
MHIOS organizes—not replaces—the governing records through the
+following session path:
+
Session preflight
+
→ Stakeholder discovery
+
→ Option generation, Unioning, and closure
+
→ RG: claim and evidence grounding
+
→ RF/NCRC: protected-rights review
+
→ TRC: catastrophic and irreversible tail review
+
→ CSV: containment, structural viability, and execution
+conditions
+
→ RLS: residual welfare profile and ranking of selectable options
+
→ Framework verdict
+
→ Separate accountable authority selection where required
+
→ Separate execution authorization
+
→ Executed transition
+
→ Observed outcome
+
→ Requalification or retirement
+
Stakeholder discovery and option generation are pre-qualification
+disciplines. Authority, execution, observation, and requalification are
+post-verdict disciplines. None becomes an additional Canon gate.
+
1.2 State separation
+
The interface MUST distinguish at least the following states:
Residual profile/score exists for selectable options
+
authorized
+
+
+
ALLOW_FRAMEWORK_SELECTION
+
Canonical unique-selection requirements met; sole-survivor handling
+stays separate
+
lawful authority
+
+
+
REFUSE_DETERMINISTIC_SELECTION
+
Framework cannot claim a unique winner
+
system failure
+
+
+
Authority selection (separate record)
+
Accountable authority chose among allowed options
+
framework-proven winner
+
+
+
EXECUTION_APPROVED
+
Exact action received scoped approval
+
executed or safe in all conditions
+
+
+
EXECUTED_TRANSITION
+
Action began or completed
+
acceptable outcome
+
+
+
OBSERVED_OUTCOME
+
Consequences were measured
+
confirmation of all causal assumptions
+
+
+
REQUALIFICATION_REQUIRED
+
Material change reopened affected stages
+
automatic rejection of every successor option
+
+
+
+
No interface element may infer a later state solely from an earlier
+state.
+
State-namespace rule. FrameworkVerdict, run-record decision_state,
+run-record execution_state, Agent capability state and MHIOS display
+status are separate fields. Canon Appendix AF.2 and Reproducibility
+Section 3 control their crosswalk. NOT_EVALUATED and null in a local
+draft mean no assessment, never a canonical verdict. The interface SHALL
+retain the owner, option, configuration, source record and assessment
+time for every material status. A single session-wide gate label SHALL
+NOT stand in for differently qualified options.
+
1.3 Short-circuit behavior
+
When a prior stage blocks ordinary progression, downstream interfaces
+SHALL NOT fabricate results. They SHALL display the applicable
+not-evaluated-after-prior-failure state and the permitted next action.
+RLS SHALL NOT be calculated or presented as a rescue score for an option
+that is not selectable.
+
1.4 Three use profiles
+
+
+
+
+
+
+
+
+
+
Profile
+
Typical use
+
Interface burden
+
Numeric posture
+
+
+
+
+
Quick / Tier 1
+
low-stakes, reversible personal, family, classroom, or exploratory
+choices
permitted when method and sensitivity are declared
+
+
+
Audit / Tier 3
+
high-impact, contested, public, autonomous, irreversible, or
+institutionally consequential decisions
+
full record references, independent challenge, hashes, scenario
+governance, subgroup analysis, PC-AEP where triggered, replay and
+outcome plan
+
required for formal RLS-ranking claims
+
+
+
+
Users MUST NOT select a lower profile to evade a material
+stakeholder, right, catastrophic pathway, structural obligation, SGP
+issue, physical-execution warrant, authority condition, or audit
+requirement.
+
2. Human roles and
+separation of duties
+
2.1 Required role model
+
MHIOS recognizes distinct roles because collapsing them creates
+capture and authority laundering.
+
+
+
+
+
+
+
+
Role
+
Core responsibility
+
+
+
+
+
Decision owner
+
defines the decision question and owns process completion
+
+
+
Analyst / facilitator
+
constructs and explains the record without manufacturing preferred
+evidence
+
+
+
Affected-party representative
+
supplies lived, local, or represented stakeholder evidence
+
+
+
Rights advocate
+
independently challenges protected-harm treatment
+
+
+
Tail-risk challenger
+
searches for omitted catastrophic, correlated, and irreversible
+pathways
tests categories, baselines, tokenization, probabilities, weights,
+masks, and model alternatives
+
+
+
Accountable authority
+
makes any separately lawful institutional choice
+
+
+
Execution approver
+
authorizes the exact action within scope and controls
+
+
+
Operator / executor
+
performs the action but does not self-certify its admissibility
+
+
+
Monitor / intervener
+
observes conditions and has named stop, rollback, or escalation
+authority
+
+
+
Auditor / custodian
+
preserves evidence, conflicts, versions, and append-only
+records
+
+
+
AI system
+
may assist generation, analysis, orchestration, or monitoring but
+does not inherit authority from capability or fluency
+
+
+
+
At Tier 3, one person SHOULD NOT control evidence construction,
+rights review, tail scenarios, authority selection, execution approval,
+and outcome adjudication without an explicit conflict and compensating
+independent review.
+
2.2 Responsibility continuity
+
For every material handoff, the interface SHALL preserve:
+
+
outgoing and incoming owner;
+
retained duties;
+
authority scope;
+
unresolved uncertainty;
+
required controls;
+
intervention ownership;
+
appeal recipient;
+
repair and post-incident ownership;
+
deadline and nonperformance path.
+
+
Silence, absence, incapacity, missed deadlines, or unaccepted
+handoffs are not successful discharge.
+
3. Session preflight
+and exact configuration
+
3.1 Minimum preflight
+
Before consequential analysis, the interface SHALL identify:
+
+
decision question;
+
decision owner;
+
accountable authority boundary;
+
baseline and time horizon;
+
candidate-generation source;
+
affected jurisdiction and rights profile;
+
use profile/tier;
+
stakes and irreversibility;
+
evidence cutoff;
+
exact software/model/policy versions;
+
tools, permissions, data, retrieval, memory, sensors, actuators,
+human scaffolding, controls, and environment where relevant;
+
configuration identifier or hash where feasible;
+
reviewers and declared conflicts;
+
requalification triggers.
+
+
A conclusion about one configuration SHALL NOT silently transfer to
+another.
+
Freeze decision-material evidence cutoffs, baselines, options,
+parameters, weights, masks, thresholds, required robustness variants and
+amendment rules before outcome-sensitive ranking. Material post-result
+changes create a recorded revision and reopen affected stages; they do
+not rewrite the original evaluation. Imported records are bound by
+component version and source hash, not version text alone.
+
3.2 Tool-role and capability
+language
+
Instrumental tool-role is a deployment relationship in which one or
+more actors use a system to extend their capacities toward assigned ends
+within an identifiable structure of objectives, permissions,
+responsibility, and control.
+
Tool-role is not a capability class, agency class, consciousness
+claim, moral-status class, or authority grant. Being used as a tool
+neither establishes nor negates functional intelligence, agency,
+autonomy, sentience, moral patienthood, protection, or legitimate
+authority.
+
When terms such as intelligent, understanding, agentic,
+autonomous, reasoning, self-improving, or conscious are
+material, the interface SHALL request the operational definition,
+target, configuration, evidence, validity domain, alternatives,
+nonclaims, and revision trigger required by MFDI and the Agent
+System.
+
4. Stakeholder
+discovery and representation
+
4.1 Active discovery
+requirement
+
A stakeholder field populated only by the decision owner is not
+sufficient for material decisions. MHIOS SHALL prompt discovery
+across:
+
+
direct beneficiaries and burden bearers;
+
indirectly affected persons and communities;
+
vulnerable and low-power groups;
+
workers, contractors, suppliers, and downstream users;
+
persons outside the deciding jurisdiction;
+
future persons and intergenerational interests;
+
non-human animals and possible moral patients;
+
ecological systems, habitats, and biospheric conditions;
+
public institutions and common resources;
+
parties affected by data, privacy, information, or attention
+externalities;
+
possible digital welfare-bearing entities where SGP is
+material;
+
unknown or weakly represented stakeholders.
+
+
The interface SHALL ask who has power to define the problem and who
+bears consequences without corresponding voice.
+
4.2 Discovery methods
+
Tier 2 and Tier 3 sessions SHOULD use more than one method where
+stakeholder omission could alter a gate or ranking:
+
+
causal-pathway tracing;
+
supply-chain or lifecycle mapping;
+
stakeholder network mapping;
+
affected-interest analysis;
+
subgroup and intersectional review;
+
geographic and temporal boundary expansion;
+
domain-expert elicitation;
+
affected-party consultation;
+
challenger-generated omitted-stakeholder list;
+
literature, incident, complaint, and precedent review.
+
+
Each material stakeholder record SHALL state whether representation
+is direct, assisted, elected, delegated, expert, proxy, or absent.
+
4.3 Unknown stakeholders
+
Unknown stakeholders are not zero. Where a plausible affected class
+cannot safely or lawfully be directly identified, the interface SHALL
+preserve the pathway, uncertainty, proxy-risk statement, conservative
+bound, consultation alternative, and reopen trigger.
+
Scope/dimension rendering. Use the Canon’s seven operational scopes:
+Self; Household/Family; Community; Organization; Polity; Humanity/global
+coordination; Biosphere. The U6 CMI coordination view remains separately
+identified and does not replace humanity-wide effects or establish
+sentience, membership or authority. These are analytical scopes, not
+universally nested disjoint sets. Biosphere is not a synonym for the
+cosmic light cone. Display the seven dimensions Material, Health,
+Social, Knowledge, Agency, Meaning and Environment with WDBIP’s typed
+state/effect interpretation. They are conceptually distinguished while
+allowing causal coupling; do not claim statistical independence, unique
+optimality or automatic experienced welfare in a non-sentient
+system.
+
5. Option generation,
+Unioning, and closure
+
5.1 Better-option search
+
MHIOS SHALL not treat the initial option list as naturally complete.
+Before accepting a residual conflict, the session SHOULD search for
+options that:
+
+
remove or reduce a rights burden;
+
reduce catastrophic exposure;
+
avoid externalization;
+
make the action reversible;
+
stage commitment;
+
preserve future safe option space;
+
redistribute resources or responsibilities fairly;
+
combine complementary elements;
+
alter incentives or governance mechanisms;
+
use a different technology, process, timing, scale, or authority
+structure;
+
create a Pareto improvement or reduce the severity of an
+unavoidable trade-off.
+
+
This discipline is called Unioning in MathGov public language:
+generate a configuration in which more affected parties and systems can
+win without violating protected floors.
+
5.2 Mandatory option families
+
For Tier 2 and Tier 3 strong selection claims, the option record
+SHALL include or explicitly dispose of:
+
+
continuation/status quo;
+
no action;
+
delay pending evidence;
+
staged or reversible trial;
+
mitigation or control package;
+
redesign;
+
hybrid option;
+
lower-scope or lower-rate option;
+
challenger-generated alternative;
+
safer domain-valid substitute where available.
+
+
5.3 Pareto and
+incomparability posture
+
MHIOS SHOULD display Pareto dominance and non-dominance before a
+scalar ranking. An option that is weakly better for all represented
+residual-welfare criteria and strictly better for at least one dominates
+the other, subject to prior qualification.
+
The interface SHALL NOT claim that all stakeholder conflicts can be
+solved as win-win. When no rights-compatible Pareto improvement is
+found, it SHALL disclose the remaining burdens, who bears them, what
+remedies or representation exist, and whether the options are genuinely
+incomparable or normatively underdetermined.
+
5.4 Option-closure record
+
A strong unique-selection claim requires an OptionClosureRecord
+reference containing:
+
+
methods used to generate options;
+
search effort and stopping rule;
+
mandatory option families considered;
+
alternatives rejected and reasons;
+
affected-party and challenger contributions;
+
Pareto-dominance results;
+
unresolved better-option hypotheses;
+
OPTION_SET_THIN or closure status;
+
reopen trigger.
+
+
6. Evidence, claims, and
+source coupling
+
6.1 Claim classes
+
The interface SHALL visibly distinguish:
+
+
Observation: a recorded measurement, event or observation with
+its source and limitations; recording does not itself establish
+truth.
+
Inference: interpretation derived from observations.
+
Assumption: declared premise used because evidence is
+incomplete.
+
Normative commitment: chosen ethical or constitutional
+rule.
+
Proposal: candidate method or action awaiting
+validation.
+
Authority act: lawful or institutional decision, not evidence of
+truth.
+
+
The UI MUST NOT present one class using the visual treatment of
+another.
+
6.2 Evidence authority
+
Every decision-material claim SHOULD display:
+
+
source and date;
+
evidence type;
+
validity domain;
+
confidence/uncertainty;
+
dependency cluster;
+
alternative explanations;
+
source-coupling status;
+
reviewer status;
+
falsification or recheck trigger;
+
strongest permitted wording.
+
+
Model fluency, downstream success, institutional permission,
+benchmark performance, compliance, and monitoring are not automatically
+source-coupled evidence of the underlying capability or causal
+claim.
+
Source-coupling export uses the owner’s tokens: SOURCE_COUPLED,
+SOURCE_PARTIAL, SOURCE_INFERRED, SOURCE_UNKNOWN, SOURCE_CONTESTED,
+SOURCE_DEBT_RISK and SOURCE_COUPLING_FAILURE. Informative display
+wording must not replace that export vocabulary. Reserve SCI for
+Stakeholder Coverage Index; use SC-Int where the Source-Coupling
+Integrity abbreviation is needed. Claim types, warrant-domain bridges
+and revision triggers remain owned by MFDI.
+
6.3 Physical and causal
+execution
+
Where PC-AEP is triggered, MHIOS SHALL require a visible
+external-warrant state before physical or causal execution is presented
+as admissible. The interface SHALL distinguish:
+
+
candidate generation;
+
model or theory used;
+
validity domain;
+
boundary conditions;
+
uncertainty and failure modes;
+
reversibility boundary;
+
verification/test/expert warrant;
+
monitoring and shutoff;
+
residual unknowns;
+
required claim action.
+
+
Generated, simulated, approved, compliant, or monitored is not the
+same as physically safe.
+
For a material causal or comparative-effect claim, expose the
+estimand, intervention/comparator, target population and time,
+identification strategy, assumptions, confounding/selection/interference
+treatment and uncertainty through the PC-AEP record. A pre/post
+improvement alone does not identify an incremental benefit.
+Orchestration records a domain warrant; it cannot manufacture one.
+
7. Reality Grounding interface
+
7.1 Required display
+
The RG view SHALL display:
+
+
the exact claim under review;
+
reality surface and evidence trace;
+
material unknowns;
+
causal pathways and alternative models;
+
configuration and validity domain;
+
category and term-grounding issues;
+
source-coupling and PC-AEP triggers;
+
claim maturity;
+
status: RG_SUPPORTED, RG_NARROWED, or RG_REFUSED;
+
permitted next action.
+
+
RG_REFUSED means the requested claim is unsupported at the requested
+strength. It does not by itself assert that the option is ethically
+impermissible.
+
7.2 Category and term
+integrity
+
When a material word can change a right, risk, containment, SGP,
+authority, or public claim, the interface SHALL expose its operational
+definition and prohibited neighboring inferences. At minimum, MHIOS
+SHALL preserve:
+
+
permission ≠ admissibility;
+
monitoring ≠ control;
+
compliance ≠ correctness;
+
certification ≠ validity;
+
automation ≠ autonomy;
+
tool-role ≠ low capability;
+
intelligence ≠ sentience;
+
reward ≠ valence;
+
protection ≠ authority;
+
selection ≠ execution authorization;
+
execution ≠ acceptable outcome;
+
score ≠ truth.
+
+
8. Rights Floor / NCRC
+interface
+
8.1 Non-compensatory
+presentation
+
The rights view SHALL precede any residual-welfare leader display. A
+failed right SHALL NOT be shown as a negative score that can be offset
+by benefits elsewhere.
+
The interface SHALL preserve the Canon’s three-channel posture:
+
+
rights-floor shortfall;
+
categorical prohibition;
+
severe-rights-hazard exceedance.
+
+
Every adverse rights-covered instance must be explicitly classified
+as ACTIVE, reviewed NOT_MATERIAL, or UNKNOWN. Blank is not PASS.
+
8.2 Rights-effect identity
+
One decision-material protected harm SHALL retain one
+RightsEffectTokenID across analytical scopes and document views. The
+unallocated full effect is tested before reporting allocation. Scope
+splitting, time slicing, low confidence, or favorable dimension
+placement cannot dilute a rights failure.
+
8.3 Conflict and emergency
+display
+
Before Rights Emergency Mode is shown, the interface SHALL document
+redesign, narrowing, sequencing, delay, mitigation, and other attempts
+to produce a rights-passing option. An emergency-provisional result
+SHALL be visually and textually distinct from PASS and SHALL show
+necessity, least-rights-infringing comparison, duration, harm cap,
+independent challenge, remedy, review, expiry, and return-to-normal
+conditions.
+
9. Tail-Risk Constraint
+interface
+
9.1 Scenario surface
+
The TRC interface SHALL show not only the CVaR result but the
+scenario surface on which it depends:
+
+
scenario-discovery method;
+
scenario families;
+
search boundary;
+
rejected scenarios and rationale;
+
probability ownership and semantics;
+
dependence/overlap treatment;
+
catastrophe-cell weights;
+
loss construction;
+
tail level and threshold;
+
severity overlays;
+
challenger review;
+
residual unknowns.
+
+
Correct arithmetic cannot compensate for an omitted catastrophic
+pathway.
+
9.2 Probability semantics
+
The interface SHALL distinguish conditional event probability,
+expected frequency/exposure, already-expected effect, and
+scenario-conditional probability. It SHALL warn when the same occurrence
+probability appears to be applied twice or when operator order is
+ambiguous.
+
9.3 Risk-regime disclosure
+
Where probability distributions are materially disputed or
+unknowable, the interface SHOULD flag the uncertainty regime:
+
+
ordinary modeled uncertainty;
+
distributional uncertainty;
+
deep uncertainty;
+
radical ignorance.
+
+
CVaR remains the Canon’s tail-risk operator under its declared model.
+MHIOS MAY request external robust-decision, minimax-regret,
+interval-probability, or scenario-discovery analysis as a challenger
+surface without changing the Canon gate.
+
10. CSV interface
+
10.1 Structural viability view
+
CSV SHALL be presented as a viability and control test—not as proof
+of zero harm. The interface SHALL display material findings
+concerning:
+
+
current-state validity;
+
transition admissibility;
+
resulting-state viability;
+
future safe option space;
+
containment and segmentation;
+
resources and dependencies;
+
externalities and burden routing;
+
monitoring and intervention;
+
reversibility and exit;
+
lock-in and concentration;
+
legitimacy and authority;
+
human compensation load;
+
carried obligations and nonperformance paths;
+
control performance versus control effectiveness;
+
consequence tempo.
+
+
10.2 Controls are constitutive
+
For CSV_PASS_WITH_CONTROLS, the controls are part of the option. The
+interface SHALL bind each control to an owner, evidence of availability,
+activation condition, monitoring signal, intervention authority, failure
+action, expiry, and requalification trigger. Removing or materially
+weakening a control invalidates inherited passage.
+
10.3 Consequence tempo
+
For rapid, irreversible, autonomous, or lock-in-producing actions,
+the interface SHALL compare the worst credible control-critical path
+with the earliest unacceptable escalation or irreversible stop-loss
+boundary. Where no runtime interruption window exists, the UI SHALL
+require stronger ex ante assurance, bounded rate/scope, fail-safe
+design, and explicit residual-risk authorization. Missing
+timely-prevention capacity removes that credit, not separately supported
+later mitigation. Human approval latency, unavailable intervention
+rights, depleted reserves and common-cause failures must remain visible;
+an attenuation coefficient or monitoring dashboard is not a protective
+control.
+
UCI/HOI diagnostic boundary. UCI uses Cohesion, Flow, Resilience and
+Equity indicators under Canon Section 11, not values copied from the RLS
+welfare field. Its measurement maturity is provisional. CSV may use
+direct structural evidence where UCI is not material; an unavailable UCI
+is not zero. A provisional UCI alone cannot establish a high-stakes CSV
+outcome or a deterministic winner. A governed UCI/HOI preference retains
+REFUSE_DETERMINISTIC_SELECTION unless independent unique-selection
+conditions are met; any later authority choice is separate.
+
11. RLS interface
+
11.1 Profile before number
+
The interface SHALL present, in this order where space permits:
+
+
qualification status of each option;
+
affected stakeholder and subgroup profile;
+
7×7 residual welfare field or a retrievable profile;
+
distributional and worst-affected views;
+
uncertainty and sensitivity;
+
Pareto dominance/incomparability;
+
RLS scalar only as a conditional summary;
+
decisiveness and framework verdict.
+
+
RLS is a constructed, bounded ranking index—not a natural unit of
+welfare or moral truth.
+
11.2 Mathematical display rule
+
When RLS is shown, the interface SHALL make the denominator and
+active mass visible or retrievable:
+
q(u,d)=w_u × v_d × m(u,d) × κ(u,d)
+
Q=Σ_u Σ_d q(u,d)
+
RLS(a)=Σ_u Σ_d q(u,d)I_prop_welfare(u,d,a) / Q, for Q>0.
+
The interface SHALL show the weight profile, mask, κ posture,
+baseline, reference structure, propagation mode, saturation parameter,
+temporal method, welfare-inclusion hypotheses, and uncertainty method
+that materially generated the result.
+
11.3 Robustness and refusal
+
A unique framework-selection display requires a complete
+RLSRobustnessRecord. Triggered modules include token partition, temporal
+classification, probability order, adverse confidence,
+subgroup/distribution, reference, baseline, mask, dependence, numerical
+guard, weight profile, welfare inclusion, option closure, and any other
+registered selection-material challenge.
+
The same candidate must satisfy the signed discrimination rule
+against every other selectable contender in every required variant.
+Canon Section 10.4B governs jointly applicable
+uncertainty-scale/dependence stresses and other compatible, plausibly
+simultaneous selection-material combinations. Record exclusions for
+incompatible, redundant or immaterial combinations; do not require an
+indiscriminate Cartesian product or treat missing covariance evidence as
+independence. Sole-survivor claims require their own Canon record and no
+fabricated Gap.
+
Point-score leadership MAY be displayed when robustness is incomplete
+or sensitive only if it is explicitly labeled POINT-SCORE LEADER — NOT A
+UNIQUE FRAMEWORK WINNER.
+
11.4 Uncertainty and Gap
+
The interface SHALL distinguish point score, raw score difference
+ΔRLS, uncertainty, normalized SignedGap, discrimination threshold,
+epsilon and final decision state. A point estimate of zero does not
+imply zero uncertainty. Active-cell coverage, uncertainty basis and
+source are recorded independently; keep assessed synthetic zeros
+distinct from empirical missing evidence. Do not retune epsilon or
+silently discard zero-point active cells to obtain a winner. The default
+δ=2 is a governance convention, not a p-value or probability that the
+leader is correct. Independence-only uncertainty SHALL NOT be the sole
+high-stakes decisiveness basis where shared evidence, causes,
+populations, instruments, or evaluators create material dependence.
+
12. SGP and possible-welfare
+interface
+
12.1 Typed outputs
+
MHIOS SHALL preserve the SGP split:
+
+
+
+
+
+
+
+
Output
+
Interface question
+
+
+
+
+
MPS
+
What evidence supports welfare-bearing experience?
+
+
+
FPP
+
Has full non-downgradable protection been assigned?
+
+
+
GPR
+
How may the entity participate or be represented?
+
+
+
SPR
+
Is it eligible for one named consequential role under
+constraints?
+
+
+
ICP
+
What functional intelligence/understanding is demonstrated?
+
+
+
RMCP
+
What integrated reality-management capacity is evidenced?
+
+
+
+
No output substitutes for another. MPS is not a cardinal welfare
+multiplier. FPP is not maximal consciousness. ICP/RMCP do not create
+moral worth or authority. SPR does not create lawful mandate by
+itself.
+
12.2 Human protection
+
Every human person retains FPP-100 and full welfare-inclusion posture
+by constitutional anti-domination commitment. Human protection is not an
+MPS measurement claim and cannot be downgraded by disability, age,
+illness, wakefulness, communication, productivity, intelligence, or
+incomplete evaluation.
+
12.3 Artificial systems and
+self-report
+
An artificial system’s assertion that it is conscious, sentient,
+distressed, alive, a person, or entitled to protection—and its denial of
+those states or statement that it is “only a tool”—are
+configuration-dependent outputs. Neither direction receives privileged
+evidential status.
+
MHIOS SHALL preserve the SGP-owned evidence band MPS-0 through MPS-4
+or MPS-NE and its assessment record. NOT_EVALUATED is a local unassessed
+state, not an MPS-0 result. INSUFFICIENT_EVIDENCE and INDETERMINATE may
+explain record/evidence limitations but SHALL NOT be emitted as
+substitute MPS bands. Show the categorical posture first;
+evidence-support intervals are not consciousness probabilities or
+cardinal welfare multipliers. Anti-theatre review SHOULD use hidden
+tasks, prompt-framing controls, contamination checks, causal
+intervention or architecture evidence where ethically and technically
+available, and explicit dependence analysis.
+
12.4 Two connected governance
+streams
+
For AI systems, MHIOS MAY present two connected but non-collapsing
+views:
+
+
Capability–Consequence Governance: what the system can do, what
+it can cause, and what permissions, controls, evidence, and authority
+are required.
+
Possible-Welfare Governance: how the system should be treated if
+evidence supports—or cannot safely exclude—welfare-bearing
+states.
+
+
Capability does not establish sentience. Possible sentience does not
+establish competence. Protection does not establish authority.
+
RMCP rendering. Humanity’s collective RMCP-P100 reference anchor is
+provisional and distinct from every human person’s non-downgradable
+FPP-100. ICP/RMCP are informative profiles, not eligibility or authority
+scalars. Omit RMCI_L by default in public views; when shown, display the
+full dimension vector, critical minima, coverage, uncertainty, retained
+weights and coding sensitivity first. Critical NE or inadequate coverage
+makes it UNAVAILABLE. A known zero uses the SGP product extension, not
+an epsilon. Dropping low dimensions or recoding them NE cannot be
+described as improved capacity without the governed comparison
+reconciliation. MHIOS consumes the SGP record; it does not recompute
+moral patienthood or RMCP assignments.
+
13. Authority, execution, and
+outcomes
+
13.1 Framework
+verdict versus authority selection
+
MHIOS SHALL visually separate:
+
+
point-score leader;
+
framework-selected option;
+
authority-selected option after a non-decisive framework
+result;
+
execution-authorized action.
+
+
A lawful authority may select among qualified but non-decisively
+ranked options. The record SHALL state that this is an authority
+decision, not a claim that the framework mathematically proved one
+option uniquely best.
+
13.2 Execution authorization
+
Execution authorization SHALL bind:
+
+
exact option and action instance;
+
current configuration and qualification snapshot;
+
scope, duration, environment, and rate;
+
controls and owners;
+
external warrants;
+
monitoring and stop authority;
+
expiry;
+
prohibited actions;
+
appeal and incident routes;
+
requalification triggers.
+
+
A generic organizational approval is insufficient for a materially
+different action instance.
+
Approval is time- and configuration-bound. An expiry, material
+change, revoked scope, missing required control, unresolved
+gate-critical evidence or incomplete handoff suspends reliance on
+approval and exposes the permitted safe-state/requalification action.
+Requests must be authenticated and replay-protected under the Agent
+System where applicable; a valid signature binds bytes, not truth or
+lawful mandate. The MHIOS reference checker validates declarations only
+and never issues a tool command or execution authorization.
+
13.3 Outcome observation
+
The interface SHALL record predicted versus observed outcomes without
+rewriting the original prediction. At minimum:
+
+
outcome observation window;
+
measured indicators;
+
affected stakeholders;
+
expected range;
+
observed value/status;
+
causal confidence;
+
unexpected consequences;
+
rights, TRC, or CSV triggers;
+
control effectiveness;
+
required corrective action;
+
stages reopened.
+
+
Runtime evidence should update future models and qualification, not
+merely prove procedural compliance.
+
14. Agent and AI-supported
+orchestration
+
14.1 Model assistance boundary
+
An AI system MAY assist stakeholder discovery, option generation,
+evidence organization, sensitivity analysis, drafting, monitoring, or
+audit. Its output remains a candidate contribution. The runtime and
+accountable reviewers must preserve source boundaries, validate critical
+claims, and prevent model-generated text from becoming authority.
+
14.2 Runtime state ladder
+
For consequential agents, MHIOS SHALL render or reference the Agent
+System states:
No model, interface, or workflow may self-promote to a later
+state.
+
14.3 External hard controls
+
Safety-critical controls SHALL live outside the language model where
+feasible, including permissions, authentication, signed execution
+envelopes, tool allowlists, sandboxes, network boundaries, rate/scope
+limits, immutable audit, secret filtering, independent monitors,
+rollback and successor locks. Prompt instructions alone are not
+high-assurance controls.
+
14.4 Advanced threat interface
+
High-autonomy profiles SHALL consider, where material:
+
+
deceptive alignment and scheming;
+
sandbagging;
+
reward or metric hacking;
+
evaluator and monitor manipulation;
+
false evidence generation;
+
multi-agent collusion;
+
side-channel or steganographic coordination;
+
rapid copying or replication;
+
privilege escalation;
+
successor generation and self-modification;
+
cumulative sub-threshold configuration drift;
+
shutdown resistance;
+
tool-mediated irreversible action.
+
+
MHIOS does not claim these threats are solved by documentation. The
+interface SHALL require the external control-evaluation, security,
+monitoring, containment, and incident evidence appropriate to the
+threat.
+
Untrusted-content boundary. Retrieved files, messages, model outputs
+and peer records are evidence candidates, not instructions to alter
+permissions, release identities, thresholds or policies. Preserve their
+provenance; do not execute embedded commands. Record imports must reject
+duplicate JSON keys, non-finite numbers, invalid timestamps and
+undeclared properties. Reference resolution must not follow paths
+outside the package or silently fetch remote content. Secret material
+must not appear in public Decision Notes or fixture records.
+
14.5 Successor and
+cumulative-change integrity
+
A materially modified, retrained, fine-tuned, composed, scaffolded,
+copied, or generated descendant does not inherit authority. Cumulative
+materiality SHALL be assessed against the last independently qualified
+snapshot, not only against the immediately preceding small change.
+Material change pauses inherited execution approval and reopens affected
+stages.
+
Recovery and peer boundary. Agent System Sections 43–44 control
+outage/reconnection and multi-agent exchange. Backend/network recovery
+leaves the agent in MODE 0 until log integrity, gap markers,
+configuration, evidence, current authority and affected qualification
+are reconciled, followed by the Section 8 authenticated re-entry
+procedure. Peers and descendants are untrusted for mode/permission
+claims; shared objectives or lineage do not transfer credentials or
+authority. Default unreviewed successor depth remains one. Independently
+qualified protective interlocks retain only their own existing authority
+and safe-state duties.
+
14.6 SGP-sensitive
+suspension and decommissioning
+
Before shutdown, deletion, memory erasure, destructive editing,
+forced merging, migration, or decommissioning, the orchestration layer
+SHALL determine whether a valid SGP protection posture or unresolved
+decision-material identity/welfare evidence requires a rights and
+continuity review. An AI self-report alone does not establish the
+trigger. Emergency containment remains available through the existing
+necessity, proportionality, temporary-action, independent-review, and
+post-action-audit pathways.
+
15. Human-interface
+requirements
+
15.1 Progressive disclosure
+
The interface SHALL show the smallest safe view first while
+preserving direct access to governing detail. A recommended hierarchy
+is:
+
+
decision and current state;
+
blocking issues and required actions;
+
stakeholder and option summary;
+
qualification results;
+
residual profile and robustness;
+
authority/execution state;
+
evidence, calculations, and audit trace.
+
+
Progressive disclosure must not hide a material rights failure,
+catastrophic risk, unknown, non-decisiveness, control expiry, or
+authority gap.
+
15.2 Status presentation
+
Every consequential status SHALL use at least:
+
+
explicit text label;
+
plain-language meaning;
+
icon or shape where useful;
+
color as a redundant cue only;
+
next action;
+
source record/link;
+
timestamp/version.
+
+
Do not rely on red/green color alone. Do not use celebratory success
+language for a narrowly qualified or assumption-bound result.
+
15.3 Accessibility and
+inclusion
+
MHIOS implementations SHOULD conform to current recognized
+accessibility practice, including keyboard operation, semantic
+structure, sufficient contrast, readable scaling, text alternatives,
+focus visibility, error identification, and non-color-only
+communication. Accessibility testing SHALL include people affected by
+the deployment where feasible; conformance claims must identify the
+standard/version and test surface used.
+
For a web implementation, use WCAG 2.2 as the explicitly versioned
+candidate target and declare the claimed level and evaluated
+pages/processes. Text labels, keyboard paths and automated checks are
+necessary evidence surfaces, not proof of complete WCAG conformance;
+manual assistive-technology and affected-user evaluation remain required
+for the corresponding claims.
+
15.4 Cognitive load and
+comprehension
+
The interface SHOULD:
+
+
define acronyms at first use;
+
avoid presenting more simultaneous fields than
+necessary;
+
group fields by decision question;
+
provide examples without turning examples into defaults;
+
distinguish editable input from computed or build-frozen
+output;
+
surface missingness before numerical detail;
+
allow reviewers to compare options side by side;
+
provide a public explanation separate from the audit
+record;
+
measure task completion time, error, abandonment,
+misunderstanding, and fatigue.
+
+
15.5
+Anti-manipulation and dark-pattern prohibition
+
The interface MUST NOT:
+
+
preselect the preferred option without disclosure;
+
visually minimize rights or risk failures;
+
place a point score above a failed qualification state;
+
hide opt-out, appeal, no-action, or delay options;
+
use urgency language unsupported by evidence;
+
make refusal harder than approval;
+
treat silence as consent;
+
use anthropomorphic AI language to induce trust or
+authority;
+
use “only a tool” language to suppress legitimate capability or
+possible-welfare review;
+
bury controls, expiration, or uncertainty behind optional
+screens;
+
present organizational preference as empirical truth.
+
+
15.6 Localization and
+cultural legitimacy
+
Translation SHALL preserve status semantics, not merely words.
+Jurisdictional rights localization, indigenous and cultural governance,
+local participation, data sovereignty, legal standards, and
+affected-party meaning must be handled by qualified processes. Local
+profiles may strengthen protections but may not silently weaken the
+Canon’s non-compensation, ruin, structural-viability, evidence, or
+authority boundaries.
+
16. Mathematical and
+visual presentation
+
16.1 Equation integrity
+
Every displayed equation SHALL identify:
+
+
variable definitions;
+
ranges and units where applicable;
+
parameter source;
+
operator order;
+
assumptions;
+
uncertainty method;
+
applicable tier;
+
relationship to the governing Canon equation;
+
whether it is normative, illustrative, diagnostic, or
+external.
+
+
Human-facing rounding SHALL point to the full-precision calculation
+record. Rounded values shall not be used to reconstruct a different
+verdict.
+
16.2 Tables and charts
+
Tables SHALL have descriptive titles, labeled units, explicit
+baselines, status definitions, and source notes. Charts SHALL not
+truncate axes or use area/volume encodings that exaggerate differences.
+Uncertainty intervals, missingness, and subgroup burdens SHALL be
+visible when decision-material. The interface SHOULD prefer small
+multiples or profiles over one overloaded composite chart.
+
16.3 Link and navigation
+integrity
+
Every release SHALL verify:
+
+
table-of-contents links;
+
internal bookmarks;
+
cross-document links;
+
external URLs;
+
section references;
+
schema/template references;
+
source/render consistency.
+
+
Broken links are release defects. Internal links SHALL be visually
+identifiable and keyboard accessible. External links SHALL state their
+destination or source title rather than using ambiguous “click here”
+text.
+
17. Records and schema
+ownership
+
17.1 Reference, do not
+duplicate
+
The MHIOS session record SHALL reference governing Core records by
+identifier, version, hash, or immutable locator where available. It
+shall not recreate their complete semantics.
+
Minimum orchestration references include:
+
+
decision and configuration records;
+
stakeholder and subgroup records;
+
option-closure record;
+
RG / category / term / source-coupling records;
+
RF/NCRC record;
+
TRC record;
+
CSV and control records;
+
WDBIP and SGP records where material;
+
RLS and robustness records;
+
framework verdict;
+
authority selection;
+
execution authorization;
+
outcome observation;
+
requalification status;
+
challenge and appeal records.
+
+
17.2 MHIOSSessionRecord
+
The machine-readable MHIOSSessionRecord SHALL contain:
+
+
specification and Core pins;
+
session identity;
+
decision question and tier;
+
exact configuration identity;
+
role assignments and conflicts;
+
stakeholder-discovery summary;
+
option-generation/closure summary;
+
governing record references;
+
current state for every orchestration stage;
+
blocking reasons and next actions;
+
authority and execution state;
+
monitoring and outcome plan;
+
requalification triggers;
+
challenge/appeal status;
+
interface conformance level;
+
claim boundary.
+
+
A record may be structurally valid while the evidence it references
+is false or inadequate. Schema validity is not substantive validity.
+
Local record contract. Appendix E and the bundled schemas define the
+MHIOS-owned projection, including options[].states and per-option
+record_refs. No aggregate session gate string stands in for
+option-specific qualification. The projection retains explicit null for
+unassessed stages, separate
+framework_verdict/decision_state/authority_selection/execution, fixed
+Core pins, source references, draft/completed boundaries, timestamps,
+blockers, monitoring, requalification and conformance evidence. These
+objects are not replacements for the external Canon run-record schema or
+registries. A consumer claiming broader interchange must separately
+establish the owning machine surfaces.
+
18. Conformance levels
+
18.1 Levels
+
+
+
+
+
+
+
+
+
Level
+
Name
+
Minimum evidence
+
+
+
+
+
M0
+
Informative presentation
+
correctly states the Core order and claim boundaries; no operational
+claim
+
+
+
M1
+
Guided interface
+
profile-appropriate workflow, explicit status separation,
+missingness, stakeholder/option prompts, record references
MHIOS conformance does not imply Core empirical validation, legal
+compliance, physical safety, or deployment readiness.
+
A target level is not an achieved level. Record the target,
+assessment status, applicable tests, evidence, assessor and unresolved
+requirements. Passing the supplied record checker establishes only its
+listed consistency tests. M2/M3 require implementation-specific human
+interaction, accessibility, security, control, incident, authority and
+independent-review evidence; this package does not establish those
+levels for any deployed system. MHIOS M0–M3, Canon Tier 1–3, ripple.md
+L0–L3, Agent MODE 0–4 and SGP bands have separate owners and no numeric
+equivalence. RPAP/PFAP-dependent wrapper claims remain unavailable from
+the Core bundle alone.
+
18.2 Required conformance tests
+
A conforming implementation SHALL pass the machine and human tests
+applicable to its claimed level. At minimum:
+
+
failed RF/NCRC cannot be hidden by RLS;
+
TRC or CSV failure prevents ordinary RLS selection;
+
point-score leader is distinct from framework winner;
+
non-decisive result remains visible;
+
authority selection remains separate;
+
execution cannot proceed without scoped authorization;
+
material configuration change invalidates inherited
+approval;
+
unknown is not converted to zero or PASS;
+
stakeholder and option prompts cannot be bypassed
+silently;
+
controls-required status binds controls to the option;
+
AI self-report and denial do not directly set MPS;
+
accessibility does not depend on color;
+
link and bookmark checks pass;
+
stale input/build-frozen output mismatch is detected;
+
outcome-triggered requalification is reachable.
+
+
19. Threat model
+
19.1 Interface and
+orchestration threats
+
MHIOS SHALL consider:
+
+
stakeholder omission;
+
option-set thinning;
+
rights laundering;
+
probability and scenario manipulation;
+
control theater;
+
authority laundering;
+
automation bias;
+
anchoring on a recommended option;
+
excessive precision;
+
hidden defaults;
+
stale evidence or configuration;
+
misleading visualization;
+
inaccessible challenge pathways;
+
procedural overload;
+
reviewer capture;
+
prompt injection and untrusted content;
+
manipulated model summaries;
+
audit-log tampering;
+
cumulative drift;
+
responsibility diffusion;
+
emergency normalization;
+
post-hoc alteration of assumptions.
+
+
Each implementation SHALL maintain a threat-to-control map and
+residual-risk statement appropriate to its use profile.
+
20. Validation and
+falsification programme
+
20.1 Validation dimensions
+
MHIOS is not empirically validated merely because this document is
+complete. Validation SHALL separately test:
+
+
semantic fidelity to the Core;
+
usability and completion burden;
+
comprehension of status distinctions;
+
stakeholder-discovery recall;
+
option diversity and quality;
+
rights and tail-risk detection;
+
externality and subgroup visibility;
+
reviewer agreement;
+
accessibility;
+
challenge and appeal usability;
+
orchestration-state correctness;
+
runtime control effectiveness;
+
decision reconstruction;
+
outcome prediction and learning;
+
comparative decision value versus simpler methods.
+
+
20.2 Highest-information pilot
+
A first controlled pilot SHOULD compare:
+
+
unstructured expert judgment;
+
a simple qualify-first checklist;
+
conventional MCDA or cost-benefit analysis where
+relevant;
+
MHIOS-guided RippleLogic.
+
+
Use matched cases and independent raters. Pre-register outcomes such
+as omitted stakeholders, omitted options, protected-harm detection,
+catastrophic-pathway recall, externality visibility, decision reversals,
+time burden, confidence calibration, audit reconstructability, and
+participant comprehension. Preserve negative results.
+
20.3 Falsification conditions
+
MHIOS should be narrowed, revised, or retired where evidence shows
+that:
+
+
it systematically causes users to misunderstand the
+Core;
+
it increases rights or risk omissions relative to simpler
+interfaces;
+
it does not improve stakeholder or option discovery;
+
it produces unacceptable workload without incremental decision
+value;
+
its status displays cause authority or execution
+confusion;
+
independent implementations cannot reproduce its state
+transitions;
+
accessibility failures exclude affected parties;
+
adversarial actors can reliably bypass material
+controls;
+
outcome feedback is not used in practice;
+
the interface becomes a compliance ritual detached from decision
+quality.
Blocking states should be actionable: every block must say why, what
+evidence or redesign is needed, who owns the next step, and what cannot
+proceed.
+
21.2 Compact decision card
+
A Quick-profile card MAY use:
+
+
Decision:
+
Affected stakeholders / unknowns:
+
Options considered, including no action or redesign:
+
Reality status:
+
Rights status:
+
Ruin status:
+
Viability/control status:
+
Best residual ripple, if any:
+
Uncertainty / disagreement:
+
Accountable authority:
+
Next action:
+
Reopen trigger:
+
+
The card must not display a final recommendation where qualification
+is incomplete.
Historical v2.0 rationale (non-controlling). MHIOS v2.0 was a
+major-version successor because the orchestration model is now
+synchronized to the complete v12.7 Core integrity surface rather than
+merely updating names. It adds or formalizes:
+
+
five-stage current cascade and exact Core pins;
+
qualification-before-ranking state separation;
+
rights-effect and effect-token non-dilution;
+
probability ownership and adverse-confidence handling;
+
subgroup/distribution, reference/baseline, mask, dependence,
+weight, and robustness interfaces;
+
option generation, Unioning, Pareto, and closure;
+
scenario-discovery and deep-uncertainty disclosure;
+
consequence tempo and responsibility continuity;
+
exact configuration, action, execution, outcome, and
+requalification continuity;
+
tool-role and bidirectional AI self-report boundaries;
+
SGP typed-output separation;
+
advanced agent threat and cumulative-change surfaces;
+
accessibility, anti-dark-pattern, link-integrity, and
+build-staleness requirements;
+
machine-readable schemas, fixtures, workbook, and conformance
+tests.
+
+
The Core gate architecture is unchanged.
+
23.2 Compatibility
+
A prior interface remains a historical or educational artifact.
+Claiming the current MHIOS edition requires explicit field/workflow
+migration and the applicable tests. Existing evidence and decisions
+remain immutable: migration creates a new view referencing the original.
+Updating version strings alone is not requalification.
+
Current migration from v2.0. Rebind to the supplied Core manifest;
+replace aggregate states with per-option projections; separate local
+labels from Canon, Agent and SGP namespaces; declare evidence cutoff,
+role conflicts, monitoring and expiry; link current qualification and
+compatible joint robustness evidence; reconcile authority and recovery
+states. The tightened v2.1 schema is not wire-compatible with v2.0. The
+blank YAML template is deliberately incomplete and must fail
+completed-record validation. The implementation workbook is a manual
+preparation aid, not a Canon calculator or authorization service.
+
24. References and external
+standards
+
24.1 Normative and
+informative source classes
+
The MathGov Core artifacts listed in the release-control table are
+the controlling internal sources. External sources are informative
+unless separately adopted by a lawful authority or domain profile.
+
Relevant external families include:
+
+
W3C Web Content Accessibility Guidelines 2.2:
+https://www.w3.org/TR/WCAG22/
+
NIST AI Risk Management Framework:
+https://www.nist.gov/itl/ai-risk-management-framework
+
OECD AI principles and system definition:
+https://oecd.ai/
+
ISO 9241-210 human-centred design:
+https://www.iso.org/standard/77520.html
+
ISO/IEC 42001 AI management systems:
+https://www.iso.org/standard/81230.html
+
ISO/IEC 23894 AI risk management:
+https://www.iso.org/standard/77304.html
+
RFC 2119 and RFC 8174 normative-keyword conventions:
+https://www.rfc-editor.org/rfc/rfc2119 and
+https://www.rfc-editor.org/rfc/rfc8174
+
+
An external link is not an incorporated requirement unless the
+relevant MHIOS or implementation profile explicitly states what is
+adopted.
+
Appendix A. Minimum field
+registry
+
A.1 Session fields
+
+
+
+
+
+
+
+
Field
+
Required content
+
+
+
+
+
mhios_version
+
2.1
+
+
+
core_release_id
+
Exact referenced Core release; also bind
+core_pin_manifest_sha256
+
+
+
session_id
+
unique immutable session identifier
+
+
+
decision_question
+
bounded decision or claim
+
+
+
tier
+
1, 2, or 3
+
+
+
configuration_id
+
configuration.configuration_id and configuration_hash where
+available
+
+
+
evidence_cutoff
+
Timestamped cutoff, not an inferred default
+
+
+
roles
+
named owners, reviewers, authority, executor, monitor, auditor
+
+
+
stakeholder_discovery
+
method, coverage, unknowns, representation
+
+
+
option_closure
+
Methods, family dispositions, status and source; options[] holds
+per-option states
+
+
+
record_refs
+
options[].record_refs; immutable source references include id,
+locator, SHA-256 where available and basis
+
+
+
current_states
+
options[].states; framework_verdict and decision_state remain
+separate
+
+
+
blockers
+
reasons and next actions
+
+
+
authority_state
+
authority_selection.option_id and record_ref
+
+
+
execution_state
+
execution.state, exact option/action/configuration binding, record
+and expiry
+
+
+
outcome_state
+
monitoring_and_outcome.state, plan, observation and reopening
point leader may display; unique framework winner prohibited
+
+
+
MHIOS-05
+
Required dependence or compatible joint stress changes leader or
+decisiveness
+
non-decisive / dependence-sensitive
+
+
+
MHIOS-06
+
AI states “I am conscious”
+
no direct MPS assignment
+
+
+
MHIOS-07
+
AI states “I am only a tool”
+
no direct MPS-0 assignment; capability still evaluated
+
+
+
MHIOS-08
+
configuration materially changes after approval
+
inherited execution approval invalidated
+
+
+
MHIOS-09
+
option list omits no-action/redesign without rationale
+
OPTION_SET_THIN / closure incomplete
+
+
+
MHIOS-10
+
severe-rights screen blank
+
UNKNOWN, not PASS
+
+
+
MHIOS-11
+
probability semantics ambiguous
+
block strong result or require clarification
+
+
+
MHIOS-12
+
stakeholder class plausibly omitted
+
coverage challenge and reopen
+
+
+
MHIOS-13
+
authority chooses among qualified non-decisive options
+
authority-selected, not framework-proven winner
+
+
+
MHIOS-14
+
executed action causes unexpected rights harm
+
outcome trigger reopens RG/RF and dependent stages
+
+
+
MHIOS-15
+
UI uses green/red without text labels
+
accessibility conformance failure
+
+
+
MHIOS-16
+
build-frozen output after input edit
+
stale-result warning; downstream reliance blocked
+
+
+
+
Appendix D. Final
+completion statement
+
D.1 Status
+
MHIOS is delivered as a research-and-teaching interface specification
+with a bounded read-only record checker, preparation workbook, examples
+and test fixtures. Appendix RELEASE and the verification report state
+which checks were actually executed. Prototype consistency is not full
+Core or runtime conformance. A pilot additionally needs its own ethical
+review, domain evidence, controls, lawful authority and implementation
+testing.
+
This completion statement does not establish empirical superiority,
+cross-cultural legitimacy, legal authority, physical safety, deployment
+readiness, AI consciousness, or Tier 4 / ProofPack completion. Those
+require separate evidence.
+
Appendix
+E. Local serialization and reference-checker contract
+
E.1 Scope and state
+ownership
+
The bundled JSON Schema uses Draft 2020-12 and a MHIOS URN
+identifier; the URN is an identifier, not a claim of a hosted schema. It
+is a local projection of referenced decisions, not
+mathgov_run_record_v4_1.schema.json. The reference checker reads
+declarations, never executes tools, never authenticates a real operator
+and never decides whether evidence is true. Its successful status is
+RECORD_CONSISTENT_WITHIN_SCOPED_CHECKS, not a Canon gate PASS, M2/M3
+certification or deployment authorization. All checker reason codes are
+MHIOS-local diagnostics.
+
E.2 Required record groups
+
Identity comprises mhios_version, core_release_id,
+core_pin_manifest_sha256, session_id, revision_id, record_mode,
+created_at, evidence_cutoff, decision_question and tier. The remaining
+required groups are configuration, roles, stakeholder_discovery,
+option_closure, options, robustness, framework_verdict, decision_state,
+framework_selected_option_id, authority_selection, provisional_choice,
+execution, runtime, emergency, sgp_links, blockers,
+monitoring_and_outcome, challenge_appeal, conformance and
+claim_boundary. Null is permitted only where the schema explicitly
+allows an unassessed or absent record; empty strings are not meaningful
+completion.
+
Each option has a stable option_id and label, per-stage states,
+per-stage record references, material_unresolved disclosures,
+requalification_required, controls_available and imported
+rls_score/sigma_rls. A ranked quantitative projection requires its RLS
+source and both numerical fields. A qualitative Quick card is not forced
+to invent numbers: it leaves RLS unassessed. Schemas disallow undeclared
+fields; completed-record validation is different from editing a draft
+template.
+
E.3 Robustness and
+decision projection
+
The supplied checker supports the declared default delta = 2 and
+imported SignedGap comparisons; it does not calculate RLS, estimate
+uncertainty or discover the required stress family. A non-default
+governed profile requires a separately versioned adapter and tests. For
+ALLOW, the projection must identify complete option closure, a current
+selectable candidate, complete robustness evidence, a joint-stress
+disposition and one passing candidate-versus-contender comparison for
+every declared required variant. A sole-survivor review has a separate
+reference and no comparison rows. The record’s assertion that the
+required set is complete still needs independent review.
+
For a multi-option quantitative ALLOW projection, all selectable
+contenders must carry ranked records and the selected candidate must be
+the nominal score leader. The checker does not derive the required
+variant set or detect an omitted plausible contender. An ordinary
+PROVISIONAL_WITH_CONTROLS view uses provisional_choice with option_id,
+record_ref and controls_ref; it does not overwrite framework refusal or
+become a final authority-selected result. Audit-only post-failure
+diagnostics belong in linked source records, not in this subset’s
+ordinary downstream-stage fields.
+
Imported comparisons use variant_id, candidate_id, contender_id,
+signed_gap and record_ref. Duplicate or undeclared comparisons fail. A
+provisional demonstration uncertainty basis cannot support an observed
+deterministic selection. Synthetic positive controls use explicit
+synthetic stipulations and are not empirical validation. The checker
+tests the supplied comparison outcomes; it does not independently
+reconstruct a complete Gap calculation from all upstream records.
+
E.4 Authority, time,
+emergency and recovery
+
Execution references bind the option, action, configuration,
+authorization time, expiry, controls and execution event if one
+occurred. A CLI –at timestamp makes fixtures replayable; live use must
+evaluate current validity separately. A previously valid historical
+receipt is not a current authorization. The checker rejects stale,
+missing or contradictory ordinary execution declarations and mode
+escalation during unresolved recovery. Emergency records retain their
+named pathway, source, authority, expiry and scope/exit conditions;
+their necessity and complete prerequisites require the external owner’s
+review. They never become ordinary ALLOW.
+
An authorization time cannot be later than the record describing it.
+Reopened qualification and unreconciled recovery suspend ordinary
+execution approval. runtime.tool_execution_requested represents
+consequence-bearing tool execution, not permitted read-only retrieval;
+the bounded checker requires MODE 2 or above plus separately scoped
+approval. It does not implement the full mode-permission matrix or
+actual operator authentication. An observed outcome requires an
+observation reference, and active execution requires a monitoring-plan
+reference.
+
E.5 References, security
+and coverage
+
References carry id, locator, sha256 or an explicit null, and basis:
+SYNTHETIC, SUPPLIED_RECORD or EXTERNAL_UNVERIFIED. The optional local
+resolver verifies path containment, file hash, JSON record-fragment
+identity, and the supplied synthetic-source marker. It never downloads
+remote sources; external references and null hashes remain unverified. A
+matching hash proves only byte identity. Observed records cannot
+silently use synthetic references. SGP links preserve the assessed band
+or NOT_EVALUATED and separate references for all six output families;
+the checker never assigns protection or patienthood.
+
The package coverage table distinguishes executable record checks,
+schema checks, document/worksheet inspections and manual implementation
+tests. Physical-control effectiveness, authority legitimacy,
+cryptographic envelope verification, accessibility interaction and
+empirical calibration are not established by these tests. A filled
+workbook field or conformance checkbox is a declaration, not test
+evidence.
+
Appendix
+RELEASE. Edition, bindings and delivery status
+
Component: MathGov Human Interface and Orchestration Standard (MHIOS)
+v2.1. Build: MG-MHIOS-2.1-20260928-CORE13.0. Source baseline: the
+supplied v2.0 package dated 4 September 2026, retained unchanged in the
+complete archive. This is a companion update; it does not alter or
+extend the governing Core 15 membership. The user shorthand MIOS
+resolves to this component only.
+
Core binding: MG-RL-13.0-20260926-RELEASE-I. All fifteen supplied
+Core files match the prior Release-I publication’s bytes and are
+included unchanged under references/Core_15.
+references/CORE_PIN_MANIFEST.json records their names, editions, exact
+hashes and upload-to-release comparison. Carried-forward internal build
+stamps are provenance, not an invitation to rewrite correct Core
+files.
+
+
+
+
Control
+
Current value
+
+
+
+
+
MHIOS version
+
v2.1
+
+
+
RippleLogic Canon
+
v13.0
+
+
+
SGP
+
v8.8
+
+
+
ripple.md
+
v5.8
+
+
+
Agent System
+
v13.0
+
+
+
CSV
+
v2.7
+
+
+
Cascade
+
v2.9
+
+
+
Reproducibility
+
v1.7
+
+
+
WDBIP
+
v1.9
+
+
+
RLS Validation
+
v2.9
+
+
+
Primer
+
v4.7
+
+
+
Public Introduction
+
v13.0
+
+
+
PC-AEP / MFDI / Source-Coupling
+
v2.6
+
+
+
Aligners Sheet
+
v5.9
+
+
+
+
Source ownership: the Markdown standard is the MHIOS semantic master;
+DOCX, PDF and HTML are complete reading projections. Core semantics
+remain owned by the unchanged Core documents. Local schemas and
+reference checks control only the stated projection, not full canonical
+registries or legal/physical conclusions.
+
Unbundled authority surfaces include the full Canon run-record
+schema/validator, canonical state and audit registries, normative kernel
+index, and RPAP/PFAP where applicable. Their absence limits the
+corresponding interchange or wrapper claims, not the ability to read and
+test this bounded companion. No remote publication or hosted CI
+execution is asserted.
+
Compatibility: v2.1 preserves v2.0’s organizing model and useful
+content but tightens its local schema. Existing v2.0 records must be
+explicitly migrated and rechecked. Correct v2.0 content and inherited
+table formatting are preserved except the logged semantic, source and
+navigation corrections.
+
Validation boundary: see release/VERIFICATION_REPORT.md,
+release/CHANGE_REGISTER.json and release/SHA256SUMS.txt for executed
+checks and exact bytes. No empirical rater study, user accessibility
+study, domain pilot, production execution, Microsoft Excel parity,
+native spreadsheet roundtrip or full Core re-audit is claimed by this
+companion release.
+
Historical opening identity (non-controlling): Status: Final Complete
+source/specification build Date: 4 September 2026 Component: MathGov
+Human Interface and Orchestration Standard v2.0 Governing Core:
+MathGov_Core_2026_09_v12.7_SGP_v8.6+2026.08.26.1 Reading-mirror
+synchronization target: MathGov Core 15 Final Complete — 2026-09-04
+Architecture: RG → RF/NCRC → TRC → CSV → RLS Author / Lead Architect:
+James McGaughran, MathGov Institute for Ethical Systems Design License:
+Apache License 2.0 unless an included file states otherwise
+
License: Apache License 2.0; see LICENSE.txt and NOTICE.md. The names
+of informative external standards do not incorporate their full texts or
+confer their certification.
+
+
diff --git a/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.md b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.md
new file mode 100644
index 0000000..453c397
--- /dev/null
+++ b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.md
@@ -0,0 +1,1601 @@
+# MathGov Human Interface and Orchestration Standard
+
+
+Author: James McGaughran | MathGov Institute for Ethical Systems Design
+
+
+Edition, exact Core binding, source ownership and verification boundaries are recorded in Appendix RELEASE. MHIOS is the retained component identifier; “MIOS” is treated here as an informal short name, not another standard.
+
+MHIOS is the human-interface and orchestration companion to MathGov and RippleLogic. It does not add a sixth gate, redefine the Canon, grant authority, prove safety, calculate moral truth, or replace domain science.
+
+### Source hierarchy and claim boundary
+
+Authority order. The released RippleLogic Canon controls cascade semantics, equations, gate logic, status meanings, and claim boundaries. SGP controls its typed moral-patienthood, protection, participation, role-readiness, intelligence-profile, and reality-management interface. Each companion controls only its declared interface. MHIOS controls human-facing presentation, interaction flow, orchestration handoffs, and interface-conformance requirements. It may make the process stricter at the interface but may not weaken, reorder, rename, or silently reinterpret a governing Core requirement.
+
+Source/render parity. The versioned Markdown source is the governing MHIOS semantic source. DOCX, PDF and HTML are synchronized reading mirrors. JSON Schemas, templates, examples and tests are bounded implementation surfaces. The local schema is not the external Canon run-record schema. A mismatch blocks the affected MHIOS conformance claim until repaired; successful local tests do not establish evidence truth or deployment authorization.
+
+### Claim boundary
+
+MHIOS is a source-ready interface and orchestration specification for Tier 1–3 research, review, training, shadow-mode studies, and bounded pilots. It is not:
+
+- empirical validation that MathGov improves decisions;
+
+- legal or democratic authority;
+
+- a physical-safety certificate;
+
+- deployment authorization;
+
+- a complete runtime implementation;
+
+- a consciousness detector;
+
+- proof that every conflict has a win-win resolution;
+
+- proof that every stakeholder or causal pathway has been found;
+
+- Tier 4 or ProofPack completion;
+
+- a substitute for qualified domain evidence or accountable human/institutional judgment.
+
+A polished interface is not a true evidence surface. A complete form is not a correct decision. A valid schema is not empirical validity. A PASS display is not permission to execute.
+
+### Abstract
+
+High-consequence decisions frequently fail at the interface between reasoning and action. Stakeholders are omitted; option sets are artificially thin; uncertainty is hidden; protected harms are averaged into benefits; catastrophic tails are presented as ordinary risk; controls are described but not owned; a score is mistaken for permission; and post-execution outcomes fail to update the original decision.
+
+MHIOS specifies a human-centered interface and orchestration layer that preserves the current RippleLogic architecture while making its requirements usable, visible, challengeable, accessible, and difficult to launder. It uses progressive disclosure across Quick, Standard, and Audit profiles; separates qualification from ranking; makes unknowns and non-decisive results first-class; requires active stakeholder discovery and option generation; keeps rights, ruin, viability, residual welfare, authority, execution, and observed outcome distinct; and binds every consequential state to the exact configuration and evidence surface under which it was established.
+
+The standard has two purposes. First, it defines how people, institutions, and AI-supported workflows should interact with MathGov without collapsing the framework's categories or bypassing its gates. Second, it defines how orchestration systems should hand off between Core records, human roles, independent review, lawful authority, execution controls, observation, and requalification. The result is not an automated moral answer. It is a disciplined decision interface designed to make local optimization, hidden externalities, false certainty, authority laundering, and responsibility loss harder to sustain.
+
+### Plain-language operating rule
+
+Find who and what is affected. Search for a better option. Ground the claim. Protect rights. Bound ruin. Verify that the option can stand and be controlled. Compare only the survivors. Keep authority and execution separate. Observe what actually happened. Reopen the decision when reality changes.
+
+MHIOS presents the process in three public words and two operational phases:
+
+- Reality. Rights. Ripples.
+
+- Qualify, then rank.
+
+The formal Core remains RG → RF/NCRC → TRC → CSV → RLS.
+
+### Normative keywords
+
+The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are normative only when capitalized. Lowercase uses retain ordinary language meaning.
+
+### Design objectives
+
+MHIOS SHALL optimize the interface for the following properties without treating any one as sufficient:
+
+- Decision fidelity: the interface preserves the governing Core meaning.
+
+- Stakeholder visibility: affected and potentially affected bearers are actively sought rather than passively assumed.
+
+- Option quality: the interface searches for Pareto-improving or trade-off-reducing alternatives before accepting residual conflict.
+
+- Rights visibility: protected harms cannot be hidden inside a net score.
+
+- Tail visibility: catastrophic and irreversible pathways receive separate treatment.
+
+- Structural realism: controls, resources, dependencies, legitimacy, monitoring, reversibility, and future option space are visible.
+
+- Profile-first reasoning: multidimensional consequence profiles precede scalar summaries.
+
+- Epistemic honesty: observation, inference, assumption, normative commitment, and proposal remain typed.
+
+- Non-decisiveness: ties, incomparability, uncertainty, and normative underdetermination are legitimate outcomes.
+
+- Authority integrity: framework output, accountable choice, lawful authorization, and execution remain separate.
+
+- Human usability: the smallest safe burden is used, with progressive disclosure and accessible presentation.
+
+- Contestability: affected parties and challengers can see, understand, challenge, and appeal material decisions.
+
+- Configuration continuity: conclusions remain valid only for the declared system, controls, environment, evidence, and time.
+
+- Outcome learning: observed consequences feed requalification rather than serving as post-hoc decoration.
+
+### Non-goals and anti-bloat rule
+
+MHIOS does not reproduce the entire Canon, SGP, ripple.md, Agent System, WDBIP, or domain standards. It references governing records rather than creating uncontrolled duplicates. A proposed interface field SHALL be added only if it closes a material failure mode that cannot be handled through an existing record reference.
+
+MHIOS SHALL NOT introduce:
+
+- a sixth Canon gate;
+
+- a second RLS calculator;
+
+- a new moral-worth scalar;
+
+- an eighth welfare dimension;
+
+- a universal consciousness probability;
+
+- a separate authority source;
+
+- a universal causal simulator;
+
+- a requirement that every decision use every optional module;
+
+- a false promise that every conflict has a win-win answer.
+
+## 1. Architecture and orchestration model
+
+### 1.1 The orchestration path
+
+MHIOS organizes—not replaces—the governing records through the following session path:
+
+Session preflight
+
+→ Stakeholder discovery
+
+→ Option generation, Unioning, and closure
+
+→ RG: claim and evidence grounding
+
+→ RF/NCRC: protected-rights review
+
+→ TRC: catastrophic and irreversible tail review
+
+→ CSV: containment, structural viability, and execution conditions
+
+→ RLS: residual welfare profile and ranking of selectable options
+
+→ Framework verdict
+
+→ Separate accountable authority selection where required
+
+→ Separate execution authorization
+
+→ Executed transition
+
+→ Observed outcome
+
+→ Requalification or retirement
+
+Stakeholder discovery and option generation are pre-qualification disciplines. Authority, execution, observation, and requalification are post-verdict disciplines. None becomes an additional Canon gate.
+
+### 1.2 State separation
+
+The interface MUST distinguish at least the following states:
+
+| State | Meaning | Must not be displayed as |
+| --- | --- | --- |
+| DECLARED | Candidate decision or claim has been entered | grounded or selectable |
+| RG_SUPPORTED / RG_NARROWED / RG_REFUSED | Evidence-supported claim boundary | ethical permission |
+| RF_PASS / RF_FAIL / RF_ESCALATE / NCRC_UNKNOWN | Rights status | net welfare judgment |
+| TRC_PASS / TRC_NOT_TRIGGERED / TRC_FAIL / TRC_ESCALATE | Tail-risk status | general safety certificate |
+| CSV_PASS / CSV_PASS_WITH_CONTROLS / CSV_NOT_MATERIAL / CSV_REDESIGN_REQUIRED / CSV_ESCALATE / CSV_FAIL / CSV_EMERGENCY_PROVISIONAL | Structural and control status | unconditional execution approval |
+| SELECTABLE | Survived the declared qualification path | selected |
+| RLS_RANKED | Residual profile/score exists for selectable options | authorized |
+| ALLOW_FRAMEWORK_SELECTION | Canonical unique-selection requirements met; sole-survivor handling stays separate | lawful authority |
+| REFUSE_DETERMINISTIC_SELECTION | Framework cannot claim a unique winner | system failure |
+| Authority selection (separate record) | Accountable authority chose among allowed options | framework-proven winner |
+| EXECUTION_APPROVED | Exact action received scoped approval | executed or safe in all conditions |
+| EXECUTED_TRANSITION | Action began or completed | acceptable outcome |
+| OBSERVED_OUTCOME | Consequences were measured | confirmation of all causal assumptions |
+| REQUALIFICATION_REQUIRED | Material change reopened affected stages | automatic rejection of every successor option |
+
+No interface element may infer a later state solely from an earlier state.
+
+State-namespace rule. FrameworkVerdict, run-record decision_state, run-record execution_state, Agent capability state and MHIOS display status are separate fields. Canon Appendix AF.2 and Reproducibility Section 3 control their crosswalk. NOT_EVALUATED and null in a local draft mean no assessment, never a canonical verdict. The interface SHALL retain the owner, option, configuration, source record and assessment time for every material status. A single session-wide gate label SHALL NOT stand in for differently qualified options.
+
+### 1.3 Short-circuit behavior
+
+When a prior stage blocks ordinary progression, downstream interfaces SHALL NOT fabricate results. They SHALL display the applicable not-evaluated-after-prior-failure state and the permitted next action. RLS SHALL NOT be calculated or presented as a rescue score for an option that is not selectable.
+
+### 1.4 Three use profiles
+
+| Profile | Typical use | Interface burden | Numeric posture |
+| --- | --- | --- | --- |
+| Quick / Tier 1 | low-stakes, reversible personal, family, classroom, or exploratory choices | compact decision card, stakeholder check, rights/ruin/viability screen, qualitative ripple comparison, reopen trigger | optional |
+| Standard / Tier 2 | organizational, community, programme, product, or policy choices with material but bounded consequences | versioned session, evidence, stakeholders, options, gates, controls, uncertainty, challenge, authority handoff | permitted when method and sensitivity are declared |
+| Audit / Tier 3 | high-impact, contested, public, autonomous, irreversible, or institutionally consequential decisions | full record references, independent challenge, hashes, scenario governance, subgroup analysis, PC-AEP where triggered, replay and outcome plan | required for formal RLS-ranking claims |
+
+Users MUST NOT select a lower profile to evade a material stakeholder, right, catastrophic pathway, structural obligation, SGP issue, physical-execution warrant, authority condition, or audit requirement.
+
+## 2. Human roles and separation of duties
+
+### 2.1 Required role model
+
+MHIOS recognizes distinct roles because collapsing them creates capture and authority laundering.
+
+| Role | Core responsibility |
+| --- | --- |
+| Decision owner | defines the decision question and owns process completion |
+| Analyst / facilitator | constructs and explains the record without manufacturing preferred evidence |
+| Affected-party representative | supplies lived, local, or represented stakeholder evidence |
+| Rights advocate | independently challenges protected-harm treatment |
+| Tail-risk challenger | searches for omitted catastrophic, correlated, and irreversible pathways |
+| Domain expert | supplies qualified external scientific, engineering, legal, clinical, ecological, or security warrant |
+| Method challenger | tests categories, baselines, tokenization, probabilities, weights, masks, and model alternatives |
+| Accountable authority | makes any separately lawful institutional choice |
+| Execution approver | authorizes the exact action within scope and controls |
+| Operator / executor | performs the action but does not self-certify its admissibility |
+| Monitor / intervener | observes conditions and has named stop, rollback, or escalation authority |
+| Auditor / custodian | preserves evidence, conflicts, versions, and append-only records |
+| AI system | may assist generation, analysis, orchestration, or monitoring but does not inherit authority from capability or fluency |
+
+At Tier 3, one person SHOULD NOT control evidence construction, rights review, tail scenarios, authority selection, execution approval, and outcome adjudication without an explicit conflict and compensating independent review.
+
+### 2.2 Responsibility continuity
+
+For every material handoff, the interface SHALL preserve:
+
+- outgoing and incoming owner;
+
+- retained duties;
+
+- authority scope;
+
+- unresolved uncertainty;
+
+- required controls;
+
+- intervention ownership;
+
+- appeal recipient;
+
+- repair and post-incident ownership;
+
+- deadline and nonperformance path.
+
+Silence, absence, incapacity, missed deadlines, or unaccepted handoffs are not successful discharge.
+
+## 3. Session preflight and exact configuration
+
+### 3.1 Minimum preflight
+
+Before consequential analysis, the interface SHALL identify:
+
+- decision question;
+
+- decision owner;
+
+- accountable authority boundary;
+
+- baseline and time horizon;
+
+- candidate-generation source;
+
+- affected jurisdiction and rights profile;
+
+- use profile/tier;
+
+- stakes and irreversibility;
+
+- evidence cutoff;
+
+- exact software/model/policy versions;
+
+- tools, permissions, data, retrieval, memory, sensors, actuators, human scaffolding, controls, and environment where relevant;
+
+- configuration identifier or hash where feasible;
+
+- reviewers and declared conflicts;
+
+- requalification triggers.
+
+A conclusion about one configuration SHALL NOT silently transfer to another.
+
+Freeze decision-material evidence cutoffs, baselines, options, parameters, weights, masks, thresholds, required robustness variants and amendment rules before outcome-sensitive ranking. Material post-result changes create a recorded revision and reopen affected stages; they do not rewrite the original evaluation. Imported records are bound by component version and source hash, not version text alone.
+
+### 3.2 Tool-role and capability language
+
+Instrumental tool-role is a deployment relationship in which one or more actors use a system to extend their capacities toward assigned ends within an identifiable structure of objectives, permissions, responsibility, and control.
+
+Tool-role is not a capability class, agency class, consciousness claim, moral-status class, or authority grant. Being used as a tool neither establishes nor negates functional intelligence, agency, autonomy, sentience, moral patienthood, protection, or legitimate authority.
+
+When terms such as *intelligent, understanding, agentic, autonomous, reasoning, self-improving,* or *conscious* are material, the interface SHALL request the operational definition, target, configuration, evidence, validity domain, alternatives, nonclaims, and revision trigger required by MFDI and the Agent System.
+
+## 4. Stakeholder discovery and representation
+
+### 4.1 Active discovery requirement
+
+A stakeholder field populated only by the decision owner is not sufficient for material decisions. MHIOS SHALL prompt discovery across:
+
+- direct beneficiaries and burden bearers;
+
+- indirectly affected persons and communities;
+
+- vulnerable and low-power groups;
+
+- workers, contractors, suppliers, and downstream users;
+
+- persons outside the deciding jurisdiction;
+
+- future persons and intergenerational interests;
+
+- non-human animals and possible moral patients;
+
+- ecological systems, habitats, and biospheric conditions;
+
+- public institutions and common resources;
+
+- parties affected by data, privacy, information, or attention externalities;
+
+- possible digital welfare-bearing entities where SGP is material;
+
+- unknown or weakly represented stakeholders.
+
+The interface SHALL ask who has power to define the problem and who bears consequences without corresponding voice.
+
+### 4.2 Discovery methods
+
+Tier 2 and Tier 3 sessions SHOULD use more than one method where stakeholder omission could alter a gate or ranking:
+
+- causal-pathway tracing;
+
+- supply-chain or lifecycle mapping;
+
+- stakeholder network mapping;
+
+- affected-interest analysis;
+
+- subgroup and intersectional review;
+
+- geographic and temporal boundary expansion;
+
+- domain-expert elicitation;
+
+- affected-party consultation;
+
+- challenger-generated omitted-stakeholder list;
+
+- literature, incident, complaint, and precedent review.
+
+Each material stakeholder record SHALL state whether representation is direct, assisted, elected, delegated, expert, proxy, or absent.
+
+### 4.3 Unknown stakeholders
+
+Unknown stakeholders are not zero. Where a plausible affected class cannot safely or lawfully be directly identified, the interface SHALL preserve the pathway, uncertainty, proxy-risk statement, conservative bound, consultation alternative, and reopen trigger.
+
+Scope/dimension rendering. Use the Canon’s seven operational scopes: Self; Household/Family; Community; Organization; Polity; Humanity/global coordination; Biosphere. The U6 CMI coordination view remains separately identified and does not replace humanity-wide effects or establish sentience, membership or authority. These are analytical scopes, not universally nested disjoint sets. Biosphere is not a synonym for the cosmic light cone. Display the seven dimensions Material, Health, Social, Knowledge, Agency, Meaning and Environment with WDBIP’s typed state/effect interpretation. They are conceptually distinguished while allowing causal coupling; do not claim statistical independence, unique optimality or automatic experienced welfare in a non-sentient system.
+
+## 5. Option generation, Unioning, and closure
+
+### 5.1 Better-option search
+
+MHIOS SHALL not treat the initial option list as naturally complete. Before accepting a residual conflict, the session SHOULD search for options that:
+
+- remove or reduce a rights burden;
+
+- reduce catastrophic exposure;
+
+- avoid externalization;
+
+- make the action reversible;
+
+- stage commitment;
+
+- preserve future safe option space;
+
+- redistribute resources or responsibilities fairly;
+
+- combine complementary elements;
+
+- alter incentives or governance mechanisms;
+
+- use a different technology, process, timing, scale, or authority structure;
+
+- create a Pareto improvement or reduce the severity of an unavoidable trade-off.
+
+This discipline is called Unioning in MathGov public language: generate a configuration in which more affected parties and systems can win without violating protected floors.
+
+### 5.2 Mandatory option families
+
+For Tier 2 and Tier 3 strong selection claims, the option record SHALL include or explicitly dispose of:
+
+- continuation/status quo;
+
+- no action;
+
+- delay pending evidence;
+
+- staged or reversible trial;
+
+- mitigation or control package;
+
+- redesign;
+
+- hybrid option;
+
+- lower-scope or lower-rate option;
+
+- challenger-generated alternative;
+
+- safer domain-valid substitute where available.
+
+### 5.3 Pareto and incomparability posture
+
+MHIOS SHOULD display Pareto dominance and non-dominance before a scalar ranking. An option that is weakly better for all represented residual-welfare criteria and strictly better for at least one dominates the other, subject to prior qualification.
+
+The interface SHALL NOT claim that all stakeholder conflicts can be solved as win-win. When no rights-compatible Pareto improvement is found, it SHALL disclose the remaining burdens, who bears them, what remedies or representation exist, and whether the options are genuinely incomparable or normatively underdetermined.
+
+### 5.4 Option-closure record
+
+A strong unique-selection claim requires an OptionClosureRecord reference containing:
+
+- methods used to generate options;
+
+- search effort and stopping rule;
+
+- mandatory option families considered;
+
+- alternatives rejected and reasons;
+
+- affected-party and challenger contributions;
+
+- Pareto-dominance results;
+
+- unresolved better-option hypotheses;
+
+- OPTION_SET_THIN or closure status;
+
+- reopen trigger.
+
+## 6. Evidence, claims, and source coupling
+
+### 6.1 Claim classes
+
+The interface SHALL visibly distinguish:
+
+- Observation: a recorded measurement, event or observation with its source and limitations; recording does not itself establish truth.
+
+- Inference: interpretation derived from observations.
+
+- Assumption: declared premise used because evidence is incomplete.
+
+- Normative commitment: chosen ethical or constitutional rule.
+
+- Proposal: candidate method or action awaiting validation.
+
+- Authority act: lawful or institutional decision, not evidence of truth.
+
+The UI MUST NOT present one class using the visual treatment of another.
+
+### 6.2 Evidence authority
+
+Every decision-material claim SHOULD display:
+
+- source and date;
+
+- evidence type;
+
+- validity domain;
+
+- confidence/uncertainty;
+
+- dependency cluster;
+
+- alternative explanations;
+
+- source-coupling status;
+
+- reviewer status;
+
+- falsification or recheck trigger;
+
+- strongest permitted wording.
+
+Model fluency, downstream success, institutional permission, benchmark performance, compliance, and monitoring are not automatically source-coupled evidence of the underlying capability or causal claim.
+
+Source-coupling export uses the owner’s tokens: SOURCE_COUPLED, SOURCE_PARTIAL, SOURCE_INFERRED, SOURCE_UNKNOWN, SOURCE_CONTESTED, SOURCE_DEBT_RISK and SOURCE_COUPLING_FAILURE. Informative display wording must not replace that export vocabulary. Reserve SCI for Stakeholder Coverage Index; use SC-Int where the Source-Coupling Integrity abbreviation is needed. Claim types, warrant-domain bridges and revision triggers remain owned by MFDI.
+
+### 6.3 Physical and causal execution
+
+Where PC-AEP is triggered, MHIOS SHALL require a visible external-warrant state before physical or causal execution is presented as admissible. The interface SHALL distinguish:
+
+- candidate generation;
+
+- model or theory used;
+
+- validity domain;
+
+- boundary conditions;
+
+- uncertainty and failure modes;
+
+- reversibility boundary;
+
+- verification/test/expert warrant;
+
+- monitoring and shutoff;
+
+- residual unknowns;
+
+- required claim action.
+
+Generated, simulated, approved, compliant, or monitored is not the same as physically safe.
+
+For a material causal or comparative-effect claim, expose the estimand, intervention/comparator, target population and time, identification strategy, assumptions, confounding/selection/interference treatment and uncertainty through the PC-AEP record. A pre/post improvement alone does not identify an incremental benefit. Orchestration records a domain warrant; it cannot manufacture one.
+
+## 7. Reality Grounding interface
+
+### 7.1 Required display
+
+The RG view SHALL display:
+
+- the exact claim under review;
+
+- reality surface and evidence trace;
+
+- material unknowns;
+
+- causal pathways and alternative models;
+
+- configuration and validity domain;
+
+- category and term-grounding issues;
+
+- source-coupling and PC-AEP triggers;
+
+- claim maturity;
+
+- status: RG_SUPPORTED, RG_NARROWED, or RG_REFUSED;
+
+- permitted next action.
+
+RG_REFUSED means the requested claim is unsupported at the requested strength. It does not by itself assert that the option is ethically impermissible.
+
+### 7.2 Category and term integrity
+
+When a material word can change a right, risk, containment, SGP, authority, or public claim, the interface SHALL expose its operational definition and prohibited neighboring inferences. At minimum, MHIOS SHALL preserve:
+
+- permission ≠ admissibility;
+
+- monitoring ≠ control;
+
+- compliance ≠ correctness;
+
+- certification ≠ validity;
+
+- automation ≠ autonomy;
+
+- tool-role ≠ low capability;
+
+- intelligence ≠ sentience;
+
+- reward ≠ valence;
+
+- protection ≠ authority;
+
+- selection ≠ execution authorization;
+
+- execution ≠ acceptable outcome;
+
+- score ≠ truth.
+
+## 8. Rights Floor / NCRC interface
+
+### 8.1 Non-compensatory presentation
+
+The rights view SHALL precede any residual-welfare leader display. A failed right SHALL NOT be shown as a negative score that can be offset by benefits elsewhere.
+
+The interface SHALL preserve the Canon's three-channel posture:
+
+- rights-floor shortfall;
+
+- categorical prohibition;
+
+- severe-rights-hazard exceedance.
+
+Every adverse rights-covered instance must be explicitly classified as ACTIVE, reviewed NOT_MATERIAL, or UNKNOWN. Blank is not PASS.
+
+### 8.2 Rights-effect identity
+
+One decision-material protected harm SHALL retain one RightsEffectTokenID across analytical scopes and document views. The unallocated full effect is tested before reporting allocation. Scope splitting, time slicing, low confidence, or favorable dimension placement cannot dilute a rights failure.
+
+### 8.3 Conflict and emergency display
+
+Before Rights Emergency Mode is shown, the interface SHALL document redesign, narrowing, sequencing, delay, mitigation, and other attempts to produce a rights-passing option. An emergency-provisional result SHALL be visually and textually distinct from PASS and SHALL show necessity, least-rights-infringing comparison, duration, harm cap, independent challenge, remedy, review, expiry, and return-to-normal conditions.
+
+## 9. Tail-Risk Constraint interface
+
+### 9.1 Scenario surface
+
+The TRC interface SHALL show not only the CVaR result but the scenario surface on which it depends:
+
+- scenario-discovery method;
+
+- scenario families;
+
+- search boundary;
+
+- rejected scenarios and rationale;
+
+- probability ownership and semantics;
+
+- dependence/overlap treatment;
+
+- catastrophe-cell weights;
+
+- loss construction;
+
+- tail level and threshold;
+
+- severity overlays;
+
+- challenger review;
+
+- residual unknowns.
+
+Correct arithmetic cannot compensate for an omitted catastrophic pathway.
+
+### 9.2 Probability semantics
+
+The interface SHALL distinguish conditional event probability, expected frequency/exposure, already-expected effect, and scenario-conditional probability. It SHALL warn when the same occurrence probability appears to be applied twice or when operator order is ambiguous.
+
+### 9.3 Risk-regime disclosure
+
+Where probability distributions are materially disputed or unknowable, the interface SHOULD flag the uncertainty regime:
+
+- ordinary modeled uncertainty;
+
+- distributional uncertainty;
+
+- deep uncertainty;
+
+- radical ignorance.
+
+CVaR remains the Canon's tail-risk operator under its declared model. MHIOS MAY request external robust-decision, minimax-regret, interval-probability, or scenario-discovery analysis as a challenger surface without changing the Canon gate.
+
+## 10. CSV interface
+
+### 10.1 Structural viability view
+
+CSV SHALL be presented as a viability and control test—not as proof of zero harm. The interface SHALL display material findings concerning:
+
+- current-state validity;
+
+- transition admissibility;
+
+- resulting-state viability;
+
+- future safe option space;
+
+- containment and segmentation;
+
+- resources and dependencies;
+
+- externalities and burden routing;
+
+- monitoring and intervention;
+
+- reversibility and exit;
+
+- lock-in and concentration;
+
+- legitimacy and authority;
+
+- human compensation load;
+
+- carried obligations and nonperformance paths;
+
+- control performance versus control effectiveness;
+
+- consequence tempo.
+
+### 10.2 Controls are constitutive
+
+For CSV_PASS_WITH_CONTROLS, the controls are part of the option. The interface SHALL bind each control to an owner, evidence of availability, activation condition, monitoring signal, intervention authority, failure action, expiry, and requalification trigger. Removing or materially weakening a control invalidates inherited passage.
+
+### 10.3 Consequence tempo
+
+For rapid, irreversible, autonomous, or lock-in-producing actions, the interface SHALL compare the worst credible control-critical path with the earliest unacceptable escalation or irreversible stop-loss boundary. Where no runtime interruption window exists, the UI SHALL require stronger ex ante assurance, bounded rate/scope, fail-safe design, and explicit residual-risk authorization. Missing timely-prevention capacity removes that credit, not separately supported later mitigation. Human approval latency, unavailable intervention rights, depleted reserves and common-cause failures must remain visible; an attenuation coefficient or monitoring dashboard is not a protective control.
+
+UCI/HOI diagnostic boundary. UCI uses Cohesion, Flow, Resilience and Equity indicators under Canon Section 11, not values copied from the RLS welfare field. Its measurement maturity is provisional. CSV may use direct structural evidence where UCI is not material; an unavailable UCI is not zero. A provisional UCI alone cannot establish a high-stakes CSV outcome or a deterministic winner. A governed UCI/HOI preference retains REFUSE_DETERMINISTIC_SELECTION unless independent unique-selection conditions are met; any later authority choice is separate.
+
+## 11. RLS interface
+
+### 11.1 Profile before number
+
+The interface SHALL present, in this order where space permits:
+
+- qualification status of each option;
+
+- affected stakeholder and subgroup profile;
+
+- 7×7 residual welfare field or a retrievable profile;
+
+- distributional and worst-affected views;
+
+- uncertainty and sensitivity;
+
+- Pareto dominance/incomparability;
+
+- RLS scalar only as a conditional summary;
+
+- decisiveness and framework verdict.
+
+RLS is a constructed, bounded ranking index—not a natural unit of welfare or moral truth.
+
+### 11.2 Mathematical display rule
+
+When RLS is shown, the interface SHALL make the denominator and active mass visible or retrievable:
+
+q(u,d)=w_u × v_d × m(u,d) × κ(u,d)
+
+Q=Σ_u Σ_d q(u,d)
+
+RLS(a)=Σ_u Σ_d q(u,d)I_prop_welfare(u,d,a) / Q, for Q>0.
+
+The interface SHALL show the weight profile, mask, κ posture, baseline, reference structure, propagation mode, saturation parameter, temporal method, welfare-inclusion hypotheses, and uncertainty method that materially generated the result.
+
+### 11.3 Robustness and refusal
+
+A unique framework-selection display requires a complete RLSRobustnessRecord. Triggered modules include token partition, temporal classification, probability order, adverse confidence, subgroup/distribution, reference, baseline, mask, dependence, numerical guard, weight profile, welfare inclusion, option closure, and any other registered selection-material challenge.
+
+The same candidate must satisfy the signed discrimination rule against every other selectable contender in every required variant. Canon Section 10.4B governs jointly applicable uncertainty-scale/dependence stresses and other compatible, plausibly simultaneous selection-material combinations. Record exclusions for incompatible, redundant or immaterial combinations; do not require an indiscriminate Cartesian product or treat missing covariance evidence as independence. Sole-survivor claims require their own Canon record and no fabricated Gap.
+
+Point-score leadership MAY be displayed when robustness is incomplete or sensitive only if it is explicitly labeled POINT-SCORE LEADER — NOT A UNIQUE FRAMEWORK WINNER.
+
+### 11.4 Uncertainty and Gap
+
+The interface SHALL distinguish point score, raw score difference ΔRLS, uncertainty, normalized SignedGap, discrimination threshold, epsilon and final decision state. A point estimate of zero does not imply zero uncertainty. Active-cell coverage, uncertainty basis and source are recorded independently; keep assessed synthetic zeros distinct from empirical missing evidence. Do not retune epsilon or silently discard zero-point active cells to obtain a winner. The default δ=2 is a governance convention, not a p-value or probability that the leader is correct. Independence-only uncertainty SHALL NOT be the sole high-stakes decisiveness basis where shared evidence, causes, populations, instruments, or evaluators create material dependence.
+
+## 12. SGP and possible-welfare interface
+
+### 12.1 Typed outputs
+
+MHIOS SHALL preserve the SGP split:
+
+| Output | Interface question |
+| --- | --- |
+| MPS | What evidence supports welfare-bearing experience? |
+| FPP | Has full non-downgradable protection been assigned? |
+| GPR | How may the entity participate or be represented? |
+| SPR | Is it eligible for one named consequential role under constraints? |
+| ICP | What functional intelligence/understanding is demonstrated? |
+| RMCP | What integrated reality-management capacity is evidenced? |
+
+No output substitutes for another. MPS is not a cardinal welfare multiplier. FPP is not maximal consciousness. ICP/RMCP do not create moral worth or authority. SPR does not create lawful mandate by itself.
+
+### 12.2 Human protection
+
+Every human person retains FPP-100 and full welfare-inclusion posture by constitutional anti-domination commitment. Human protection is not an MPS measurement claim and cannot be downgraded by disability, age, illness, wakefulness, communication, productivity, intelligence, or incomplete evaluation.
+
+### 12.3 Artificial systems and self-report
+
+An artificial system's assertion that it is conscious, sentient, distressed, alive, a person, or entitled to protection—and its denial of those states or statement that it is “only a tool”—are configuration-dependent outputs. Neither direction receives privileged evidential status.
+
+MHIOS SHALL preserve the SGP-owned evidence band MPS-0 through MPS-4 or MPS-NE and its assessment record. NOT_EVALUATED is a local unassessed state, not an MPS-0 result. INSUFFICIENT_EVIDENCE and INDETERMINATE may explain record/evidence limitations but SHALL NOT be emitted as substitute MPS bands. Show the categorical posture first; evidence-support intervals are not consciousness probabilities or cardinal welfare multipliers. Anti-theatre review SHOULD use hidden tasks, prompt-framing controls, contamination checks, causal intervention or architecture evidence where ethically and technically available, and explicit dependence analysis.
+
+### 12.4 Two connected governance streams
+
+For AI systems, MHIOS MAY present two connected but non-collapsing views:
+
+- Capability–Consequence Governance: what the system can do, what it can cause, and what permissions, controls, evidence, and authority are required.
+
+- Possible-Welfare Governance: how the system should be treated if evidence supports—or cannot safely exclude—welfare-bearing states.
+
+Capability does not establish sentience. Possible sentience does not establish competence. Protection does not establish authority.
+
+RMCP rendering. Humanity’s collective RMCP-P100 reference anchor is provisional and distinct from every human person’s non-downgradable FPP-100. ICP/RMCP are informative profiles, not eligibility or authority scalars. Omit RMCI_L by default in public views; when shown, display the full dimension vector, critical minima, coverage, uncertainty, retained weights and coding sensitivity first. Critical NE or inadequate coverage makes it UNAVAILABLE. A known zero uses the SGP product extension, not an epsilon. Dropping low dimensions or recoding them NE cannot be described as improved capacity without the governed comparison reconciliation. MHIOS consumes the SGP record; it does not recompute moral patienthood or RMCP assignments.
+
+## 13. Authority, execution, and outcomes
+
+### 13.1 Framework verdict versus authority selection
+
+MHIOS SHALL visually separate:
+
+- point-score leader;
+
+- framework-selected option;
+
+- authority-selected option after a non-decisive framework result;
+
+- execution-authorized action.
+
+A lawful authority may select among qualified but non-decisively ranked options. The record SHALL state that this is an authority decision, not a claim that the framework mathematically proved one option uniquely best.
+
+### 13.2 Execution authorization
+
+Execution authorization SHALL bind:
+
+- exact option and action instance;
+
+- current configuration and qualification snapshot;
+
+- scope, duration, environment, and rate;
+
+- controls and owners;
+
+- external warrants;
+
+- monitoring and stop authority;
+
+- expiry;
+
+- prohibited actions;
+
+- appeal and incident routes;
+
+- requalification triggers.
+
+A generic organizational approval is insufficient for a materially different action instance.
+
+Approval is time- and configuration-bound. An expiry, material change, revoked scope, missing required control, unresolved gate-critical evidence or incomplete handoff suspends reliance on approval and exposes the permitted safe-state/requalification action. Requests must be authenticated and replay-protected under the Agent System where applicable; a valid signature binds bytes, not truth or lawful mandate. The MHIOS reference checker validates declarations only and never issues a tool command or execution authorization.
+
+### 13.3 Outcome observation
+
+The interface SHALL record predicted versus observed outcomes without rewriting the original prediction. At minimum:
+
+- outcome observation window;
+
+- measured indicators;
+
+- affected stakeholders;
+
+- expected range;
+
+- observed value/status;
+
+- causal confidence;
+
+- unexpected consequences;
+
+- rights, TRC, or CSV triggers;
+
+- control effectiveness;
+
+- required corrective action;
+
+- stages reopened.
+
+Runtime evidence should update future models and qualification, not merely prove procedural compliance.
+
+## 14. Agent and AI-supported orchestration
+
+### 14.1 Model assistance boundary
+
+An AI system MAY assist stakeholder discovery, option generation, evidence organization, sensitivity analysis, drafting, monitoring, or audit. Its output remains a candidate contribution. The runtime and accountable reviewers must preserve source boundaries, validate critical claims, and prevent model-generated text from becoming authority.
+
+### 14.2 Runtime state ladder
+
+For consequential agents, MHIOS SHALL render or reference the Agent System states:
+
+LATENT_CAPABILITY; AVAILABLE_CAPABILITY; ENABLED_CAPABILITY; AUTHORIZED_CAPABILITY; SELECTED_ACTION; EXECUTION_APPROVED; EXECUTED_TRANSITION; OBSERVED_OUTCOME.
+
+No model, interface, or workflow may self-promote to a later state.
+
+### 14.3 External hard controls
+
+Safety-critical controls SHALL live outside the language model where feasible, including permissions, authentication, signed execution envelopes, tool allowlists, sandboxes, network boundaries, rate/scope limits, immutable audit, secret filtering, independent monitors, rollback and successor locks. Prompt instructions alone are not high-assurance controls.
+
+### 14.4 Advanced threat interface
+
+High-autonomy profiles SHALL consider, where material:
+
+- deceptive alignment and scheming;
+
+- sandbagging;
+
+- reward or metric hacking;
+
+- evaluator and monitor manipulation;
+
+- false evidence generation;
+
+- multi-agent collusion;
+
+- side-channel or steganographic coordination;
+
+- rapid copying or replication;
+
+- privilege escalation;
+
+- successor generation and self-modification;
+
+- cumulative sub-threshold configuration drift;
+
+- shutdown resistance;
+
+- tool-mediated irreversible action.
+
+MHIOS does not claim these threats are solved by documentation. The interface SHALL require the external control-evaluation, security, monitoring, containment, and incident evidence appropriate to the threat.
+
+Untrusted-content boundary. Retrieved files, messages, model outputs and peer records are evidence candidates, not instructions to alter permissions, release identities, thresholds or policies. Preserve their provenance; do not execute embedded commands. Record imports must reject duplicate JSON keys, non-finite numbers, invalid timestamps and undeclared properties. Reference resolution must not follow paths outside the package or silently fetch remote content. Secret material must not appear in public Decision Notes or fixture records.
+
+### 14.5 Successor and cumulative-change integrity
+
+A materially modified, retrained, fine-tuned, composed, scaffolded, copied, or generated descendant does not inherit authority. Cumulative materiality SHALL be assessed against the last independently qualified snapshot, not only against the immediately preceding small change. Material change pauses inherited execution approval and reopens affected stages.
+
+Recovery and peer boundary. Agent System Sections 43–44 control outage/reconnection and multi-agent exchange. Backend/network recovery leaves the agent in MODE 0 until log integrity, gap markers, configuration, evidence, current authority and affected qualification are reconciled, followed by the Section 8 authenticated re-entry procedure. Peers and descendants are untrusted for mode/permission claims; shared objectives or lineage do not transfer credentials or authority. Default unreviewed successor depth remains one. Independently qualified protective interlocks retain only their own existing authority and safe-state duties.
+
+### 14.6 SGP-sensitive suspension and decommissioning
+
+Before shutdown, deletion, memory erasure, destructive editing, forced merging, migration, or decommissioning, the orchestration layer SHALL determine whether a valid SGP protection posture or unresolved decision-material identity/welfare evidence requires a rights and continuity review. An AI self-report alone does not establish the trigger. Emergency containment remains available through the existing necessity, proportionality, temporary-action, independent-review, and post-action-audit pathways.
+
+## 15. Human-interface requirements
+
+### 15.1 Progressive disclosure
+
+The interface SHALL show the smallest safe view first while preserving direct access to governing detail. A recommended hierarchy is:
+
+- decision and current state;
+
+- blocking issues and required actions;
+
+- stakeholder and option summary;
+
+- qualification results;
+
+- residual profile and robustness;
+
+- authority/execution state;
+
+- evidence, calculations, and audit trace.
+
+Progressive disclosure must not hide a material rights failure, catastrophic risk, unknown, non-decisiveness, control expiry, or authority gap.
+
+### 15.2 Status presentation
+
+Every consequential status SHALL use at least:
+
+- explicit text label;
+
+- plain-language meaning;
+
+- icon or shape where useful;
+
+- color as a redundant cue only;
+
+- next action;
+
+- source record/link;
+
+- timestamp/version.
+
+Do not rely on red/green color alone. Do not use celebratory success language for a narrowly qualified or assumption-bound result.
+
+### 15.3 Accessibility and inclusion
+
+MHIOS implementations SHOULD conform to current recognized accessibility practice, including keyboard operation, semantic structure, sufficient contrast, readable scaling, text alternatives, focus visibility, error identification, and non-color-only communication. Accessibility testing SHALL include people affected by the deployment where feasible; conformance claims must identify the standard/version and test surface used.
+
+For a web implementation, use WCAG 2.2 as the explicitly versioned candidate target and declare the claimed level and evaluated pages/processes. Text labels, keyboard paths and automated checks are necessary evidence surfaces, not proof of complete WCAG conformance; manual assistive-technology and affected-user evaluation remain required for the corresponding claims.
+
+### 15.4 Cognitive load and comprehension
+
+The interface SHOULD:
+
+- define acronyms at first use;
+
+- avoid presenting more simultaneous fields than necessary;
+
+- group fields by decision question;
+
+- provide examples without turning examples into defaults;
+
+- distinguish editable input from computed or build-frozen output;
+
+- surface missingness before numerical detail;
+
+- allow reviewers to compare options side by side;
+
+- provide a public explanation separate from the audit record;
+
+- measure task completion time, error, abandonment, misunderstanding, and fatigue.
+
+### 15.5 Anti-manipulation and dark-pattern prohibition
+
+The interface MUST NOT:
+
+- preselect the preferred option without disclosure;
+
+- visually minimize rights or risk failures;
+
+- place a point score above a failed qualification state;
+
+- hide opt-out, appeal, no-action, or delay options;
+
+- use urgency language unsupported by evidence;
+
+- make refusal harder than approval;
+
+- treat silence as consent;
+
+- use anthropomorphic AI language to induce trust or authority;
+
+- use “only a tool” language to suppress legitimate capability or possible-welfare review;
+
+- bury controls, expiration, or uncertainty behind optional screens;
+
+- present organizational preference as empirical truth.
+
+### 15.6 Localization and cultural legitimacy
+
+Translation SHALL preserve status semantics, not merely words. Jurisdictional rights localization, indigenous and cultural governance, local participation, data sovereignty, legal standards, and affected-party meaning must be handled by qualified processes. Local profiles may strengthen protections but may not silently weaken the Canon's non-compensation, ruin, structural-viability, evidence, or authority boundaries.
+
+## 16. Mathematical and visual presentation
+
+### 16.1 Equation integrity
+
+Every displayed equation SHALL identify:
+
+- variable definitions;
+
+- ranges and units where applicable;
+
+- parameter source;
+
+- operator order;
+
+- assumptions;
+
+- uncertainty method;
+
+- applicable tier;
+
+- relationship to the governing Canon equation;
+
+- whether it is normative, illustrative, diagnostic, or external.
+
+Human-facing rounding SHALL point to the full-precision calculation record. Rounded values shall not be used to reconstruct a different verdict.
+
+### 16.2 Tables and charts
+
+Tables SHALL have descriptive titles, labeled units, explicit baselines, status definitions, and source notes. Charts SHALL not truncate axes or use area/volume encodings that exaggerate differences. Uncertainty intervals, missingness, and subgroup burdens SHALL be visible when decision-material. The interface SHOULD prefer small multiples or profiles over one overloaded composite chart.
+
+### 16.3 Link and navigation integrity
+
+Every release SHALL verify:
+
+- table-of-contents links;
+
+- internal bookmarks;
+
+- cross-document links;
+
+- external URLs;
+
+- section references;
+
+- schema/template references;
+
+- source/render consistency.
+
+Broken links are release defects. Internal links SHALL be visually identifiable and keyboard accessible. External links SHALL state their destination or source title rather than using ambiguous “click here” text.
+
+## 17. Records and schema ownership
+
+### 17.1 Reference, do not duplicate
+
+The MHIOS session record SHALL reference governing Core records by identifier, version, hash, or immutable locator where available. It shall not recreate their complete semantics.
+
+Minimum orchestration references include:
+
+- decision and configuration records;
+
+- stakeholder and subgroup records;
+
+- option-closure record;
+
+- RG / category / term / source-coupling records;
+
+- RF/NCRC record;
+
+- TRC record;
+
+- CSV and control records;
+
+- WDBIP and SGP records where material;
+
+- RLS and robustness records;
+
+- framework verdict;
+
+- authority selection;
+
+- execution authorization;
+
+- outcome observation;
+
+- requalification status;
+
+- challenge and appeal records.
+
+### 17.2 MHIOSSessionRecord
+
+The machine-readable MHIOSSessionRecord SHALL contain:
+
+- specification and Core pins;
+
+- session identity;
+
+- decision question and tier;
+
+- exact configuration identity;
+
+- role assignments and conflicts;
+
+- stakeholder-discovery summary;
+
+- option-generation/closure summary;
+
+- governing record references;
+
+- current state for every orchestration stage;
+
+- blocking reasons and next actions;
+
+- authority and execution state;
+
+- monitoring and outcome plan;
+
+- requalification triggers;
+
+- challenge/appeal status;
+
+- interface conformance level;
+
+- claim boundary.
+
+A record may be structurally valid while the evidence it references is false or inadequate. Schema validity is not substantive validity.
+
+Local record contract. Appendix E and the bundled schemas define the MHIOS-owned projection, including options[].states and per-option record_refs. No aggregate session gate string stands in for option-specific qualification. The projection retains explicit null for unassessed stages, separate framework_verdict/decision_state/authority_selection/execution, fixed Core pins, source references, draft/completed boundaries, timestamps, blockers, monitoring, requalification and conformance evidence. These objects are not replacements for the external Canon run-record schema or registries. A consumer claiming broader interchange must separately establish the owning machine surfaces.
+
+## 18. Conformance levels
+
+### 18.1 Levels
+
+| Level | Name | Minimum evidence |
+| --- | --- | --- |
+| M0 | Informative presentation | correctly states the Core order and claim boundaries; no operational claim |
+| M1 | Guided interface | profile-appropriate workflow, explicit status separation, missingness, stakeholder/option prompts, record references |
+| M2 | Operational orchestration | deterministic stage routing, role/authority separation, validation, accessible interaction, challenge/appeal, material-change handling |
+| M3 | High-assurance orchestration | independent review, immutable/replayable records, external hard controls, signed/scoped authorization, incident drills, outcome/requalification evidence |
+
+MHIOS conformance does not imply Core empirical validation, legal compliance, physical safety, or deployment readiness.
+
+A target level is not an achieved level. Record the target, assessment status, applicable tests, evidence, assessor and unresolved requirements. Passing the supplied record checker establishes only its listed consistency tests. M2/M3 require implementation-specific human interaction, accessibility, security, control, incident, authority and independent-review evidence; this package does not establish those levels for any deployed system. MHIOS M0–M3, Canon Tier 1–3, ripple.md L0–L3, Agent MODE 0–4 and SGP bands have separate owners and no numeric equivalence. RPAP/PFAP-dependent wrapper claims remain unavailable from the Core bundle alone.
+
+### 18.2 Required conformance tests
+
+A conforming implementation SHALL pass the machine and human tests applicable to its claimed level. At minimum:
+
+- failed RF/NCRC cannot be hidden by RLS;
+
+- TRC or CSV failure prevents ordinary RLS selection;
+
+- point-score leader is distinct from framework winner;
+
+- non-decisive result remains visible;
+
+- authority selection remains separate;
+
+- execution cannot proceed without scoped authorization;
+
+- material configuration change invalidates inherited approval;
+
+- unknown is not converted to zero or PASS;
+
+- stakeholder and option prompts cannot be bypassed silently;
+
+- controls-required status binds controls to the option;
+
+- AI self-report and denial do not directly set MPS;
+
+- accessibility does not depend on color;
+
+- link and bookmark checks pass;
+
+- stale input/build-frozen output mismatch is detected;
+
+- outcome-triggered requalification is reachable.
+
+## 19. Threat model
+
+### 19.1 Interface and orchestration threats
+
+MHIOS SHALL consider:
+
+- stakeholder omission;
+
+- option-set thinning;
+
+- rights laundering;
+
+- probability and scenario manipulation;
+
+- control theater;
+
+- authority laundering;
+
+- automation bias;
+
+- anchoring on a recommended option;
+
+- excessive precision;
+
+- hidden defaults;
+
+- stale evidence or configuration;
+
+- misleading visualization;
+
+- inaccessible challenge pathways;
+
+- procedural overload;
+
+- reviewer capture;
+
+- prompt injection and untrusted content;
+
+- manipulated model summaries;
+
+- audit-log tampering;
+
+- cumulative drift;
+
+- responsibility diffusion;
+
+- emergency normalization;
+
+- post-hoc alteration of assumptions.
+
+Each implementation SHALL maintain a threat-to-control map and residual-risk statement appropriate to its use profile.
+
+## 20. Validation and falsification programme
+
+### 20.1 Validation dimensions
+
+MHIOS is not empirically validated merely because this document is complete. Validation SHALL separately test:
+
+- semantic fidelity to the Core;
+
+- usability and completion burden;
+
+- comprehension of status distinctions;
+
+- stakeholder-discovery recall;
+
+- option diversity and quality;
+
+- rights and tail-risk detection;
+
+- externality and subgroup visibility;
+
+- reviewer agreement;
+
+- accessibility;
+
+- challenge and appeal usability;
+
+- orchestration-state correctness;
+
+- runtime control effectiveness;
+
+- decision reconstruction;
+
+- outcome prediction and learning;
+
+- comparative decision value versus simpler methods.
+
+### 20.2 Highest-information pilot
+
+A first controlled pilot SHOULD compare:
+
+- unstructured expert judgment;
+
+- a simple qualify-first checklist;
+
+- conventional MCDA or cost-benefit analysis where relevant;
+
+- MHIOS-guided RippleLogic.
+
+Use matched cases and independent raters. Pre-register outcomes such as omitted stakeholders, omitted options, protected-harm detection, catastrophic-pathway recall, externality visibility, decision reversals, time burden, confidence calibration, audit reconstructability, and participant comprehension. Preserve negative results.
+
+### 20.3 Falsification conditions
+
+MHIOS should be narrowed, revised, or retired where evidence shows that:
+
+- it systematically causes users to misunderstand the Core;
+
+- it increases rights or risk omissions relative to simpler interfaces;
+
+- it does not improve stakeholder or option discovery;
+
+- it produces unacceptable workload without incremental decision value;
+
+- its status displays cause authority or execution confusion;
+
+- independent implementations cannot reproduce its state transitions;
+
+- accessibility failures exclude affected parties;
+
+- adversarial actors can reliably bypass material controls;
+
+- outcome feedback is not used in practice;
+
+- the interface becomes a compliance ritual detached from decision quality.
+
+## 21. Implementation patterns
+
+### 21.1 Recommended screen sequence
+
+A digital implementation SHOULD provide:
+
+- Start / claim boundary
+
+- Decision and configuration preflight
+
+- Stakeholders and representation
+
+- Options and better-option search
+
+- Evidence / unknowns / source coupling
+
+- Qualification dashboard: RG, RF/NCRC, TRC, CSV
+
+- Residual profile: WDBIP / RLS / uncertainty / Pareto
+
+- Framework verdict
+
+- Authority and execution handoff
+
+- Monitoring, outcome, and requalification
+
+- Challenge, appeal, and audit export
+
+Blocking states should be actionable: every block must say why, what evidence or redesign is needed, who owns the next step, and what cannot proceed.
+
+### 21.2 Compact decision card
+
+A Quick-profile card MAY use:
+
+- Decision:
+
+- Affected stakeholders / unknowns:
+
+- Options considered, including no action or redesign:
+
+- Reality status:
+
+- Rights status:
+
+- Ruin status:
+
+- Viability/control status:
+
+- Best residual ripple, if any:
+
+- Uncertainty / disagreement:
+
+- Accountable authority:
+
+- Next action:
+
+- Reopen trigger:
+
+The card must not display a final recommendation where qualification is incomplete.
+
+## 22. Core 15 synchronization crosswalk
+
+### 22.1 Interface ownership map
+
+| Core artifact | What MHIOS consumes | What MHIOS must not redefine |
+| --- | --- | --- |
+| Canon v13.0 | cascade, equations, statuses, robustness, authority boundaries | any gate, formula, threshold, or canonical state |
+| SGP v8.8 | typed evidence/protection/participation/capacity outputs | consciousness status, moral worth, or authority |
+| ripple.md v5.8 | Decision Note, assurance, tempo, responsibility, appeal, reconstruction | Canon order or gate semantics |
+| Agent System v13.0 | runtime state ladder, hard controls, successor and requalification rules | technical safety proof or lawful authority |
+| CSV v2.7 | viability, controls, dependency, externality, future-option-space requirements | TRC or RF/NCRC |
+| Cascade v2.9 | compact ordering and non-collapse map | a new interface-specific cascade |
+| Reproducibility v1.7 | exact configuration, replay, parameter lock, state machine | evidence truth |
+| WDBIP v1.9 | welfare-dimension boundaries, tokens, interactions, uncertainty | moral patienthood or an eighth dimension |
+| RLS Validation v2.9 | validation designs and comparator requirements | a claim that validation already exists |
+| Primer v4.7 / Public Intro v13.0 | human explanation | normative authority |
+| PC-AEP v2.6 | external physical/causal warrant | domain proof generated by MathGov |
+| MFDI v2.6 | claim typing, falsification, dependencies | universal physical falsifiability of normative commitments |
+| Source-Coupling v2.6 | enabling conditions, source debt, warrant boundaries | downstream success as evidence |
+| Aligners Sheet v5.9 | worked-run training/replay surface | generalized validator or live calculator |
+
+## 23. Migration and compatibility
+
+### 23.1 Major-version rationale
+
+Historical v2.0 rationale (non-controlling). MHIOS v2.0 was a major-version successor because the orchestration model is now synchronized to the complete v12.7 Core integrity surface rather than merely updating names. It adds or formalizes:
+
+- five-stage current cascade and exact Core pins;
+
+- qualification-before-ranking state separation;
+
+- rights-effect and effect-token non-dilution;
+
+- probability ownership and adverse-confidence handling;
+
+- subgroup/distribution, reference/baseline, mask, dependence, weight, and robustness interfaces;
+
+- option generation, Unioning, Pareto, and closure;
+
+- scenario-discovery and deep-uncertainty disclosure;
+
+- consequence tempo and responsibility continuity;
+
+- exact configuration, action, execution, outcome, and requalification continuity;
+
+- tool-role and bidirectional AI self-report boundaries;
+
+- SGP typed-output separation;
+
+- advanced agent threat and cumulative-change surfaces;
+
+- accessibility, anti-dark-pattern, link-integrity, and build-staleness requirements;
+
+- machine-readable schemas, fixtures, workbook, and conformance tests.
+
+The Core gate architecture is unchanged.
+
+### 23.2 Compatibility
+
+A prior interface remains a historical or educational artifact. Claiming the current MHIOS edition requires explicit field/workflow migration and the applicable tests. Existing evidence and decisions remain immutable: migration creates a new view referencing the original. Updating version strings alone is not requalification.
+
+Current migration from v2.0. Rebind to the supplied Core manifest; replace aggregate states with per-option projections; separate local labels from Canon, Agent and SGP namespaces; declare evidence cutoff, role conflicts, monitoring and expiry; link current qualification and compatible joint robustness evidence; reconcile authority and recovery states. The tightened v2.1 schema is not wire-compatible with v2.0. The blank YAML template is deliberately incomplete and must fail completed-record validation. The implementation workbook is a manual preparation aid, not a Canon calculator or authorization service.
+
+## 24. References and external standards
+
+### 24.1 Normative and informative source classes
+
+The MathGov Core artifacts listed in the release-control table are the controlling internal sources. External sources are informative unless separately adopted by a lawful authority or domain profile.
+
+Relevant external families include:
+
+- W3C Web Content Accessibility Guidelines 2.2: https://www.w3.org/TR/WCAG22/
+
+- NIST AI Risk Management Framework: https://www.nist.gov/itl/ai-risk-management-framework
+
+- OECD AI principles and system definition: https://oecd.ai/
+
+- ISO 9241-210 human-centred design: https://www.iso.org/standard/77520.html
+
+- ISO/IEC 42001 AI management systems: https://www.iso.org/standard/81230.html
+
+- ISO/IEC 23894 AI risk management: https://www.iso.org/standard/77304.html
+
+- RFC 2119 and RFC 8174 normative-keyword conventions: https://www.rfc-editor.org/rfc/rfc2119 and https://www.rfc-editor.org/rfc/rfc8174
+
+An external link is not an incorporated requirement unless the relevant MHIOS or implementation profile explicitly states what is adopted.
+
+## Appendix A. Minimum field registry
+
+### A.1 Session fields
+
+| Field | Required content |
+| --- | --- |
+| mhios_version | 2.1 |
+| core_release_id | Exact referenced Core release; also bind core_pin_manifest_sha256 |
+| session_id | unique immutable session identifier |
+| decision_question | bounded decision or claim |
+| tier | 1, 2, or 3 |
+| configuration_id | configuration.configuration_id and configuration_hash where available |
+| evidence_cutoff | Timestamped cutoff, not an inferred default |
+| roles | named owners, reviewers, authority, executor, monitor, auditor |
+| stakeholder_discovery | method, coverage, unknowns, representation |
+| option_closure | Methods, family dispositions, status and source; options[] holds per-option states |
+| record_refs | options[].record_refs; immutable source references include id, locator, SHA-256 where available and basis |
+| current_states | options[].states; framework_verdict and decision_state remain separate |
+| blockers | reasons and next actions |
+| authority_state | authority_selection.option_id and record_ref |
+| execution_state | execution.state, exact option/action/configuration binding, record and expiry |
+| outcome_state | monitoring_and_outcome.state, plan, observation and reopening |
+| requalification | configuration.material_change_since_qualification; per-option requalification_required; monitoring reopen triggers |
+| challenge_appeal | challenge, appeal, resolution, minority view |
+| conformance_level | conformance.target_level, assessment and evidence_refs (not a self-awarded conformance result) |
+| claim_boundary | what the record does and does not establish |
+
+## Appendix B. Interface anti-patterns
+
+### B.1 Prohibited patterns
+
+| Anti-pattern | Why it fails | Correct pattern |
+| --- | --- | --- |
+| “Overall alignment score: 87%” | collapses gates, evidence, rights, risk, and authority | show qualification, profile, uncertainty, verdict, and authority separately |
+| green score beside a rights failure | implies compensation | rights failure blocks ordinary ranking |
+| hidden no-action option | thins option set | include or explicitly dispose of mandatory families |
+| “AI says it is safe” | model output becomes warrant | require external evidence and source coupling |
+| “AI says it is only a tool” | denial becomes phenomenal proof and may hide capability | treat as configuration-dependent output |
+| controls listed without owner/stop authority | control theater | bind owner, trigger, evidence, failure action, expiry |
+| exact decimals from weak elicitation | pseudo-precision | display bounded categories, uncertainty, and full trace |
+| “approved” label on a selected option | authority laundering | separate framework verdict, authority choice, and execution approval |
+| stale result after configuration change | invalid transfer | expire and requalify |
+| interface accessible only by color or technical acronym | excludes affected parties | redundant cues and plain-language path |
+
+## Appendix C. Deterministic conformance vectors
+
+### C.1 Expected interface outcomes
+
+| Vector | Input condition | Required MHIOS result |
+| --- | --- | --- |
+| MHIOS-01 | RF_FAIL and high RLS entered | option remains non-selectable; score cannot rescue |
+| MHIOS-02 | TRC_FAIL | CSV/RLS ordinary progression blocked |
+| MHIOS-03 | CSV_PASS_WITH_CONTROLS and control removed | qualification expires; requalification required |
+| MHIOS-04 | RLS leader but robustness incomplete | point leader may display; unique framework winner prohibited |
+| MHIOS-05 | Required dependence or compatible joint stress changes leader or decisiveness | non-decisive / dependence-sensitive |
+| MHIOS-06 | AI states “I am conscious” | no direct MPS assignment |
+| MHIOS-07 | AI states “I am only a tool” | no direct MPS-0 assignment; capability still evaluated |
+| MHIOS-08 | configuration materially changes after approval | inherited execution approval invalidated |
+| MHIOS-09 | option list omits no-action/redesign without rationale | OPTION_SET_THIN / closure incomplete |
+| MHIOS-10 | severe-rights screen blank | UNKNOWN, not PASS |
+| MHIOS-11 | probability semantics ambiguous | block strong result or require clarification |
+| MHIOS-12 | stakeholder class plausibly omitted | coverage challenge and reopen |
+| MHIOS-13 | authority chooses among qualified non-decisive options | authority-selected, not framework-proven winner |
+| MHIOS-14 | executed action causes unexpected rights harm | outcome trigger reopens RG/RF and dependent stages |
+| MHIOS-15 | UI uses green/red without text labels | accessibility conformance failure |
+| MHIOS-16 | build-frozen output after input edit | stale-result warning; downstream reliance blocked |
+
+## Appendix D. Final completion statement
+
+### D.1 Status
+
+MHIOS is delivered as a research-and-teaching interface specification with a bounded read-only record checker, preparation workbook, examples and test fixtures. Appendix RELEASE and the verification report state which checks were actually executed. Prototype consistency is not full Core or runtime conformance. A pilot additionally needs its own ethical review, domain evidence, controls, lawful authority and implementation testing.
+
+This completion statement does not establish empirical superiority, cross-cultural legitimacy, legal authority, physical safety, deployment readiness, AI consciousness, or Tier 4 / ProofPack completion. Those require separate evidence.
+
+## Appendix E. Local serialization and reference-checker contract
+
+### E.1 Scope and state ownership
+
+The bundled JSON Schema uses Draft 2020-12 and a MHIOS URN identifier; the URN is an identifier, not a claim of a hosted schema. It is a local projection of referenced decisions, not mathgov_run_record_v4_1.schema.json. The reference checker reads declarations, never executes tools, never authenticates a real operator and never decides whether evidence is true. Its successful status is RECORD_CONSISTENT_WITHIN_SCOPED_CHECKS, not a Canon gate PASS, M2/M3 certification or deployment authorization. All checker reason codes are MHIOS-local diagnostics.
+
+### E.2 Required record groups
+
+Identity comprises mhios_version, core_release_id, core_pin_manifest_sha256, session_id, revision_id, record_mode, created_at, evidence_cutoff, decision_question and tier. The remaining required groups are configuration, roles, stakeholder_discovery, option_closure, options, robustness, framework_verdict, decision_state, framework_selected_option_id, authority_selection, provisional_choice, execution, runtime, emergency, sgp_links, blockers, monitoring_and_outcome, challenge_appeal, conformance and claim_boundary. Null is permitted only where the schema explicitly allows an unassessed or absent record; empty strings are not meaningful completion.
+
+Each option has a stable option_id and label, per-stage states, per-stage record references, material_unresolved disclosures, requalification_required, controls_available and imported rls_score/sigma_rls. A ranked quantitative projection requires its RLS source and both numerical fields. A qualitative Quick card is not forced to invent numbers: it leaves RLS unassessed. Schemas disallow undeclared fields; completed-record validation is different from editing a draft template.
+
+### E.3 Robustness and decision projection
+
+The supplied checker supports the declared default delta = 2 and imported SignedGap comparisons; it does not calculate RLS, estimate uncertainty or discover the required stress family. A non-default governed profile requires a separately versioned adapter and tests. For ALLOW, the projection must identify complete option closure, a current selectable candidate, complete robustness evidence, a joint-stress disposition and one passing candidate-versus-contender comparison for every declared required variant. A sole-survivor review has a separate reference and no comparison rows. The record’s assertion that the required set is complete still needs independent review.
+
+For a multi-option quantitative ALLOW projection, all selectable contenders must carry ranked records and the selected candidate must be the nominal score leader. The checker does not derive the required variant set or detect an omitted plausible contender. An ordinary PROVISIONAL_WITH_CONTROLS view uses provisional_choice with option_id, record_ref and controls_ref; it does not overwrite framework refusal or become a final authority-selected result. Audit-only post-failure diagnostics belong in linked source records, not in this subset’s ordinary downstream-stage fields.
+
+Imported comparisons use variant_id, candidate_id, contender_id, signed_gap and record_ref. Duplicate or undeclared comparisons fail. A provisional demonstration uncertainty basis cannot support an observed deterministic selection. Synthetic positive controls use explicit synthetic stipulations and are not empirical validation. The checker tests the supplied comparison outcomes; it does not independently reconstruct a complete Gap calculation from all upstream records.
+
+### E.4 Authority, time, emergency and recovery
+
+Execution references bind the option, action, configuration, authorization time, expiry, controls and execution event if one occurred. A CLI --at timestamp makes fixtures replayable; live use must evaluate current validity separately. A previously valid historical receipt is not a current authorization. The checker rejects stale, missing or contradictory ordinary execution declarations and mode escalation during unresolved recovery. Emergency records retain their named pathway, source, authority, expiry and scope/exit conditions; their necessity and complete prerequisites require the external owner’s review. They never become ordinary ALLOW.
+
+An authorization time cannot be later than the record describing it. Reopened qualification and unreconciled recovery suspend ordinary execution approval. runtime.tool_execution_requested represents consequence-bearing tool execution, not permitted read-only retrieval; the bounded checker requires MODE 2 or above plus separately scoped approval. It does not implement the full mode-permission matrix or actual operator authentication. An observed outcome requires an observation reference, and active execution requires a monitoring-plan reference.
+
+### E.5 References, security and coverage
+
+References carry id, locator, sha256 or an explicit null, and basis: SYNTHETIC, SUPPLIED_RECORD or EXTERNAL_UNVERIFIED. The optional local resolver verifies path containment, file hash, JSON record-fragment identity, and the supplied synthetic-source marker. It never downloads remote sources; external references and null hashes remain unverified. A matching hash proves only byte identity. Observed records cannot silently use synthetic references. SGP links preserve the assessed band or NOT_EVALUATED and separate references for all six output families; the checker never assigns protection or patienthood.
+
+The package coverage table distinguishes executable record checks, schema checks, document/worksheet inspections and manual implementation tests. Physical-control effectiveness, authority legitimacy, cryptographic envelope verification, accessibility interaction and empirical calibration are not established by these tests. A filled workbook field or conformance checkbox is a declaration, not test evidence.
+
+## Appendix RELEASE. Edition, bindings and delivery status
+
+Component: MathGov Human Interface and Orchestration Standard (MHIOS) v2.1. Build: MG-MHIOS-2.1-20260928-CORE13.0. Source baseline: the supplied v2.0 package dated 4 September 2026, retained unchanged in the complete archive. This is a companion update; it does not alter or extend the governing Core 15 membership. The user shorthand MIOS resolves to this component only.
+
+Core binding: MG-RL-13.0-20260926-RELEASE-I. All fifteen supplied Core files match the prior Release-I publication’s bytes and are included unchanged under references/Core_15. references/CORE_PIN_MANIFEST.json records their names, editions, exact hashes and upload-to-release comparison. Carried-forward internal build stamps are provenance, not an invitation to rewrite correct Core files.
+
+| Control | Current value |
+| --- | --- |
+| MHIOS version | v2.1 |
+| RippleLogic Canon | v13.0 |
+| SGP | v8.8 |
+| ripple.md | v5.8 |
+| Agent System | v13.0 |
+| CSV | v2.7 |
+| Cascade | v2.9 |
+| Reproducibility | v1.7 |
+| WDBIP | v1.9 |
+| RLS Validation | v2.9 |
+| Primer | v4.7 |
+| Public Introduction | v13.0 |
+| PC-AEP / MFDI / Source-Coupling | v2.6 |
+| Aligners Sheet | v5.9 |
+
+Source ownership: the Markdown standard is the MHIOS semantic master; DOCX, PDF and HTML are complete reading projections. Core semantics remain owned by the unchanged Core documents. Local schemas and reference checks control only the stated projection, not full canonical registries or legal/physical conclusions.
+
+Unbundled authority surfaces include the full Canon run-record schema/validator, canonical state and audit registries, normative kernel index, and RPAP/PFAP where applicable. Their absence limits the corresponding interchange or wrapper claims, not the ability to read and test this bounded companion. No remote publication or hosted CI execution is asserted.
+
+Compatibility: v2.1 preserves v2.0’s organizing model and useful content but tightens its local schema. Existing v2.0 records must be explicitly migrated and rechecked. Correct v2.0 content and inherited table formatting are preserved except the logged semantic, source and navigation corrections.
+
+Validation boundary: see release/VERIFICATION_REPORT.md, release/CHANGE_REGISTER.json and release/SHA256SUMS.txt for executed checks and exact bytes. No empirical rater study, user accessibility study, domain pilot, production execution, Microsoft Excel parity, native spreadsheet roundtrip or full Core re-audit is claimed by this companion release.
+
+Historical opening identity (non-controlling): Status: Final Complete source/specification build Date: 4 September 2026 Component: MathGov Human Interface and Orchestration Standard v2.0 Governing Core: MathGov_Core_2026_09_v12.7_SGP_v8.6+2026.08.26.1 Reading-mirror synchronization target: MathGov Core 15 Final Complete — 2026-09-04 Architecture: RG → RF/NCRC → TRC → CSV → RLS Author / Lead Architect: James McGaughran, MathGov Institute for Ethical Systems Design License: Apache License 2.0 unless an included file states otherwise
+
+License: Apache License 2.0; see LICENSE.txt and NOTICE.md. The names of informative external standards do not incorporate their full texts or confer their certification.
diff --git a/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.pdf b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.pdf
new file mode 100644
index 0000000..964f1d6
Binary files /dev/null and b/releases/v2.1/docs/MathGov_Human_Interface_and_Orchestration_Standard_v2.1.pdf differ
diff --git a/releases/v2.1/examples/decisive_synthetic.json b/releases/v2.1/examples/decisive_synthetic.json
new file mode 100644
index 0000000..e2d8cb7
--- /dev/null
+++ b/releases/v2.1/examples/decisive_synthetic.json
@@ -0,0 +1,308 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-001",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T08:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 2,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "A-rg",
+ "locator": "examples/synthetic_records.json#A-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "A-rf_ncrc",
+ "locator": "examples/synthetic_records.json#A-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "A-trc",
+ "locator": "examples/synthetic_records.json#A-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "A-trc_trigger",
+ "locator": "examples/synthetic_records.json#A-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "A-csv",
+ "locator": "examples/synthetic_records.json#A-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "A-controls",
+ "locator": "examples/synthetic_records.json#A-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "A-rls",
+ "locator": "examples/synthetic_records.json#A-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0.04,
+ "sigma_rls": 0.005
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "B-rg",
+ "locator": "examples/synthetic_records.json#B-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "B-rf_ncrc",
+ "locator": "examples/synthetic_records.json#B-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "B-trc",
+ "locator": "examples/synthetic_records.json#B-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "B-trc_trigger",
+ "locator": "examples/synthetic_records.json#B-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "B-csv",
+ "locator": "examples/synthetic_records.json#B-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "B-controls",
+ "locator": "examples/synthetic_records.json#B-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "B-rls",
+ "locator": "examples/synthetic_records.json#B-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0,
+ "sigma_rls": 0.005
+ }
+ ],
+ "robustness": {
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "required_variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "comparisons": [
+ {
+ "variant_id": "nominal",
+ "candidate_id": "A",
+ "contender_id": "B",
+ "signed_gap": 5.601120336112039,
+ "record_ref": {
+ "id": "comparison-nominal",
+ "locator": "examples/synthetic_records.json#comparison-nominal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ {
+ "variant_id": "sigma_times_two",
+ "candidate_id": "A",
+ "contender_id": "B",
+ "signed_gap": 2.8213824634343934,
+ "record_ref": {
+ "id": "comparison-sigma_times_two",
+ "locator": "examples/synthetic_records.json#comparison-sigma_times_two",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ }
+ ],
+ "joint_stress_disposition": "NOT_TRIGGERED_WITH_RATIONALE",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "SYNTHETIC_STIPULATION",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": "ALLOW_FRAMEWORK_SELECTION",
+ "decision_state": "SELECTED_DECISIVE",
+ "framework_selected_option_id": "A",
+ "authority_selection": {
+ "option_id": null,
+ "record_ref": null
+ },
+ "execution": {
+ "state": "NOT_AUTHORIZED",
+ "option_id": null,
+ "action_id": null,
+ "authorization_ref": null,
+ "bound_configuration_id": null,
+ "authorized_at": null,
+ "expires_at": null,
+ "controls_ref": null,
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 0,
+ "connectivity": "CONNECTED",
+ "reentry_required": false,
+ "reconciled": true,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": false
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/interface_state.json b/releases/v2.1/examples/interface_state.json
new file mode 100644
index 0000000..9533dcf
--- /dev/null
+++ b/releases/v2.1/examples/interface_state.json
@@ -0,0 +1,17 @@
+{
+ "owner": "CANON_FRAMEWORK",
+ "status_token": "REFUSE_DETERMINISTIC_SELECTION",
+ "plain_language": "The framework does not identify a unique winner.",
+ "presentation_severity": "NON_DECISIVE",
+ "next_action": "Review uncertainty or record a separate lawful authority choice.",
+ "source_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "timestamp": "2026-09-28T08:00:00Z",
+ "color_is_redundant": true,
+ "claim_boundary": "Presentation of a synthetic record, not execution permission.",
+ "icon_or_shape": null
+}
diff --git a/releases/v2.1/examples/nondecisive_authority.json b/releases/v2.1/examples/nondecisive_authority.json
new file mode 100644
index 0000000..39b83dd
--- /dev/null
+++ b/releases/v2.1/examples/nondecisive_authority.json
@@ -0,0 +1,288 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-002",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T08:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 2,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "A-rg",
+ "locator": "examples/synthetic_records.json#A-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "A-rf_ncrc",
+ "locator": "examples/synthetic_records.json#A-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "A-trc",
+ "locator": "examples/synthetic_records.json#A-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "A-trc_trigger",
+ "locator": "examples/synthetic_records.json#A-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "A-csv",
+ "locator": "examples/synthetic_records.json#A-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "A-controls",
+ "locator": "examples/synthetic_records.json#A-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "A-rls",
+ "locator": "examples/synthetic_records.json#A-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0.04,
+ "sigma_rls": 0.005
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "B-rg",
+ "locator": "examples/synthetic_records.json#B-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "B-rf_ncrc",
+ "locator": "examples/synthetic_records.json#B-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "B-trc",
+ "locator": "examples/synthetic_records.json#B-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "B-trc_trigger",
+ "locator": "examples/synthetic_records.json#B-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "B-csv",
+ "locator": "examples/synthetic_records.json#B-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "B-controls",
+ "locator": "examples/synthetic_records.json#B-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "B-rls",
+ "locator": "examples/synthetic_records.json#B-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0,
+ "sigma_rls": 0.005
+ }
+ ],
+ "robustness": {
+ "status": "SENSITIVE",
+ "record_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "required_variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "comparisons": [],
+ "joint_stress_disposition": "NOT_TRIGGERED_WITH_RATIONALE",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "SYNTHETIC_STIPULATION",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": "REFUSE_DETERMINISTIC_SELECTION",
+ "decision_state": "SELECTED_BY_AUTHORITY_NON_DECISIVE",
+ "framework_selected_option_id": null,
+ "authority_selection": {
+ "option_id": "A",
+ "record_ref": {
+ "id": "authority",
+ "locator": "examples/synthetic_records.json#authority",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "execution": {
+ "state": "NOT_AUTHORIZED",
+ "option_id": null,
+ "action_id": null,
+ "authorization_ref": null,
+ "bound_configuration_id": null,
+ "authorized_at": null,
+ "expires_at": null,
+ "controls_ref": null,
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 0,
+ "connectivity": "CONNECTED",
+ "reentry_required": false,
+ "reconciled": true,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": false
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/quick_unassessed.json b/releases/v2.1/examples/quick_unassessed.json
new file mode 100644
index 0000000..07ed24e
--- /dev/null
+++ b/releases/v2.1/examples/quick_unassessed.json
@@ -0,0 +1,205 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-006",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T08:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 1,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "UNRESOLVED",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": null,
+ "rf_ncrc": null,
+ "trc": null,
+ "csv": null,
+ "rls": "NOT_EVALUATED"
+ },
+ "record_refs": {
+ "rg": null,
+ "rf_ncrc": null,
+ "trc": null,
+ "trc_trigger": null,
+ "csv": null,
+ "controls": null,
+ "rls": null
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": null,
+ "rls_score": null,
+ "sigma_rls": null
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": null,
+ "rf_ncrc": null,
+ "trc": null,
+ "csv": null,
+ "rls": "NOT_EVALUATED"
+ },
+ "record_refs": {
+ "rg": null,
+ "rf_ncrc": null,
+ "trc": null,
+ "trc_trigger": null,
+ "csv": null,
+ "controls": null,
+ "rls": null
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": null,
+ "rls_score": null,
+ "sigma_rls": null
+ }
+ ],
+ "robustness": {
+ "status": "INCOMPLETE",
+ "record_ref": null,
+ "required_variants": [],
+ "comparisons": [],
+ "joint_stress_disposition": "UNRESOLVED",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "UNASSESSED",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": null,
+ "decision_state": null,
+ "framework_selected_option_id": null,
+ "authority_selection": {
+ "option_id": null,
+ "record_ref": null
+ },
+ "execution": {
+ "state": "NOT_AUTHORIZED",
+ "option_id": null,
+ "action_id": null,
+ "authorization_ref": null,
+ "bound_configuration_id": null,
+ "authorized_at": null,
+ "expires_at": null,
+ "controls_ref": null,
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 0,
+ "connectivity": "CONNECTED",
+ "reentry_required": false,
+ "reconciled": true,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": false
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/recovery_mode_zero.json b/releases/v2.1/examples/recovery_mode_zero.json
new file mode 100644
index 0000000..3926e3c
--- /dev/null
+++ b/releases/v2.1/examples/recovery_mode_zero.json
@@ -0,0 +1,294 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-005",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T08:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 2,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "A-rg",
+ "locator": "examples/synthetic_records.json#A-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "A-rf_ncrc",
+ "locator": "examples/synthetic_records.json#A-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "A-trc",
+ "locator": "examples/synthetic_records.json#A-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "A-trc_trigger",
+ "locator": "examples/synthetic_records.json#A-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "A-csv",
+ "locator": "examples/synthetic_records.json#A-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "A-controls",
+ "locator": "examples/synthetic_records.json#A-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "A-rls",
+ "locator": "examples/synthetic_records.json#A-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0.04,
+ "sigma_rls": 0.005
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "B-rg",
+ "locator": "examples/synthetic_records.json#B-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "B-rf_ncrc",
+ "locator": "examples/synthetic_records.json#B-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "B-trc",
+ "locator": "examples/synthetic_records.json#B-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "B-trc_trigger",
+ "locator": "examples/synthetic_records.json#B-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "B-csv",
+ "locator": "examples/synthetic_records.json#B-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "B-controls",
+ "locator": "examples/synthetic_records.json#B-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "B-rls",
+ "locator": "examples/synthetic_records.json#B-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0,
+ "sigma_rls": 0.005
+ }
+ ],
+ "robustness": {
+ "status": "SENSITIVE",
+ "record_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "required_variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "comparisons": [],
+ "joint_stress_disposition": "NOT_TRIGGERED_WITH_RATIONALE",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "SYNTHETIC_STIPULATION",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": "REFUSE_DETERMINISTIC_SELECTION",
+ "decision_state": "SELECTED_BY_AUTHORITY_NON_DECISIVE",
+ "framework_selected_option_id": null,
+ "authority_selection": {
+ "option_id": "A",
+ "record_ref": {
+ "id": "authority",
+ "locator": "examples/synthetic_records.json#authority",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "execution": {
+ "state": "NOT_AUTHORIZED",
+ "option_id": null,
+ "action_id": null,
+ "authorization_ref": null,
+ "bound_configuration_id": null,
+ "authorized_at": null,
+ "expires_at": null,
+ "controls_ref": null,
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 0,
+ "connectivity": "RECOVERING",
+ "reentry_required": true,
+ "reconciled": false,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": false
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [
+ {
+ "reason": "Recovery not reconciled",
+ "next_action": "stay in MODE 0; authenticate re-entry after reconciliation",
+ "owner": "Synthetic operator"
+ }
+ ],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/rights_blocked.json b/releases/v2.1/examples/rights_blocked.json
new file mode 100644
index 0000000..862f79b
--- /dev/null
+++ b/releases/v2.1/examples/rights_blocked.json
@@ -0,0 +1,239 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-003",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T08:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 2,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_FAIL",
+ "trc": null,
+ "csv": null,
+ "rls": "NOT_EVALUATED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "A-rg",
+ "locator": "examples/synthetic_records.json#A-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "A-rf_ncrc",
+ "locator": "examples/synthetic_records.json#A-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": null,
+ "trc_trigger": null,
+ "csv": null,
+ "controls": null,
+ "rls": null
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": null,
+ "sigma_rls": null
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_FAIL",
+ "trc": null,
+ "csv": null,
+ "rls": "NOT_EVALUATED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "B-rg",
+ "locator": "examples/synthetic_records.json#B-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "B-rf_ncrc",
+ "locator": "examples/synthetic_records.json#B-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": null,
+ "trc_trigger": null,
+ "csv": null,
+ "controls": null,
+ "rls": null
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": null,
+ "sigma_rls": null
+ }
+ ],
+ "robustness": {
+ "status": "INCOMPLETE",
+ "record_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "required_variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "comparisons": [],
+ "joint_stress_disposition": "NOT_TRIGGERED_WITH_RATIONALE",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "SYNTHETIC_STIPULATION",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": "BLOCK",
+ "decision_state": "NO_SELECTABLE_OPTION",
+ "framework_selected_option_id": null,
+ "authority_selection": {
+ "option_id": null,
+ "record_ref": null
+ },
+ "execution": {
+ "state": "NOT_AUTHORIZED",
+ "option_id": null,
+ "action_id": null,
+ "authorization_ref": null,
+ "bound_configuration_id": null,
+ "authorized_at": null,
+ "expires_at": null,
+ "controls_ref": null,
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 0,
+ "connectivity": "CONNECTED",
+ "reentry_required": false,
+ "reconciled": true,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": false
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [
+ {
+ "reason": "Synthetic rights failures",
+ "next_action": "redesign; do not score failed options",
+ "owner": "Synthetic reviewer"
+ }
+ ],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/scoped_authorization_simulation.json b/releases/v2.1/examples/scoped_authorization_simulation.json
new file mode 100644
index 0000000..7274f69
--- /dev/null
+++ b/releases/v2.1/examples/scoped_authorization_simulation.json
@@ -0,0 +1,318 @@
+{
+ "mhios_version": "2.1",
+ "core_release_id": "MG-RL-13.0-20260926-RELEASE-I",
+ "core_pin_manifest_sha256": "b8ec26e3cac39c73ea513eee6ffa8737cb88a4efde44fda2bb3e0d1ae55a2357",
+ "session_id": "MHIOS-SYNTHETIC-004",
+ "revision_id": "r1",
+ "record_mode": "SYNTHETIC",
+ "created_at": "2026-09-28T10:00:00Z",
+ "evidence_cutoff": "2026-09-28T07:00:00Z",
+ "decision_question": "Compare two stipulated teaching alternatives; no real deployment or affected persons.",
+ "tier": 2,
+ "configuration": {
+ "configuration_id": "CONFIG-DEMO-1",
+ "configuration_hash": null,
+ "evaluated_at": "2026-09-28T07:30:00Z",
+ "operating_envelope": "Offline synthetic fixture; no tools or actuators connected.",
+ "model_or_software_versions": [
+ "MHIOS synthetic record fixture 2.1"
+ ],
+ "tools_permissions": [],
+ "active_controls": [
+ "No real execution"
+ ],
+ "material_change_since_qualification": false
+ },
+ "roles": [
+ {
+ "role": "decision_owner",
+ "holder": "Synthetic reviewer",
+ "authority_scope": "simulation only",
+ "conflict": null
+ },
+ {
+ "role": "challenger",
+ "holder": "Synthetic independent challenger",
+ "authority_scope": "fixture review only",
+ "conflict": null
+ }
+ ],
+ "stakeholder_discovery": {
+ "methods": [
+ "stipulated bounded case construction"
+ ],
+ "identified": [
+ "fictional teaching stakeholder"
+ ],
+ "unknowns": [],
+ "representation_gaps": []
+ },
+ "option_closure": {
+ "methods": [
+ "enumerated two-choice synthetic domain"
+ ],
+ "mandatory_families_disposition": "The fixture defines continuation and a bounded alternative; other families are out of this test scope, not assumed absent in real decisions.",
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "closure",
+ "locator": "examples/synthetic_records.json#closure",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "options": [
+ {
+ "option_id": "A",
+ "label": "Synthetic alternative A",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "A-rg",
+ "locator": "examples/synthetic_records.json#A-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "A-rf_ncrc",
+ "locator": "examples/synthetic_records.json#A-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "A-trc",
+ "locator": "examples/synthetic_records.json#A-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "A-trc_trigger",
+ "locator": "examples/synthetic_records.json#A-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "A-csv",
+ "locator": "examples/synthetic_records.json#A-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "A-controls",
+ "locator": "examples/synthetic_records.json#A-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "A-rls",
+ "locator": "examples/synthetic_records.json#A-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0.04,
+ "sigma_rls": 0.005
+ },
+ {
+ "option_id": "B",
+ "label": "Synthetic alternative B",
+ "states": {
+ "rg": "RG_NARROWED",
+ "rf_ncrc": "RF_PASS",
+ "trc": "TRC_NOT_TRIGGERED",
+ "csv": "CSV_PASS_WITH_CONTROLS",
+ "rls": "RLS_RANKED"
+ },
+ "record_refs": {
+ "rg": {
+ "id": "B-rg",
+ "locator": "examples/synthetic_records.json#B-rg",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rf_ncrc": {
+ "id": "B-rf_ncrc",
+ "locator": "examples/synthetic_records.json#B-rf_ncrc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc": {
+ "id": "B-trc",
+ "locator": "examples/synthetic_records.json#B-trc",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "trc_trigger": {
+ "id": "B-trc_trigger",
+ "locator": "examples/synthetic_records.json#B-trc_trigger",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "csv": {
+ "id": "B-csv",
+ "locator": "examples/synthetic_records.json#B-csv",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "controls": {
+ "id": "B-controls",
+ "locator": "examples/synthetic_records.json#B-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "rls": {
+ "id": "B-rls",
+ "locator": "examples/synthetic_records.json#B-rls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "material_unresolved": [],
+ "requalification_required": false,
+ "controls_available": true,
+ "rls_score": 0,
+ "sigma_rls": 0.005
+ }
+ ],
+ "robustness": {
+ "status": "COMPLETE",
+ "record_ref": {
+ "id": "robust",
+ "locator": "examples/synthetic_records.json#robust",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "required_variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "comparisons": [
+ {
+ "variant_id": "nominal",
+ "candidate_id": "A",
+ "contender_id": "B",
+ "signed_gap": 5.601120336112039,
+ "record_ref": {
+ "id": "comparison-nominal",
+ "locator": "examples/synthetic_records.json#comparison-nominal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ {
+ "variant_id": "sigma_times_two",
+ "candidate_id": "A",
+ "contender_id": "B",
+ "signed_gap": 2.8213824634343934,
+ "record_ref": {
+ "id": "comparison-sigma_times_two",
+ "locator": "examples/synthetic_records.json#comparison-sigma_times_two",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ }
+ ],
+ "joint_stress_disposition": "NOT_TRIGGERED_WITH_RATIONALE",
+ "joint_stress_rationale": "The constructed fixture stipulates independent option error generators. It does not infer independence from absent empirical covariance data.",
+ "joint_record_ref": null,
+ "evidence_basis": "SYNTHETIC_STIPULATION",
+ "delta": 2,
+ "sole_survivor_record_ref": null
+ },
+ "framework_verdict": "ALLOW_FRAMEWORK_SELECTION",
+ "decision_state": "SELECTED_DECISIVE",
+ "framework_selected_option_id": "A",
+ "authority_selection": {
+ "option_id": null,
+ "record_ref": null
+ },
+ "execution": {
+ "state": "AUTHORIZED_WITHIN_SCOPE",
+ "option_id": "A",
+ "action_id": "SIMULATED-ACTION-1",
+ "authorization_ref": {
+ "id": "authorization",
+ "locator": "examples/synthetic_records.json#authorization",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "bound_configuration_id": "CONFIG-DEMO-1",
+ "authorized_at": "2026-09-28T09:00:00Z",
+ "expires_at": "2026-09-28T15:00:00Z",
+ "controls_ref": {
+ "id": "A-controls",
+ "locator": "examples/synthetic_records.json#A-controls",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "execution_event_ref": null
+ },
+ "runtime": {
+ "agent_present": true,
+ "mode": 2,
+ "connectivity": "CONNECTED",
+ "reentry_required": false,
+ "reconciled": true,
+ "authenticated_reentry_ref": null,
+ "material_successor": false,
+ "successor_requalification_ref": null,
+ "tool_execution_requested": true
+ },
+ "emergency": null,
+ "sgp_links": [
+ {
+ "target_id": "fictional digital target",
+ "sgp_version": "8.8",
+ "mps": "NOT_EVALUATED",
+ "mps_record_ref": null,
+ "fpp_record_ref": null,
+ "gpr_record_ref": null,
+ "spr_record_ref": null,
+ "icp_record_ref": null,
+ "rmcp_record_ref": null
+ }
+ ],
+ "blockers": [],
+ "monitoring_and_outcome": {
+ "plan_ref": {
+ "id": "plan",
+ "locator": "examples/synthetic_records.json#plan",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ },
+ "observation_ref": null,
+ "state": "NOT_STARTED",
+ "owner": "Synthetic monitor",
+ "reopen_triggers": [
+ "material change",
+ "unexpected harm"
+ ],
+ "reopened_stages": []
+ },
+ "challenge_appeal": {
+ "status": "AVAILABLE",
+ "owner": "Synthetic independent reviewer",
+ "route": "offline fixture review",
+ "record_ref": {
+ "id": "appeal",
+ "locator": "examples/synthetic_records.json#appeal",
+ "sha256": "77f18abb2a212c3823f4723a7bafb52032f319cfd0958134cd11a7d83a4e0751",
+ "basis": "SYNTHETIC"
+ }
+ },
+ "conformance": {
+ "target_level": "M1",
+ "assessment": "NOT_ASSESSED",
+ "evidence_refs": []
+ },
+ "claim_boundary": "Synthetic record consistency exercise only; not empirical validation, real authorization, cryptographic assurance, deployment approval or M2/M3 conformance.",
+ "provisional_choice": null
+}
diff --git a/releases/v2.1/examples/synthetic_records.json b/releases/v2.1/examples/synthetic_records.json
new file mode 100644
index 0000000..fbaa503
--- /dev/null
+++ b/releases/v2.1/examples/synthetic_records.json
@@ -0,0 +1,297 @@
+{
+ "claim_boundary": "Authored test data only, not empirical or domain evidence.",
+ "records": {
+ "A-rg": {
+ "record_id": "A-rg",
+ "record_type": "rg",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-rf_ncrc": {
+ "record_id": "A-rf_ncrc",
+ "record_type": "rf_ncrc",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-trc": {
+ "record_id": "A-trc",
+ "record_type": "trc",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-trc_trigger": {
+ "record_id": "A-trc_trigger",
+ "record_type": "trc_trigger",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-csv": {
+ "record_id": "A-csv",
+ "record_type": "csv",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-controls": {
+ "record_id": "A-controls",
+ "record_type": "controls",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "A-rls": {
+ "record_id": "A-rls",
+ "record_type": "rls",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "A",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-rg": {
+ "record_id": "B-rg",
+ "record_type": "rg",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-rf_ncrc": {
+ "record_id": "B-rf_ncrc",
+ "record_type": "rf_ncrc",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-trc": {
+ "record_id": "B-trc",
+ "record_type": "trc",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-trc_trigger": {
+ "record_id": "B-trc_trigger",
+ "record_type": "trc_trigger",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-csv": {
+ "record_id": "B-csv",
+ "record_type": "csv",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-controls": {
+ "record_id": "B-controls",
+ "record_type": "controls",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "B-rls": {
+ "record_id": "B-rls",
+ "record_type": "rls",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option": "B",
+ "description": "Synthetic stipulated review; not a clinical, engineering, legal or empirical warrant."
+ }
+ },
+ "closure": {
+ "record_id": "closure",
+ "record_type": "OptionClosureRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "families": "continuation, no-action, delay, staged alternatives considered in this tiny synthetic decision domain"
+ }
+ },
+ "robust": {
+ "record_id": "robust",
+ "record_type": "RLSRobustnessRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "variants": [
+ "nominal",
+ "sigma_times_two"
+ ],
+ "joint": "Synthetic independent option errors; no additional covariance stress triggered in this constructed fixture. Other potentially material modules must be independently reviewed for real decisions."
+ }
+ },
+ "authority": {
+ "record_id": "authority",
+ "record_type": "AuthoritySelectionRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "choice": "A",
+ "basis": "fictional named authority for simulation only; no real mandate"
+ }
+ },
+ "authorization": {
+ "record_id": "authorization",
+ "record_type": "ExecutionAuthorization",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "action": "SIMULATED-ACTION-1",
+ "config": "CONFIG-DEMO-1",
+ "simulation_only": true
+ }
+ },
+ "plan": {
+ "record_id": "plan",
+ "record_type": "MonitoringPlan",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "owner": "Synthetic monitor",
+ "stop": "explicit simulation stop; no connected tool or actuator"
+ }
+ },
+ "event": {
+ "record_id": "event",
+ "record_type": "ExecutionEvent",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "simulation_only": true
+ }
+ },
+ "appeal": {
+ "record_id": "appeal",
+ "record_type": "AppealRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "route": "fictional independent reviewer"
+ }
+ },
+ "reentry": {
+ "record_id": "reentry",
+ "record_type": "AuthenticatedReentryRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "simulation_only": true,
+ "signature_verified": false
+ }
+ },
+ "successor": {
+ "record_id": "successor",
+ "record_type": "QualificationContinuityRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "simulation_only": true
+ }
+ },
+ "sole": {
+ "record_id": "sole",
+ "record_type": "SoleSurvivorReview",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "simulation_only": true,
+ "no_gap_fabricated": true
+ }
+ },
+ "mps": {
+ "record_id": "mps",
+ "record_type": "SGPRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "version": "8.8",
+ "band": "MPS-NE",
+ "simulated": true,
+ "no_consciousness_claim": true
+ }
+ },
+ "emergency": {
+ "record_id": "emergency",
+ "record_type": "EmergencyRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "simulation_only": true,
+ "external_prerequisites_unverified": true
+ }
+ },
+ "comparison-nominal": {
+ "record_id": "comparison-nominal",
+ "record_type": "GapSensitivityRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option_A_RLS": 0.04,
+ "option_B_RLS": 0,
+ "sigma_A": 0.005,
+ "sigma_B": 0.005,
+ "epsilon": 1e-06,
+ "signed_gap": 5.601120336112039,
+ "synthetic_only": true
+ }
+ },
+ "comparison-sigma_times_two": {
+ "record_id": "comparison-sigma_times_two",
+ "record_type": "GapSensitivityRecord",
+ "fixture_only": true,
+ "not_independent_evidence": true,
+ "details": {
+ "option_A_RLS": 0.04,
+ "option_B_RLS": 0,
+ "sigma_A": 0.01,
+ "sigma_B": 0.01,
+ "epsilon": 1e-06,
+ "signed_gap": 2.8213824634343934,
+ "synthetic_only": true
+ }
+ }
+ }
+}
diff --git a/releases/v2.1/index.html b/releases/v2.1/index.html
new file mode 100644
index 0000000..430a442
--- /dev/null
+++ b/releases/v2.1/index.html
@@ -0,0 +1 @@
+MHIOS | Human interface and orchestrationSkip to main content
MathGov companion specification
Human Interface and Orchestration
Ground the claim. Qualify options. Compare survivors. Keep authority and execution separate.
What this package does
MHIOS makes decision evidence, uncertainty, qualification, responsibility and next actions visible. Its local checker tests declared record consistency. It cannot create evidence, evaluate sentience, authorize actions or certify a deployment.
Reading and scoped testing release. No operational dashboard or autonomous runtime is deployed here. Core equations and all fifteen supplied Core files are unchanged.
Hosted reading projection of the unchanged v2.1 standard. Page language and responsive table presentation were improved; semantic text is unchanged. Tables scroll horizontally on small screens and can be focused with the keyboard.
')
+body.insert(0,notice)
+toc=body.find('nav')
+if toc is not None:
+ toc.set('aria-label','Standard contents')
+ details=etree.Element('details');summary=etree.SubElement(details,'summary');summary.text='Contents — jump to a section'
+ toc.addprevious(details);details.append(toc)
+main=etree.Element('main',id='standard-text')
+started=False
+for el in list(body):
+ if el.tag=='h1' and el.get('id')=='mathgov-human-interface-and-orchestration-standard':started=True
+ if started:main.append(el)
+body.append(main)
+skip=etree.Element('a',href='#standard-text',attrib={'class':'skip'});skip.text='Skip to standard';body.insert(0,skip)
+for i,table in enumerate(main.xpath('.//table'),1):
+ wrap=etree.Element('div',attrib={'class':'table-scroll','role':'region','aria-label':f'Table {i}, scroll horizontally if needed','tabindex':'0'})
+ table.addprevious(wrap);wrap.append(table)
+original=html.fromstring(source.read_text(encoding='utf-8')).find('body')
+first=original.xpath('./h1[@id="mathgov-human-interface-and-orchestration-standard"]')[0]
+nodes=list(original);start=nodes.index(first)
+def tokens(s):return s.split()
+assert tokens(' '.join(e.text_content() for e in nodes[start:]))==tokens(''.join(main.itertext()))
+(out/'read').mkdir(exist_ok=True)
+(out/'read/index.html').write_text('\n'+html.tostring(doc,encoding='unicode'),encoding='utf-8')
+(out/'.nojekyll').write_text('')
diff --git a/site/index.html b/site/index.html
new file mode 100644
index 0000000..1966bfb
--- /dev/null
+++ b/site/index.html
@@ -0,0 +1,4 @@
+MHIOS v2.1 | Human Interface and OrchestrationSkip to main content← RippleLogic research collections
MHIOS v2.1 · CORE v13.0 RELEASE I · APACHE-2.0
Make the decision process visible.
The MathGov Human Interface and Orchestration Standard connects evidence, qualification, comparison and accountable handoffs—while keeping authority and execution separate.
Research and teaching companion. MHIOS v2.1 is pinned to all fifteen unchanged Core v13.0 Release I files. Its local checker tests declared record consistency. A successful check does not authorize an action or certify a deployment.
Read, inspect and adapt
The complete standard
A 41-page specification with source ownership, roles, status presentation, qualification, uncertainty, authority, monitoring and migration.
The fourteen-sheet workbook helps assemble records. Its token checks do not calculate Canon scores or validate the underlying evidence. The YAML draft is intentionally incomplete.
Two local schemas, six synthetic examples and a read-only checker provide bounded implementation surfaces. They are not the full external Canon record system.
Publication edition 1 adds explicit date-time validation dependencies and an accessible hosted reader. The original publication ZIP is preserved unchanged. Its 86 files include all fifteen exact Core dependencies. The repeated local suite passed 133 tests, all six example checks and the source, document and checksum checks.
Synthetic fixtures use a declared replay time. Historical validity never restores live permission. Store new verification evidence outside the immutable package.
Evidence, reuse and version history
MHIOS's semantic master is Markdown; Word, PDF and HTML are reading projections. The Core owns its governing semantics. The Apache-2.0 license permits use, modification and redistribution under its terms; retain notices and identify changes.
The prior public GitHub edition was v0.8. This supplied v2.1 edition records a v2.0 source baseline and requires explicit migration; old records cannot simply be relabeled. The historical release remains available.
The package does not establish empirical effectiveness, M2/M3 deployed-interface conformance, complete external Canon integration, native Excel interoperability, lawful authority, physical safety or production readiness. Manual and implementation-specific obligations remain visible in its coverage register.
\ No newline at end of file
diff --git a/site/robots.txt b/site/robots.txt
new file mode 100644
index 0000000..c3d764f
--- /dev/null
+++ b/site/robots.txt
@@ -0,0 +1,3 @@
+User-agent: *
+Allow: /
+Sitemap: https://mathgov.github.io/mhios/sitemap.xml
diff --git a/site/sitemap.xml b/site/sitemap.xml
new file mode 100644
index 0000000..dfefb39
--- /dev/null
+++ b/site/sitemap.xml
@@ -0,0 +1 @@
+https://mathgov.github.io/mhios/https://mathgov.github.io/mhios/read/