ot-asset-ownership-governancelisted

## When to Use - Establishing asset ownership where no one is accountable per class. - Resolving ownership disputes between IT and OT after a convergence project. - Fixing a governance gap surfaced by an incident where no one could authorize action. - Assigning lifecycle sign-off for aging or end-of-life assets. ## Prerequisites - Asset inventory by class: controllers, HMIs, EWS, network devices, historians, DMZ services, SIS. - Organization chart with named roles. - The change management design, so ownership aligns with approval gates. - Current access review process, if any. - Credentials: none. This skill produces design documents. - Authorization: an accountable executive signs the ownership matrix. Without one name at the top, ownership records are unenforceable. - Upstream skills: `passive-ot-network-discovery` for the asset inventory, `ot-change-management-workflow` for approval alignment. ### Safety This skill is passive. It produces assessment and governance documents only. ## Workflow 1. Ownership matrix decision. Requirement: every asset class has one named owner. Anchor: CM-8, 62443-2-1 4.3.2.2. Decision: owners are per class, not per device: controllers and their logic, HMIs, EWS, network devices, historians, DMZ services, and SIS. Each class names one operational owner and one security counterpart. Trade-off accepted: per-class ownership can disagree with per-site operations structures. The alternative is per-device ownership that scales to hundreds of ro