Conformance
The framework through which software proves that it produces the same exact Ground truth required by SG-SPEC-1.0.
Spatial Ground Conformance defines how an implementation, validator, canonical Ground Definition, or derived artifact demonstrates fidelity to the adopted Spatial Ground Specification. It translates the formal membership model into observable proof: structural validity, deterministic canonicalization, exact membership, invalid-input separation, canonical result equivalence, hidden-state independence, reconstruction, and independent reproducibility.
Conformance verifies. It does not legislate. It cannot create World-space, redefine the Spatial Ground Specification, resolve missing FSF mathematics through test precedent, or override the adopted canonical Ground Definition.
Governing Rule Specification defines truth. Conformance proves implementation fidelity to that truth.
Current Standing
Production Result
Production Conformance / Reconstruction — PASS. Two independent reconstruction implementations reproduced the adopted production behavior with zero cross-implementation mismatch. The governing Specification is SG-SPEC-1.0, Gate B is complete, and SG-WORLD-SPACE-INSTANCE-0001 is the adopted canonical World-space instance.
Conformance Classes
Definition Validator
Validates SG-CJSON structure, dependency declarations, canonicalization, permitted constructs, and exclusion of prohibited Ground semantics.
Membership Evaluator
Adds exact membership evaluation, FSF input validation, invalid-input separation, and deterministic termination.
Full Semantic Validator
Adds semantic equivalence, refinement behavior, canonical-limit tests, FSF dependency compatibility, and applicable constitutional instance checks.
Independent Reimplementation
Requires an independently developed implementation to reproduce the same canonical outputs from the same public normative inputs.
Mandatory Proof Surface
Definition Validation
Valid Ground Definitions must be accepted; malformed, unsupported, nondeterministic, dependency-defective, or semantically prohibited definitions must be rejected.
Exact Two-Valued Result
Every valid canonical Survey input must resolve to exactly WORLD or NON_WORLD. Invalid Survey input remains outside the membership vocabulary.
Canonical Result Equivalence
Independent conforming implementations must return identical canonical membership results for identical canonical inputs.
Hidden-State Prohibition
Membership may not vary with caches, clocks, locale, network state, user identity, ownership state, deployment environment, or other mutable hidden conditions.
Test Architecture
The Conformance framework includes exact test families for interior World locations, exterior non-World locations, canonical-limit contact, equivalent and non-equivalent Survey references, invalid Survey input, representation traps, transformation traps, hidden-state traps, supported refinement behavior, constitutional instance conditions, adversarial inputs, reconstruction, and independent implementation agreement.
Many Implementations · One Truth If independent implementations disagree, the architecture has discovered a problem—not a second canon.
Reference Vector Relationship
Reference Vectors provide exact executable fixtures. Conformance defines the proof obligations and conditions for passing them. The relationship is:
Proof Sequence Specification → Conformance → Reference Vectors
Reference Vectors may expose defects or unsupported dependencies, but they may not create semantics absent from the Specification.
Specification Principle Reference Vectors demonstrate the Specification. They do not create the Specification.
Production Conformance / Reconstruction
Reconstruction Evidence
Final adopted-instance proof across two independent reconstruction implementations with zero cross-implementation mismatch.
Spatial Ground Conformance
The detailed Conformance architecture defining classes, mandatory behavior, validation, failure conditions, reconstruction, and independent implementation requirements.
Demonstrated Production Membership
WORLD: origin; canonical start vertex; first boundary-edge midpoint. NON_WORLD: (490000,0), (0,490000), (750000,0). INVALID_INPUT: (1000001,0).
Authority Boundary
Conformance may validate implementation behavior, compare canonical outputs, verify exactness and canonicalization, preserve evidence, report failure, and support independent reconstruction. It may not redefine Requirements, invent missing Specification mathematics, create competing canonical World-space truth, redefine FSF mathematics, adopt the Specification, or establish the canonical World-space instance.
Conformance Boundary A validator may detect Ground truth. It may not create Ground truth.