Evidence
Read the documented local results with their dates, scope, and limitations.
Documented results and their scope.
Revision 3 documents the local results below, dated 24 October 2026. They are reported test outcomes; independent reproduction and verification have not been established.
| Population | Recorded result | Scope and limit |
|---|---|---|
| Application authorization | 9/9 declared cases | Own-record and permitted-export controls plus declared denials. The application owns enforcement. |
| Interactive C assessment | 5/5 scenario checks | Clean, dispatch fault, evidence gap, request misbinding and absent process. Numeric checks remain regression-grade. |
| Reporting protocol | 23 tests passed | Real local TLS/HTTP with synthetic assessment facts; parser, trust, binding and failure checks. |
| C-to-HTTP reporting | 5/5 cases passed | Actual frozen C adapter in applicable cases. Recipient sees monitor or absence as declared; expected failures expose no usable assessment. |
| Reporting-run integrity | 30 listed hashes matched | Documented local shasum output, exit 0. Matching a manifest does not authenticate producers or prove correctness. |
| Formal engine acceptance | Last recorded: 0/48 accepted | Revision 3 includes no updated authoritative acceptance register. These demonstration results do not establish formal engine acceptance. |
These partly overlapping populations are neither a defense percentage nor a combined engine acceptance score. A successful failure check does not mean an assessment succeeded.
Evidence provenance and reproducibility
The reported C-to-HTTP run is action-reporting-7989jd_h/report.json. Revision 3 records terminal output showing 5/5 and exit 0; the complete report is not included in the cited Revision 3 evidence. Its SHA256SUMS output listed 30 matches.
The expiry-test correction used a certificate valid from 1–2 January 2020. The corrected protocol suite reported 23 tests passed. This changed the test fixture, not the engine or reporting implementation; the revised test has a separate hash from the original package.
Evidence source: Demo implementation and design review, Revision 3, 24 October 2026. This page summarizes its reported results. The underlying review document and complete run artifacts are not distributed here; this limits independent reproduction from the website alone.