Installation and Handover Record

An IHR is one continuously maintained record covering requirements and readiness, a reproducible execution plan, actual commands, as-built state, technical verification, operational handover, and customer acceptance.

Its machine lifecycle is draft → requirements-shared → ready-for-installation → implementation-in-progress → technically-completed → customer-ready → handed-over → accepted. Readiness approval is not final acceptance.

The metadata language is a BCP-47 tag. Concrete documents translate visible headings and prose but preserve neutral lifecycle values and technical identifiers. Planned Execution must contain complete, tested commands and safe restart boundaries before installation. Actual Execution Record later captures what really ran, immutable references, recaps, idempotency, evidence, and any documented deviations.

Platform services such as name resolution, time synchronisation, package sources, proxy, trust stores, routing, and base networking are assessed in a compact baseline table. They are product-flow rows only when a commissioned or customer-specific connection requires that detail.