stability harness of soft3 — a release of the stack IS a conformance snapshot. one hemera fingerprint per canonical encoding, one per mechanism output. drift surfaces at commit time.
canonical(value) → hemera fingerprint → conformance/encoding.snap
nox(scenario, input) → hemera fingerprint → conformance/mechanism.snap
union(all snapshots) → hemera root → protocol stability root
each soft3 repo carries its own conformance/ directory of .snap files. CI compares; drift fails. promotion through five tiers (alpha → epsilon) determines how hard a snapshot is to move.
layout
| dir | purpose |
|---|---|
| docs/ | why this crate exists |
| specs/ | how snapshots are produced, compared, blessed |
| rs/ | cyber-conformance — trait, tiers, surfaces, the cargo-conformance runner |
| snapshots/ | the stack snapshot: encoding.snap, mechanism.snap, manifest.snap, bless provenance |
| fixtures/ | nox input programs, committed zheng proof fixtures |
position in the stack
conformance sits beneath every other soft3 component except hemera itself. bbg, lens, zheng, radio, foculus, cybergraph, nox, wysm, trident, mudra, mir each register their stable surface area as Conformant types and named mechanism scenarios.
status
implemented. the stack snapshot covers hemera, nebu, nox, zheng, tade and cybergraph surfaces (see specs/); the release train's conformance-snapshot gate runs cargo conformance --check from this crate. per-crate adoption follows each crate's tier promotion.
see soft3 for the surrounding stack and hemera for the underlying fingerprint primitive.