Conformance Testing - Bryant McGill

# Conformance Testing **Domain:** Testing / Interoperability **Doc Type:** Canonical Concept Node **Maturity:** Core Design Principle **Related:** [[wiki/Portable Contract|Portable Contract]], [[wiki/Shared Fixtures|Shared Fixtures]], [[wiki/Cross-Runtime Capability Parity|Cross-Runtime Capability Parity]] --- ## Definition **Conformance testing verifies that an implementation satisfies a shared behavioral contract rather than merely passing its own local tests.** Every runtime consumes the same fixtures and must agree on accepted inputs, normalized results, and error behavior. ## Project Context The modern X library requires JavaScript, PHP, Python, and Perl runners that execute canonical fixtures directly. A new port is not declared complete because its function names exist; it earns parity by producing the contract's expected observations. ## Key Insight **Conformance converts portability from an architectural intention into a repeatable measurement.** ## See Also [[wiki/Shared Fixtures|Shared Fixtures]], [[wiki/Canonical Capability Name|Canonical Capability Name]], [[wiki/Error Behavior|Error Behavior]], [[wiki/Technical Terms|Technical Terms]] ## Relationships - **Collection route:** [[collections/Neurotech|Neurotech]]. - **Source context:** [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]]. - **Inference provenance:** [[research/Research Inferences|Research Inferences]]. ## Research Inferences  These entries translate the forward-looking register in [[research/Research Inferences|Research Inferences]] into ordinary wiki prose. The tier labels apply to the inference, not automatically to every factual anchor inside it. The interpretive frame comes from [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]]. Collection route: [[collections/Neurotech|Neurotech]]. - **INF-0275 — Plausible.** Conformance suites determine which implementations are permitted to interoperate, making the test authority a gatekeeper. In a continuity market, conformance testing would decide which hosts are allowed to receive a person, which is regulatory power exercised through tooling.  ## Research Inference Attractors  These are secondary semantic placements for the inference attractor network. Each statement keeps its original ID and tier; its canonical cluster page links back to every destination. Source register: [[research/Research Inferences|Research Inferences]]. Interpretive context: [[articles/Technologies for Consciousness Mapping and Transfer|Technologies for Consciousness Mapping and Transfer]] and [[articles/Mind Uploading and AI — The Host is Reusable and the Person is the Delta|Mind Uploading and AI — The Host is Reusable and the Person is the Delta]]. Collection route: [[collections/Neurotech|Neurotech]]. - **INF-0257 — Strongly indicated.** Cell-type atlases require agreed names before comparisons across laboratories mean anything, which is why nomenclature committees precede discoveries in practice. Shared ontology is the substrate on which comparative connectomics and typed emulation both depend. - **Canonical cluster:** [[wiki/Continuity Governance|Continuity Governance]] - **INF-0263 — Strongly indicated.** Capability domains accelerate once a benchmark exists because improvement becomes visible and comparable. Establishing benchmarks for residual sufficiency and emulation fidelity would do for continuity what ImageNet did for vision. - **Canonical cluster:** [[wiki/Continuity Governance|Continuity Governance]] - **INF-0274 — Strongly indicated.** The reference implementation becomes the specification in practice, because ambiguities are resolved by reading code. Whoever writes the first working residual-format library sets the semantics regardless of what the document says. - **Canonical cluster:** [[wiki/Continuity Governance|Continuity Governance]]