Independent
Implementation Requirement

Independent Implementation Is Now Practically Testable

The solved candidate core now defines enough exact behavior for independently developed implementations to attempt the same Mandatory Core without consulting an existing codebase.

This makes independent implementation a current proof obligation for the solved profile rather than a purely future institutional idea.

The Standard Must Stand Without a Reference Codebase

The Foundational Survey Fabric shall be specified with sufficient completeness and precision that an implementation can be created independently from the published governing Specification, Conformance rules, and applicable Reference Vectors.

Access to an existing implementation shall not be required to determine canonical spatial meaning or the expected behavior of the solved Mandatory Core.

The Solved Core Must Be Reproducible Independently

Independent implementations shall be capable of reproducing the current candidate core, including CRPC parsing and normalization, canonical frame interpretation, Point / Segment / SCPE validation, exact predicates, deterministic normalization, ECEM semantics, and FSF-CJSON-1.0 parsing and serialization.

The purpose is not to require one implementation architecture. It is to prove that different architectures converge because the governing rules are sufficiently exact.

Canonical Meaning Must Not Depend on Exclusive Software

A conformance claim shall not require proprietary software, closed algorithms, inaccessible services, private libraries, or exclusive vendor infrastructure to reproduce authoritative Survey results.

Proprietary implementations may exist, but canonical truth shall remain independently derivable from the public governing materials.

Unpublished Convention Cannot Be Part of Canonical Truth

A conforming implementation shall not depend on undocumented institutional practice, private interpretation, oral tradition, unpublished exceptions, or tacit knowledge to determine authoritative results.

Any rule necessary to produce canonical truth belongs in the governing Specification, Conformance materials, or explicitly governed Reference Vector explanation.

Separate Implementers Must Reach the Same Answer

Independently developed conforming implementations shall reproduce the same authoritative canonical meaning for identical valid canonical inputs within the same applicable profile.

Where the governing Specification requires one unique normalized form or canonical byte sequence, those outputs shall also agree exactly.

Independent agreement is evidence that canonical behavior is determined by the Specification rather than by one implementation.

The Same Input Must Receive the Same Validity Judgment

Independent implementations shall classify the same candidate input identically under the same profile as canonical valid, valid noncanonical, invalid, or unsupported where the governing Conformance profile defines those outcomes.

Where valid noncanonical normalization is permitted, independently developed implementations shall also produce the same canonical normalized result.

Exact Geometry Truth Must Converge Across Implementations

Independent implementations shall agree exactly on the supported predicate profile, including Point equality and order, orientation, Point-on-Segment, Segment intersection, Point-on-boundary, Point-in-SCPE, polygon validity, connectedness, containment, and geometric equivalence where defined.

Divergence shall be investigated as a Conformance, fixture, Specification, or implementation issue rather than hidden through tolerance.

FSF-CJSON-1.0 Must Be Reproducible Without Shared Code

Independently developed implementations claiming FSF-CJSON-1.0 compatibility shall be able to parse the same valid canonical bytes to the same canonical object and serialize the same normalized object to identical canonical bytes.

Shared serializer libraries, shared parser code, or proprietary reference services shall not be necessary for canonical byte agreement.

Implementation Choice Must Remain Open

Conformance shall not require a particular programming language, operating system, database, hardware architecture, execution environment, cryptographic technology, blockchain, or vendor stack unless a later Requirement proves such dependency irreducibly necessary.

Different technical approaches remain permissible where they preserve the same canonical meaning and satisfy representation-specific obligations required by the governing Specification.

The Governing Rules Must Be Inspectable

The Specification and Conformance materials necessary to reproduce canonical Survey behavior shall be openly inspectable.

An independent implementer shall be able to determine the required mathematics, primitive geometry, validation behavior, normalization rules, canonical serialization, precision semantics, profile boundaries, and Conformance obligations from the governing materials themselves.

Canonical Expectations Must Be Testable Independently

Applicable Reference Vectors used to establish Conformance shall be openly available in sufficient form for independent implementations to execute the same cases and verify the required authoritative outcomes.

The solved core is now sufficiently deterministic for vectors covering CRPC normalization, validation, exact predicates, geometry normalization, ECEM semantics, and FSF-CJSON-1.0 bytes.

Hidden test suites may supplement quality assurance, but canonical compatibility shall not depend solely on tests that implementers cannot inspect or reproduce.

Different Architectures Should Still Converge

Independent implementations may differ in architecture, algorithms, performance strategy, internal data representation, caching, indexing, memory model, and execution technique.

Diversity is compatible with Conformance only where authoritative canonical meaning remains the same and all unique-representation obligations are satisfied.

Independent Means More Than a Second Build of the Same Code

Formal independent-implementation evidence shall ultimately require enough separation that reproduced results are not merely artifacts of shared hidden assumptions, copied algorithms, common unpublished libraries, or one implementation wrapped in another interface.

The exact evaluator and implementation-independence criteria remain open, but the intent is substantive independence of derivation from the governing standard.

Code May Illustrate the Standard, Not Replace It

A reference implementation may assist testing, education, interoperability, or fixture generation, but it shall not become an independent source of canonical spatial truth where its behavior conflicts with the governing Specification.

The standard governs the code. The code does not silently govern the standard.

Conformance Judgment Must Be Reproducible

Separate evaluators applying the same Specification, Conformance rules, and applicable Reference Vectors should be able to reach the same judgment regarding an implementation’s compatibility.

Conformance status shall not depend on discretionary private interpretation where the governing materials can define an objective result.

Canonical Truth Must Survive Outside a Running Service

The ability to interpret and verify canonical Survey truth shall not depend on continued operation of a particular server, database, hosted API, account system, network service, or vendor platform.

Operational systems may provide convenience and performance, but the underlying spatial truth shall remain reconstructable from the published standard and governed test materials.

Independent Agreement Cannot Canonize Undefined Mathematics

Two independent implementations agreeing on behavior for a Specification-open capability does not make that behavior canonical.

Current examples include general Boolean/composite output closure, arbitrary exact rotation, unresolved general distance and path-length scalar forms, future geometry not yet selected, and other open operation-result domains.

Independent implementation proves reproducibility only within a defined Specification scope.

Independent Reproduction Is Necessary Evidence, Not Canonical Authority

Independent implementation is part of the evidence required before a candidate mathematical architecture can credibly advance toward canonical adoption.

Successful reproduction demonstrates determinism and implementability. It does not itself adopt the Specification, create institutional authority, or supersede the governing adoption process.

Exclusive Dependency Prevents Canonical Conformance

If authoritative Survey results can be reproduced only through inaccessible code, private data, undocumented convention, proprietary service, exclusive institutional control, or a privileged hidden implementation dependency, the implementation shall not satisfy the independent implementation requirement.

Such dependency indicates that canonical truth has escaped the published standard or that the evidence of reproducibility is insufficient.

Independent Implementation Has Moved From Future Gate to Current Candidate Proof Obligation

The original section correctly required canonical truth to remain reproducible without privileged software or knowledge. The solved Specification core now provides enough exact behavior for genuinely independent implementations to be attempted and compared.

The formal number of implementations, evaluator rules, certification process, and evidence-publication requirements remain open. The architectural requirement itself is now executable for the solved profile.

Primary Referenced Findings

This Conformance section is derived especially from Requirements Findings #10, #14, #24, #61, #63–#64, #78–#81, and #84–#85.