consiliency-canon-core 0.1.0

Canon v2 canonicalization engine — the shared byte/digest truth for Consiliency certificates

canon-core packaging (PKG)

Dual-published canonicalization engine — the shared byte/digest truth every Consiliency certificate hashes. Same Rust engine (src/lib.rs), two distributions:

Distribution	Tool	Name	Consumer	Entry points
PyPI	maturin (pyproject.toml)	consiliency-canon-core (imports as canon_core)	Python	canonical_bytes_from_json(tagged_json), digest_from_json(tagged_json, profile)
npm	wasm-pack (Makefile.packaging)	@consiliency/canon-core (Node target)	governed-pipeline (JS)	canonicalBytesFromJson(taggedJson), digestFromJson(taggedJson, profile)

Surface is tagged-JSON text, not a raw value — this is load-bearing for byte-identity: a lone surrogate serializes to the ASCII escape \ud800, survives UTF-8 marshalling, and serde_json rejects it at parse (SPEC §5.0). Consumers MUST feed tagged-JSON text produced by a validating encoder, never a raw host string (see the GP-canon design doc). Both packages ship the shared canon-vectors.json corpus so consumers can self-verify parity.

Local build

make -f Makefile.packaging all      # needs: maturin, wasm-pack, wasm32 target

Publish

Push a canon-core-v<version> tag → .github/workflows/publish-canon-core.yml builds + publishes both via OIDC. One-time registry setup (see the workflow header) is a USER action: claim the PyPI project + the npm @consiliency scope and register the trusted publishers.