This repository uses strict DOI ownership by exact repository identity.
OMNIA != OMNIA-VALIDATION OMNIA DOI != OMNIA-VALIDATION DOI repo_name substring match is forbidden for DOI ownership exact repository identity is required for DOI ownership this_repository: Tuttotorna/OMNIA-VALIDATION this_repository_doi: 10.5281/zenodo.20322696 other_repository: Tuttotorna/OMNIA other_repository_doi: 10.5281/zenodo.20322683
Repository: Tuttotorna/OMNIA-VALIDATION Release tag: v2026.05.22 Release commit: e98a397 Release DOI: 10.5281/zenodo.20325096
Boundary:
measurement != validation validation != orchestration orchestration != decision decision != measurement
Zenodo DOI badge for this repository.
Repository: Tuttotorna/OMNIA-VALIDATION GitHub repository id: 1227176782 Release tag: v2026.05.22 Release commit: e98a397 Latest release DOI: 10.5281/zenodo.20325096
Release DOI: 10.5281/zenodo.20083830
GitHub release: OMNIA-VALIDATION v1.0.0 release
From a clean environment:
git clone [OMNIA-VALIDATION.git](https://github.com/Tuttotorna/OMNIA-VALIDATION.git)
cd OMNIA-VALIDATION
python -m pip install -e .
pytest
If the repository has optional example runners, run them after tests pass.
The point is not to believe the framework.
The point is to inspect the artifacts.
OMNIA-VALIDATION is the evidence layer of MB-X.01 / OMNIA.
It should contain:
- reproducible validation cases;
- regression tests;
- artifact contracts;
- failure examples;
- public reports;
- boundary documents;
- minimal commands that reviewers can run without understanding the whole ecosystem.
The public path is:
run tests -> inspect artifacts -> read reports -> trace claims
OMNIA-VALIDATION does not:
- infer semantic truth;
- decide whether a system is correct;
- replace external judgment;
- prove consciousness;
- perform security scanning;
- perform cryptographic attacks;
- recover keys;
- turn structural measurements into final decisions.
It validates artifacts and claims inside a declared boundary.
A validation repository must not read like a manifesto.
It must behave like a showroom.
A first-time visitor should see:
one command
one artifact
one failure mode
one report
one boundary
The correct public demonstration is:
surface correctness can pass
structural stability can fail
the failure must be inspectable
Every validation case should ideally expose:
| Field | Meaning |
|---|---|
| input | What was measured |
| transformation | What changed |
| expected boundary | What should remain stable or admissible |
| measured output | What OMNIA or related tools produced |
| artifact | Where the result is stored |
| result | pass / flag / fail / inconclusive |
| rationale | Why this result matters structurally |
| limitation | What the result does not prove |
- docs/SHOWROOM.md
- docs/VALIDATION_PROTOCOL.md
- docs/ARTIFACT_CONTRACT.md
- docs/FAILURE_EXAMPLES.md
- docs/REPRODUCIBILITY.md
- docs/BOUNDARY.md
For the full ecosystem map, start here:
| Repository | Role |
|---|---|
| lon-mirror | Canonical public entry point |
| OMNIA-VALIDATION | Public validation showroom |
| OMNIA | Core structural measurement engine |
| OMNIABASE | Representation invariance foundation |
| omnia-limit | Stop / continue boundary layer |
| OMNIA-RADAR | Structural signal detection layer |
| OMNIA-INVARIANCE | Structural invariance layer |
| OMNIA-CONSTANT | Structural constant candidate layer |
| OMNIAMIND | Structural cognition orchestration layer |
| OMNIA-THREE-BODY | Dynamic divergence stress test |
| OMNIA-SECURITY | Bounded structural security diagnostics |
| OMNIA-CRYPTO | Bounded structural crypto diagnostics |
measurement != inference != decision
test -> output -> artifact -> failure/fragility -> report
MIT.
OMNIA-VALIDATION is the control-plane registry for the current OMNIA ecosystem backbone.
OMNIA measurement
-> BoundaryCertificate
-> omnia-limit validate_certificate()
-> OMNIA-VALIDATION ValidationEnvelope
-> CI regression
-> satellite compliant producer / adapter / consumer / observer
Current registry state:
total registered entries: 14
backbone core entries: 5
satellite compliant: 9
Protected separation rules:
measurement != validation
validation != orchestration
orchestration != decision
decision != measurement
observation != decision
domain adaptation != backbone redefinition
Public status document:
docs/ECOSYSTEM_STATUS.md
Executable registry:
docs/ecosystem_backbone_compliance_registry.json
Registry tests:
tests/test_ecosystem_backbone_compliance_registry.py
tests/test_ecosystem_status_documentation.py
For a fast public overview of the full OMNIA ecosystem, start here:
This map explains the canonical backbone, the core repositories, the compliant satellites, and the role-separation rules that prevent layer collapse.
For a first public orientation to the full MB-X.01 / Logical Origin Node ecosystem, start here:
This entry point explains the ecosystem identity, the canonical backbone, the core repositories, the compliant satellites, and the strict role-separation rule:
measurement != validation != orchestration != decision
The public root reference side of the MB-X.01 / L.O.N. ecosystem is exposed by lon-mirror:
https://github.com/Tuttotorna/lon-mirror/blob/main/docs/MBX01_LON_ROOT_REFERENCE_LINK.md
Verified lon-mirror commit:
22a320d
Role:
root_reference_observer
Boundary:
observation != decision
The lon-mirror root reference observer now exposes a public entry point.
registry_commit: 22a320d public_entrypoint_commit: f74b799 public_entrypoint_link: https://github.com/Tuttotorna/lon-mirror/blob/main/docs/PUBLIC_ENTRYPOINT.md root_reference_link: https://github.com/Tuttotorna/lon-mirror/blob/main/docs/MBX01_LON_ROOT_REFERENCE_LINK.md
This closes the public path from OMNIA-VALIDATION to the lon-mirror first-reader doorway while preserving the boundary:
measurement != validation != orchestration != decision
For a non-technical first orientation, start here:
- First reader path: docs/FIRST_READER_PATH.md
- First reader path URL: https://github.com/Tuttotorna/OMNIA-VALIDATION/blob/main/docs/FIRST_READER_PATH.md
- lon-mirror public entry point: https://github.com/Tuttotorna/lon-mirror/blob/main/docs/PUBLIC_ENTRYPOINT.md
Thirty-second model:
OMNIA measures. omnia-limit validates the boundary certificate. OMNIA-VALIDATION validates the control-plane envelope. OMNIAMIND orchestrates. Satellites adapt, observe, or consume. lon-mirror acts as root reference observer.
Boundary:
measurement != validation != orchestration != decision
Patch anchors:
OMNIA-VALIDATION commit: 2e7e63c lon-mirror commit: f74b799
The public first-reader path commits are now registered.
OMNIA-VALIDATION: first_reader_path_commit: 83fa07f first_reader_path_link: https://github.com/Tuttotorna/OMNIA-VALIDATION/blob/main/docs/FIRST_READER_PATH.md
lon-mirror: first_reader_path_commit: 4dd5cb5 first_reader_path_link: https://github.com/Tuttotorna/lon-mirror/blob/main/docs/FIRST_READER_PATH.md public_entrypoint_commit: f74b799 latest_public_commit: f74b799
Boundary: first-reader path != validation first-reader path != measurement first-reader path != orchestration first-reader path != decision
OMNIA-VALIDATION now protects the distinction between commit identity and registry role identity.
Commit equality is not role equality.
Commit divergence is optional.
Role divergence is mandatory.
Role policy document:
https://github.com/Tuttotorna/OMNIA-VALIDATION/blob/main/docs/REGISTRY_ANCHOR_ROLE_SEPARATION.md
Protected role anchors:
OMNIA-VALIDATION registry_role: validator_backbone_core
OMNIA-VALIDATION first_reader_path_role: first_reader_surface
lon-mirror registry_role: root_reference_observer
lon-mirror first_reader_path_role: first_reader_surface
Boundary:
registry topology != BoundaryCertificate
first-reader path != validation
first-reader path != measurement
first-reader path != orchestration
first-reader path != decision
The final release audit for the MB-X.01 / L.O.N. ecosystem is recorded here:
docs/MBX01_LON_FINAL_RELEASE_AUDIT.md
Final audit state:
Repositories audited: 12
Clean repositories: 12
Repositories with issues: 0
No duplicate DOI values detected.
No duplicate GitHub repository ids detected.
OMNIA DOI != OMNIA-VALIDATION DOI
The final MB-X.01 / L.O.N. ecosystem audit has been archived as a dedicated OMNIA-VALIDATION release.
repository: Tuttotorna/OMNIA-VALIDATION release_tag: v2026.05.22 release_commit: e98a397 release_doi: 10.5281/zenodo.20325096 zenodo_record_url: https://zenodo.org/records/20325096 release_role: final_ecosystem_audit_snapshot final_audit_doc: docs/MBX01_LON_FINAL_RELEASE_AUDIT.md repositories_audited: 12 clean_repositories: 12 repositories_with_issues: 0 duplicate_doi_values: none duplicate_github_repository_ids: none A DOI identifies an archived release snapshot. A DOI is not a measurement. A DOI is not validation. A DOI is not orchestration. A DOI is not a decision.
measurement != inference != decision
This repository is part of the MB-X.01 / OMNIA ecosystem. Its outputs must be read as structural measurement, validation, detection, orchestration or adapter artifacts according to the repository role. They are not autonomous semantic truth claims and they do not make external decisions.