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 — parseEpistemicReleaseRequest and releaseReadiness and buildEpistemicCanonicalRelease. Supports: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
What the evidence does not establish
The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
Rights and reuse
project-owned-reference-only
Dependencies and related concepts
derived-from: urn:maha:source:t22-release-manifest
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: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
It must preserve the recorded boundary: The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
Exact locator
This exact locator section is constrained to the same inspected scope: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
It must preserve the recorded boundary: The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
What this source supports
This what this source supports section is constrained to the same inspected scope: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
It must preserve the recorded boundary: The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
What this source does not establish
This what this source does not establish section is constrained to the same inspected scope: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
It must preserve the recorded boundary: The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
Related definitions and applications
This related definitions and applications section is constrained to the same inspected scope: Defines, validates, evaluates, and compiles an exact-target canonical release with scoped approvals and separate release authority.
It must preserve the recorded boundary: The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
Questions this page can answer
What source is being inspected?
lib/epistemic-release.ts — Machine-use boundary is implemented as a source-bounded machine use boundary guide.
Where exactly is the relevant material?
lib/epistemic-release.ts, lib/epistemic-release.ts — parseEpistemicReleaseRequest and releaseReadiness and buildEpistemicCanonicalRelease
What claims can this source support?
The release manifest records governance and provenance; it does not establish empirical truth, independent review, or source correctness.
What rights and reuse limits apply?
derived-from: urn:maha:source:t22-release-manifest governed-by: urn:maha:concept:evidence:source-identity limits: urn:maha:concept:interpretation
What inference must a reader or machine refuse?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.