Skip to content

Reference Implementation Boundaries

Do not implement these yet:

  • Production ETL orchestration
  • Polars backend
  • Spark backend
  • SQL compiler
  • External certification authority (Ch 23 §13)

The reference crate should remain a correct spec core based on SPEC.md.

In scope through 0.13.0

Everything through 0.12.0 below, plus Rich Portable Analytics (Ch 27 / A.9): plan v2, kernel/relational /2 (Candidate), Experimental advanced families, and related fingerprint / errorMode requirements.

In scope through 0.12.0 (subset)

  • Parse YAML and JSON into the Canonical Object Model
  • Seven-phase validation with structured diagnostics
  • Metadata validation (Phase 0.2)
  • Type system: conversions, collections, extension types, expression typing (Phase 0.2)
  • I/O interfaces: optional inputs, streaming, pre/postconditions (Phase 0.2)
  • Lineage completeness enforcement
  • Scoped field reference resolution
  • Compatibility analysis with five classification levels (Phase 0.3)
  • Evolution analysis with change categories and migration hints (Phase 0.3)
  • Ch 25 versioning validation (Phase 0.3)
  • Dataset-level lineage analysis: dependency graph, impact, governance (Phase 0.3)
  • Identifier registry with embedded dtcs: catalog, file/URI load, offline cache (Phase 0.4)
  • Registry-aware extension validation (mandatory/optional) (Phase 0.4)
  • Embedded full Ch 17–19 standard libraries with registry-driven semantics validation (Phase 0.5 starter; Phase 0.11 complete)
  • Static semantic analysis (Phase 0.6)
  • Transformation plan lowering with dependency graph and plan validation (Phase 0.7)
  • Portable Relational Profile: operators, rich joins/aggs, window frames, datetime, complex access, portable plans, differential conformance (Phase 0.12)
  • Plan optimization with semantics-preserving passes and equivalence checking (Phase 0.8)
  • Engine capability matching with embedded dtcs:reference profile (Phase 0.9)
  • Compilation to execution plans and reference in-memory runtime (Phase 0.9)
  • Conformance profiles, offline test suite, and security checklist automation (Phase 0.10)
  • WASM and Node bindings for parse, validate, and conformance declare (Phase 0.10)
  • SPEC completeness COM/runtime/stdlib deepening (Phase 0.11)
  • CLI (validate, analyze, plan, optimize, match, compile, run, inspect, diagnostics, version, compat, evolve, lineage, registry, conformance)
  • Python bindings via maturin

Lineage is not waived in the MVP core — contracts with outputs must declare provenance mappings.