Direct answer
Runtime Witness Receipts — Artifact Role Inventory is implemented as a source-bounded artifact role inventory guide.
Answer contract
Apply the artifact role inventory lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
Computational witness receipt artifact-role verifier — lib/evidence-dossier/runtime-witness.ts — artifacts: and verifyComputationalWitnessReceipt. Supports: Defines input, output, and code artifact roles; validates deterministic ordering, uniqueness, byte counts, and SHA-256 commitments.
What the evidence does not establish
An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
Rights and reuse
project-owned-reference-only
Dependencies and related concepts
applies-to: urn:maha:concept:evidence:runtime-witness-receipts
governed-by: urn:maha:concept:governance
evidence-for: urn:maha:concept:evidence
Executable contract
This executable contract section is constrained to the same inspected scope: Defines input, output, and code artifact roles; validates deterministic ordering, uniqueness, byte counts, and SHA-256 commitments.
It must preserve the recorded boundary: An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
Verification evidence
This verification evidence section is constrained to the same inspected scope: Defines input, output, and code artifact roles; validates deterministic ordering, uniqueness, byte counts, and SHA-256 commitments.
It must preserve the recorded boundary: An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
Failure boundaries
This failure boundaries section is constrained to the same inspected scope: Defines input, output, and code artifact roles; validates deterministic ordering, uniqueness, byte counts, and SHA-256 commitments.
It must preserve the recorded boundary: An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
Dependencies
This dependencies section is constrained to the same inspected scope: Defines input, output, and code artifact roles; validates deterministic ordering, uniqueness, byte counts, and SHA-256 commitments.
It must preserve the recorded boundary: An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
Questions this page can answer
What is implemented?
Runtime Witness Receipts — Artifact Role Inventory is implemented as a source-bounded artifact role inventory guide.
Which exact locator proves it?
Computational witness receipt artifact-role verifier, lib/evidence-dossier/runtime-witness.ts — artifacts: and verifyComputationalWitnessReceipt
What fails closed?
An artifact inventory proves receipt structure and commitments, not scientific validity, independent reproduction, or completeness of the execution environment.
What does the implementation not establish?
applies-to: urn:maha:concept:evidence:runtime-witness-receipts governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence
Which release gates remain?
A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.