The catalog assigns 2 packages to this responsibility boundary. This page derives its vocabulary, topology, publication state, and maturity profile directly from those audited records.
Counts expose what the catalog actually contains. They do not convert package metadata into production-readiness or quality claims.
4 package-specific limitation entries remain visible across this domain.
6 unique capability statements are attached to packages in this domain. The language below is catalog evidence, preserved without expanding the claim.
cross-crate proof suite
production-vs-reference conformance
workspace integration fixtures
independent reference interpreters
golden fixtures
differential conformance findings
Edges are derived from sibling dependency declarations. Cross-domain traffic describes manifest topology, not runtime call direction, frequency, or activation.
Each record has a stable URL with its complete catalog scope, capabilities, targets, features, relationships, registry evidence, update trail, and known limits.
Workspace-level cross-crate integration and proof suite separated from the reference testkit.
Independent reference interpreters and golden-fixture support for semantic conformance tests.
This route reorganizes audited package metadata. It does not add implementation claims or expose access-controlled source.
p32-schema-compat / 011027f77fc7a53c6ecb05300d5c34144370fa3b