HSIMC · UN Six-Language White Paper · P6 / W0-017

Appendix E - Reference Engineering and Acceptance Roadmap

E.1 - 0. Problem and Work definition

Question answered: Demand, Authority, acceptance, baseline and responsible parties are explicit.

Minimum evidence: Versioned Work brief.

E.2 - 1. Documented

Question answered: Source documents support a possible capability.

Minimum evidence: Document hash, profile, conflicts/unknowns.

E.3 - 2. Simulated

Question answered: Contract works in a controlled simulator with no physical effect.

Minimum evidence: Test vectors, receipts and deterministic errors.

E.4 - 3. Remote simulated

Question answered: A remote client reaches the simulator through the intended route.

Minimum evidence: Route, client, protocol/runtime and remote receipts.

E.5 - 4. Physical reference

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.

E.6 - 5. Configuration freeze

Question answered: Hardware, image/runtime, adapters, contracts and test pack are fixed for shipment.

Minimum evidence: Freeze manifest and recovery procedure.

E.7 - 6. Physical delivered

Question answered: Delivered instance is bound and reproduces acceptance at destination.

Minimum evidence: Delivered identity, installation, local test and handover.

E.8 - 7. Operational

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.

E.9 - 8. Independent reproduction

Question answered: Second team/location reproduces the agreed function.

Minimum evidence: Reproduction time, deviations, clarification count and comparative evidence.

E.10 Configuration freeze

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.

E.11 Shipping rule

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.

E.12 Local operation

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.

E.13 Second-site reproduction

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.