Question answered: Demand, Authority, acceptance, baseline and responsible parties are explicit.
Minimum evidence: Versioned Work brief.
Question answered: Source documents support a possible capability.
Minimum evidence: Document hash, profile, conflicts/unknowns.
Question answered: Contract works in a controlled simulator with no physical effect.
Minimum evidence: Test vectors, receipts and deterministic errors.
Question answered: A remote client reaches the simulator through the intended route.
Minimum evidence: Route, client, protocol/runtime and remote receipts.
Question answered: A bound reference device performs limited real observations/actions under controlled conditions.
Minimum evidence: Physical Resource ID, BOM/OS/driver, test results and stop/recovery evidence.
Question answered: Hardware, image/runtime, adapters, contracts and test pack are fixed for shipment.
Minimum evidence: Freeze manifest and recovery procedure.
Question answered: Delivered instance is bound and reproduces acceptance at destination.
Minimum evidence: Delivered identity, installation, local test and handover.
Question answered: The system completes real Work over a defined period with incident and value records.
Minimum evidence: Operational log, outcomes, cost/value, maintenance and incidents.
Question answered: Second team/location reproduces the agreed function.
Minimum evidence: Reproduction time, deviations, clarification count and comparative evidence.
A freeze is not merely a filename. It should bind at least hardware revision/BOM, image or OS, runtime, driver set, adapter versions, capability contracts, application version, calibration, test pack, known limitations, recovery method and evidence hashes.
Ship after the reference configuration has passed the intended pre-shipment acceptance. Shipping does not turn the reference identity into the delivered identity. The delivered unit receives its own Resource identity and local binding record.
Where the use case requires local continuity, basic operation and safe stop/recovery should not depend on a permanently open cloud session. Cloud services can coordinate, update and collect evidence without becoming an invisible single point of control for every real-time physical behavior.
The second site returns not only pass/fail but also time to reproduce, substitutions, environmental differences, hidden assumptions, questions asked, failed attempts and final evidence. These results are inputs to the next shared Profile.