Skip to content

Specification & Conformance

The VMx behavior contract starts in spec/, not in any single language implementation.

Source Of Truth

What Lives In The Spec

  • 23 numbered chapters from 00-overview.md through 22-discriminator-vm.md
  • ADRs describing behavior and design decisions
  • shared JSON fixtures consumed by the language flavors
  • the cross-language conformance catalog in spec/12-conformance.md

Conformance Model

The current catalog contains:

  • 281 library IDs implemented by the four full-parity flavors
  • 5 THEME-00x scenario IDs exercised by the flagship example apps
  • 286 total IDs in the published catalog

The source overview is here: spec/12-conformance.md.

How The Repo Enforces It

  • Each language flavor carries a conformance suite under its own tree.
  • tools/check-conformance-coverage.py enforces full library coverage across C#, Python, TypeScript, and Swift.
  • The examples workflows enforce the separate flagship scenario contract.

Practical Reading Path

  1. Read spec/README.md for chapter ownership and release history.
  2. Read the primitive pages on this site for a faster conceptual map.
  3. Use the flavor README when you need package details or host-specific examples.
  4. Use the parity matrix and conformance catalog when you need proof rather than overview.