Reading a result envelope

Software result

A run records the archived source hash, input SHA-256, result SHA-256, elapsed website execution time and the explicit evidence class. Timings include adapter overhead and are not semiconductor measurements.

{
  "release": {"version": "1.2.0", "source_sha256": "..."},
  "input_sha256": "...",
  "result_sha256": "...",
  "evidence_class": "EXECUTED_SOFTWARE_ON_SYNTHETIC_SCENARIO"
}

Verify bytes

For a delivered archive, hash the bytes and compare with the manifest. For the JSON input and result, use sorted keys and compact separators, matching the adapter.

python -c "import hashlib,pathlib; p=pathlib.Path('release.zip'); print(hashlib.sha256(p.read_bytes()).hexdigest())"

Separate the claims

Canonical architecture, source implementation, executable-model results, physical signoff and measured silicon are different records. The website preserves that distinction. A website test report only establishes website behavior.