Direct answer
Runtime Witness Receipts — Verification describes the bounded Maha behavior established by the cited implementation and carries the implementation's explicit non-claims.
Answer contract
Apply the verification lens only to the exact inspected source scope; do not infer authority from adjacent topics.
Evidence and exact locators
t19-runtime-verifier — lib/evidence-dossier/runtime-witness.ts — verifyComputationalWitnessReceipt. Supports: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
What the evidence does not establish
A clean structural verification does not validate the computation or its inputs.
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
Inputs and prerequisites
This inputs and prerequisites section is constrained to the same inspected scope: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
It must preserve the recorded boundary: A clean structural verification does not validate the computation or its inputs.
Ordered behavior
This ordered behavior section is constrained to the same inspected scope: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
It must preserve the recorded boundary: A clean structural verification does not validate the computation or its inputs.
Verification or refusal states
This verification or refusal states section is constrained to the same inspected scope: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
It must preserve the recorded boundary: A clean structural verification does not validate the computation or its inputs.
What this does not establish
This what this does not establish section is constrained to the same inspected scope: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
It must preserve the recorded boundary: A clean structural verification does not validate the computation or its inputs.
Related definition and applications
This related definition and applications section is constrained to the same inspected scope: Checks required receipt fields, hashes, timestamps, status, seeds, and artifacts.
It must preserve the recorded boundary: A clean structural verification does not validate the computation or its inputs.
Questions this page can answer
What exact behavior is implemented?
Runtime Witness Receipts — Verification 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-runtime-verifier, lib/evidence-dossier/runtime-witness.ts — verifyComputationalWitnessReceipt
Which exact symbol bears the explanation?
A clean structural verification does not validate the computation or its inputs.
Which refusal or verification boundary applies?
applies-to: urn:maha:concept:evidence:runtime-witness-receipts 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.