# EM-TEC-01 provider comparison

Claude and Grok agree on the complete boundary: narrow WM-SFT-001 to durable Software Product identity/classification/offering/support; bind AISMM 3.1.0 as an aligned context specification; master component/package in WM-SFT-007, build/release/artifact in WM-SFT-008, deployment in WM-SFT-009 and SBOM documents in WM-SFT-012; defer interface ownership until WM-SFT-003 has a usable specification; and create one identifier-unassigned Source Repository candidate.

Both require removal of duplicated child facts from WM-SFT-001, exact immutable repository revisions for builds, separate artifact digest versus semantic fingerprint, one product with many repositories, and reference-only HR/incident/dataset facts. Both find AISMM 3.2.0 unevidenced and pin the available source to 3.1.0.

The reconciled profile treats WM-SFT-003 as a pending neighbour rather than a base, WM-SFT-012 as a referenced document master, and all five delivery profiles as unexercised acceptance fixtures. No identifier or publication readiness is claimed.