Direct answer
Manuscript Versioning — Definition is implemented as a source-bounded definition guide.
Answer contract
Apply the definition lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
t22-versioned-release — lib/epistemic-release.ts — epistemicReleaseStatus and activeEpistemicReleases. Supports: Distinguishes active, superseded, and withdrawn release states over exact targets.
What the evidence does not establish
Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
Rights and reuse
project-owned-reference-only
Dependencies and related concepts
applies-to: urn:maha:concept:release:manuscript-versioning
governed-by: urn:maha:concept:governance
evidence-for: urn:maha:concept:release
Authority or implementation
This authority or implementation section is constrained to the same inspected scope: Distinguishes active, superseded, and withdrawn release states over exact targets.
It must preserve the recorded boundary: Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
Method or mechanism
This method or mechanism section is constrained to the same inspected scope: Distinguishes active, superseded, and withdrawn release states over exact targets.
It must preserve the recorded boundary: Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
Verification and uncertainty
This verification and uncertainty section is constrained to the same inspected scope: Distinguishes active, superseded, and withdrawn release states over exact targets.
It must preserve the recorded boundary: Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
What this does not establish
This what this does not establish section is constrained to the same inspected scope: Distinguishes active, superseded, and withdrawn release states over exact targets.
It must preserve the recorded boundary: Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
Dependencies
This dependencies section is constrained to the same inspected scope: Distinguishes active, superseded, and withdrawn release states over exact targets.
It must preserve the recorded boundary: Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
Questions this page can answer
What is established?
Manuscript Versioning — Definition is implemented as a source-bounded definition guide.
What exact source or implementation establishes it?
t22-versioned-release, lib/epistemic-release.ts — epistemicReleaseStatus and activeEpistemicReleases
What dependency remains separate?
Release lineage is not a universal publishing-version ontology and does not establish equivalence between manuscripts and versions of record.
What uncertainty remains?
applies-to: urn:maha:concept:release:manuscript-versioning governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:release
What must not be inferred?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.