lib/epistemic-release.ts — Machine-use boundary

Direct answer

lib/epistemic-release.ts — Machine-use boundary is implemented as a source-bounded machine use boundary guide.

Answer contract

Apply the machine use boundary lens only to the exact inspected source scope; do not infer authority from adjacent topics.

Evidence and exact locators

lib/epistemic-release.ts — 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

derived-from: urn:maha:source:t22-versioned-release

governed-by: urn:maha:concept:evidence:source-identity

limits: urn:maha:concept:interpretation

Source identity and provenance

This source identity and provenance 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.

Exact locator

This exact locator 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 source supports

This what this source supports 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 source does not establish

This what this source 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.

Related definitions and applications

This related definitions and applications 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