Reference
Vectors
Exact fixtures through which conforming implementations prove the expected results of defined Spatial Ground semantics.
Spatial Ground Reference Vectors provide exact input-and-expected-result fixtures for validating Ground behavior across conforming implementations. They test SG-CJSON structure, canonicalization, FSF leaf validity, membership, equivalence, invalid input, hidden-state independence, reconstruction, independent implementation, and deliberately difficult dependency boundaries.
Reference Vectors do not define Spatial Ground semantics. They instantiate and test rules supplied by the Requirements, Specification, SG-CJSON, the Closed World-Space Convention, and Conformance.
Reference Vector Question Given this exact Ground input and this exact declared FSF test meaning, what exact answer must every conforming implementation produce?
Governing Rule Specification defines the rule. Reference Vectors prove the expected result.
Corpus Standing
SG-RV-1.0
The attached source establishes SG-RV-1.0 as the initial canonical Ground vector corpus. It uses the synthetic FSF-TEST-1.0 profile to test Ground semantics without inventing production Survey geometry.
Vector Status Classes
NORMATIVE
A valid input for which the governing rules determine one exact expected result.
NEGATIVE
An invalid artifact or input for which one exact failure class is expected.
ADVERSARIAL
A deliberately difficult case whose exact result is nevertheless determined.
BLOCKED_BY_FSF
A case that must not receive a fabricated production answer until the required lower-layer FSF semantics are defined.
Reference Vector Families
Structure and Dependency
SG-CJSON structure, canonicalization, and FSF leaf validity.
Membership and Limits
Basic membership, Boolean composition in the source corpus, and exact limit behavior.
Equivalence and Repeatability
Survey equivalence, invalid inputs, and hidden-state repeatability.
Reconstruction and Boundary Cases
Reconstruction, independent implementation, and reserved FSF dependency exposure.
Representative Vectors
SG-RV-001 / 002
Basic WORLD and NON_WORLD membership under a declared synthetic FSF fixture.
SG-RV-003 / 004
Tests exact outer-limit membership under the Closed World-Space Convention.
SG-RV-013 / 014
Confirms that invalid or unknown Survey input yields INVALID_INPUT rather than NON_WORLD.
SG-RV-023
Requires a clean implementation to reconstruct the expected membership mapping from the Specification, Ground Definition, test dependency semantics, and corpus alone.
Synthetic FSF Test Profile
The source corpus uses FSF-TEST-1.0 as a deliberately synthetic test-only dependency. It is not production spatial truth and must not be treated as a BitPangea Survey specification.
Test Boundary No FSF-TEST identifier may appear in a canonical BitPangea World-space instance.
SG-RV-024
Reserved Boundary / Set-Class Dependency
SG-RV-024 preserves a deliberately difficult hole-boundary case under non-regular set difference. The source corpus records it as BLOCKED_BY_FSF. The vector is intentionally retained because a Reference Vector may expose a missing or unresolved rule, but it may not invent the answer.
Hard-Vector Principle The purpose of a hard vector is not to make the architecture look complete. It is to discover exactly where it is not.
Cross-Implementation Rule
For every executable NORMATIVE or ADVERSARIAL vector, conforming implementations must agree:
Canonical Agreement Result_A(vector) = Result_B(vector)
A disagreement is evidence of an implementation, fixture, dependency, or Specification problem. It is not a second canon.
Primary Corpus Records
Spatial Ground Reference Vectors
The complete SG-RV-1.0 Reference Vector specification and vector inventory.
SG-RV-1.0 JSON
The machine-readable Reference Vector corpus for executable testing and cross-implementation comparison.
Architectural Boundary
Reference Vectors may prove, compare, reproduce, stress, expose ambiguity, and demonstrate exact expected results. They may not create World-space, redefine the Spatial Ground Specification, invent FSF mathematics, convert test precedent into canonical authority, or pull higher-layer meaning into Ground results.
Specification Principle Reference Vectors demonstrate the Specification. They do not create the Specification.