Formal Protocol Verification Run Output and Evidence

This page is generated from the AWS Linux blind-trial run evidence. The terminal transcript below is the actual output rendered into the matching screencast MP4, so instructors can compare the Response HTML and video without guessing.

Run Script Output Shown In Screencast

This is the recorded terminal output for Week 11. It is intentionally verbatim so it can be checked against the MP4 screencast.

===== Phase 11: formal verification and protocol conformance =====
172.30.0.10
200
phase11-summary GET /v1/formal/fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase11-device GET /v1/formal/fbc50d99-7b45-4568-afda-3d807bc8e3cd/172.30.0.10 -> HTTP 200
[
  "data",
  "status"
]
200
phase11-results GET /v1/formal/results?scan_id=fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase11-traces GET /v1/formal/traces?scan_id=fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]
200
phase11-conformance GET /v1/formal/conformance?scan_id=fbc50d99-7b45-4568-afda-3d807bc8e3cd -> HTTP 200
[
  "data",
  "status"
]

Endpoint Status Output

These status files came from the same remote evidence bundle. They are listed separately so students can see which API calls completed successfully without publishing raw credential examples.

Evidence Files Produced By The Run

The response page records the actual evidence inventory and file shapes from docs/final/lab-material/run-evidence/aws-8414-20260517T152520Z/remote-evidence/phase-json. JSON values that may contain credential examples are summarized rather than published raw.