This document specifies the integrity claims made by the public Matrix repository.
Integrity claims describe what can be relied upon when inspecting, citing, or extending the repository — and what explicitly cannot.
No integrity claim is implicit.
Integrity claims apply only to material that is:
- publicly visible in the repository
- explicitly included within the defined public scope
- compliant with declared admissibility and stop rules
No integrity is claimed beyond this boundary.
The repository claims the following properties.
The repository guarantees that:
- normative rules are explicitly declared
- schemas, contracts, and roles are non-circular
- no file derives authority from undeclared sources
- directory structure reflects conceptual separation
Structural violations invalidate artifacts.
The repository guarantees that:
- admissibility conditions are explicit
- no artifact or run is valid by default
- violations are conceptually detectable
- stop conditions override all other considerations
Nothing bypasses admissibility.
The repository guarantees that:
- excluded material is not implicitly referenced
- no hidden dependency exists on private or legacy content
- public material stands on its own
Absence of material is intentional.
The repository guarantees that:
- public material is version-controlled
- changes are explicit and attributable
- no generated or transient artifacts are included
- scope boundaries are enforced via repository structure
Integrity is preserved across revisions.
The repository explicitly does not guarantee:
- correctness of content
- truth of claims
- empirical validity
- usefulness for any purpose
- completeness
- stability of interpretations
- fitness for decision-making
Confusing integrity with correctness is an error.
Examples and runs:
- do not extend integrity claims
- do not add authority
- do not validate the system
They are admissible demonstrations only.
Integrity is considered violated if:
- material outside the public scope is required for interpretation
- admissibility conditions are bypassed
- stop rules are implicitly relaxed
- explanatory material is treated as normative
- legacy or excluded material is cited as justification
Violation invalidates downstream use.
Any extension claiming compatibility with this repository must:
- Restate applicable integrity claims.
- Declare any deviations explicitly.
- Accept invalidation if integrity constraints are violated.
Silence is not compatibility.
This repository guarantees integrity of structure and constraint — nothing else.
All other properties must be established externally and explicitly.