# Independent review request: EM-TEC-04 Environment, Infrastructure and Service Instance

Review this boundary independently. Proposed: complete reserved WM-SFT-010 as Runtime / Compute Environment, owning RuntimeEnvironment, InfrastructureResource, DeployedInstance and temporal HostingRelation. Keep WM-SFT-002 as logical system/application and WM-SFT-009 as deployment occurrence. Reuse WM-XCT-039 only for mastership and impact projections. Treat ConfigurationItem as an effective-dated control designation over a referenced subject, and keep physical/financial assets in separate masters linked by evidence. Use non-recycled keys and tombstones for ephemeral history; addresses are observations, not identities. A logical cluster keeps identity while node membership changes. Test one service across two regions with node replacement and as-of impact queries. Return <=1200 words: Verdict; identity/mastership; environment/resource/instance/CI; hosting/topology; ephemeral history; asset boundary; cluster/node; scenario; invariants; blockers. Challenge whether DeployedInstance belongs in WM-SFT-010 and whether ConfigurationItem needs independent identity. Do not invent identifiers or claim canonical completeness.