Open a permitted run
Obtain a scoped run ID and role token from the operator. Credentials remain only in memory.
Run and role
Verify a signed packet offline
- Download this permitted packet. It contains synthetic run evidence; preserve it only in an approved location.
- Obtain the issuer public-key digest and candidate identity from the operator through an independently trusted channel. The public key embedded in the packet is not sufficient trust.
- Obtain the reviewed Python verifier and its cryptography dependency from the candidate package. Run
python scripts/verify-lab-run.py observatory-permitted-packet.json --trusted-key-id sha256:PUBLIC_KEY_DIGEST, substituting the independently supplied digest. - Preserve the packet, key pin, candidate identity and verifier output. PASS establishes the declared integrity/replay checks, not substantive truth, fairness, advisor acceptance or full profile qualification. Report FAIL, missing evidence and unavailable verification as observed.
The presentation never grants permission. Both views use the same captured records and backend protections.
Decision evidence
Captured sources and context
Governed workflow
Use separate role credentials for each step. Select the exact record references; an earlier approval cannot stand in for a correction.
Preserve a reviewer finding
Reports remain in the run history. Submitting a report does not approve the system or assert conformance.
Proposed scenario protocol
P04 has 24 declarative matched pairs. Runtime execution coverage must be reported separately. Manual screen-reader sessions, human takeover and workload trials remain UNEVALUATED until actually conducted.
Task burden notebook
Optional, local-only observations. No automatic participant tracking. Save only synthetic dry runs or observations within explicitly agreed participant consent. Downloads contain what you enter; clear them at logout.
No observations; denominator 0.