Skip to main content

Query contract

The authoritative product contract lives in specs/queries/README.md. The generated pages on this site are projections of its executable fixtures, not a replacement for that specification.

Every primary reference query declares:

  • a versioned query-example envelope;
  • a canonical input fixture;
  • a canonical-ID-based request; and
  • the exact canonical output expected from the semantic oracle.

Before a generated page can be published, the reference-suite runner executes that request against its declared input. It records the actual output and the runtime that produced it, then requires exact JSON structural equality with the fixture expectation.

Results preserve source, artifact, evidence, assertion, validation, change set, proposal, review, decision, promotion, package, version, derivation event, rule, policy binding, semantic gap, and adapter-loss distinctions whenever they are in scope.

Backend adapters may translate these intents into other storage or query languages only when their outputs hydrate back to the same canonical shape or emit an explicit capability/loss report.

Executable proof​

The publication suite executes shared query families through the Python canonical runtime and the Rust-owned source-artifact query through the Rust canonical CLI. The wider repository continues to validate Python semantic oracles, Rust parity, memory/file adapter conformance, installed CLI contracts, and release acceptance. The documentation generator adds a separate drift gate: it cannot make a query pass, change its expected output, or promote its result.