Low-level package that implements the canonical serialization and content-addressing used throughout the governance pipeline. Consumed internally byDocumentation Index
Fetch the complete documentation index at: https://docs.manthan.systems/llms.txt
Use this file to discover all available pages before exploring further.
@parmanasystems/governance and @parmanasystems/verifier. Most applications don’t need to import this directly.
Install
Key exports
| Export | Description |
|---|---|
canonicalize | Stable, sorted-key JSON serialization |
sha256 | SHA-256 hex digest |
generateManifest | Build a content-addressed bundle manifest |
writeManifest | Write manifest to disk |
readManifest | Read and parse a manifest file |
verifyManifest | Verify that policy files match the manifest hash |
traverseDirectory | List policy files, excluding bundle artifacts |
canonicalize
Produces a deterministic JSON string from any value by recursively sorting object keys, NFC-normalizing strings, and normalizing line endings. This is the canonical byte representation for all hashing and signing operations across the governance pipeline.- Object keys are sorted recursively at every level
- Array order is preserved
- Strings are Unicode NFC-normalized
- CRLF (
\r\n) line endings are normalized to LF (\n) - Output is compact JSON - no extra whitespace
sha256
verifyManifest
Why canonical serialization matters
Theexecution_fingerprint and all signatures in the governance pipeline depend on canonical serialization. Without it:
- An attestation signed on one platform may not verify on another
- Key insertion order affects the hash, making fingerprints non-reproducible
- Third parties computing the fingerprint from the same inputs get different values