Technical Test Strategy

Documentation status: guide — see Maturity and evidence.

Technical tests protect Runtime invariants below application-level model tests.

Test families

• parsing and semantic resolution;
• hypergraph identity, traversal and transformation;
• transaction and persistence behavior;
• ABI/binding marshalling and lifetime;
• tensor correctness and gradient checks;
• accelerator equivalence and fallback;
• service/messaging failure semantics;
• performance benchmarks kept separate from correctness tests.

Publication rule

A test file can prove that an implementation path exists, but does not by itself make that path a supported public API. Public reference documentation requires a deliberate contract and compatibility policy.