Direct answer
Canonical Release — Workflow describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.
Answer contract
Apply the workflow lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
t19-canonical-release-flow — lib/epistemic-release.ts — buildEpistemicCanonicalRelease. Supports: Creates an exact-target release under a separately authenticated release authority.
What the evidence does not establish
Release is publication, not factual verification.
Rights and reuse
project-owned-reference-only
Dependencies and related concepts
applies-to: urn:maha:concept:evidence:canonical-release
governed-by: urn:maha:concept:governance
evidence-for: urn:maha:concept:evidence
Inputs and prerequisites
This inputs and prerequisites section is constrained to the same inspected scope: Creates an exact-target release under a separately authenticated release authority.
It must preserve the recorded boundary: Release is publication, not factual verification.
Ordered behavior
This ordered behavior section is constrained to the same inspected scope: Creates an exact-target release under a separately authenticated release authority.
It must preserve the recorded boundary: Release is publication, not factual verification.
Verification or refusal states
This verification or refusal states section is constrained to the same inspected scope: Creates an exact-target release under a separately authenticated release authority.
It must preserve the recorded boundary: Release is publication, not factual verification.
What this does not establish
This what this does not establish section is constrained to the same inspected scope: Creates an exact-target release under a separately authenticated release authority.
It must preserve the recorded boundary: Release is publication, not factual verification.
Related definition and applications
This related definition and applications section is constrained to the same inspected scope: Creates an exact-target release under a separately authenticated release authority.
It must preserve the recorded boundary: Release is publication, not factual verification.
Questions this page can answer
What exact behavior is implemented?
Canonical Release — Workflow describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.
Which inputs and identities are required?
t19-canonical-release-flow, lib/epistemic-release.ts — buildEpistemicCanonicalRelease
Which exact symbol bears the explanation?
Release is publication, not factual verification.
Which refusal or verification boundary applies?
applies-to: urn:maha:concept:evidence:canonical-release governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence
What external outcome does this implementation not establish?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.