Direct answer
Cryptographic Commitments — Reproducibility is limited to the behavior or authority established by the bound source and explicitly excludes the source's non-claims.
Answer contract
Apply the reproducibility lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
t20-canonical-commitment — lib/evidence-dossier/digest.ts — canonicalJson and provenanceDigest. Supports: Canonicalizes supported JSON values and emits a SHA-256 commitment that can be recomputed from the same non-empty payload.
What the evidence does not establish
A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
Rights and reuse
project-owned-reference-only
Dependencies and related concepts
applies-to: urn:maha:concept:computation:cryptographic-commitments
governed-by: urn:maha:concept:governance
evidence-for: urn:maha:concept:computation
Authority or implementation
This authority or implementation section is constrained to the same inspected scope: Canonicalizes supported JSON values and emits a SHA-256 commitment that can be recomputed from the same non-empty payload.
It must preserve the recorded boundary: A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
Mechanism or procedure
This mechanism or procedure section is constrained to the same inspected scope: Canonicalizes supported JSON values and emits a SHA-256 commitment that can be recomputed from the same non-empty payload.
It must preserve the recorded boundary: A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
Verification and uncertainty
This verification and uncertainty section is constrained to the same inspected scope: Canonicalizes supported JSON values and emits a SHA-256 commitment that can be recomputed from the same non-empty payload.
It must preserve the recorded boundary: A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
What this does not establish
This what this does not establish section is constrained to the same inspected scope: Canonicalizes supported JSON values and emits a SHA-256 commitment that can be recomputed from the same non-empty payload.
It must preserve the recorded boundary: A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
Questions this page can answer
What is established?
Cryptographic Commitments — Reproducibility is limited to the behavior or authority established by the bound source and explicitly excludes the source's non-claims.
Which exact source or symbol establishes it?
t20-canonical-commitment, lib/evidence-dossier/digest.ts — canonicalJson and provenanceDigest
Which jurisdiction or implementation boundary applies?
A matching digest establishes byte-equivalent canonical content, not truth, authorship, timestamp, or legal signature.
What remains uncertain?
applies-to: urn:maha:concept:computation:cryptographic-commitments governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:computation
What must not be inferred?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.