Evidence class: Documented handoff
Boundary: Consolidates prior decisions/evidence; did not re-probe physical T736 or deploy firmware/device.
Evidence class: Documented
Boundary: Supplier-document review, pin/interface mapping and conflicts; no new bench measurement.
Evidence class: Planned architecture
Boundary: Cloud simulation -> remote reference board -> freeze -> ship -> local bind/accept.
Evidence class: Simulated
Boundary: Simulator source and receipts; physical targets return unbound; does not prove hardware.
Evidence class: Remote simulated
Boundary: 14/14 recorded remote simulation checks; real 736 was unreachable in that record.
Evidence class: Published digital
Boundary: Digital publication/QR checks completed; physical print/NFC read-back deferred.
Evidence class: Published digital
Boundary: English summary HTML/PDF published and verified.
Evidence class: Published digital
Boundary: English Part I published and verified.
Evidence class: Published digital / current known public baseline
Boundary: English Part II published and verified.
Evidence class: Generated and archived
Boundary: Digital publication package prepared; remote deployment deferred.
Evidence class: Generated and archived
Boundary: Digital publication package prepared; remote deployment deferred.
Evidence class: Generated and archived
Boundary: Digital publication package prepared; remote deployment deferred.
Evidence class: Generated and archived
Boundary: Digital publication package prepared; remote deployment deferred.
Evidence class: Generated master
Boundary: Consolidates Parts I-VI plus front matter, Appendices A-H, glossary, source and version registers.
An operation receipt is evidence about a specific operation. A fresh observation is evidence about a current or recent state. The evidence object should carry observation time, receipt time, source, method, version and freshness limit so that a historical receipt is not silently treated as current state.
When evidence conflicts, preserve the conflict rather than silently reconciling it. A practical hierarchy is current physical measurement for the bound instance; current manufacturer/BOM-specific data; versioned engineering documentation; simulator behavior; design proposal. Different sources may answer different questions and therefore should not be forced into a single value without explanation.