# Independent review request: EM-TEC-01 Software Product and AISMM Context

Review this boundary independently. Proposed: narrow WM-SFT-001 to Software Product identity/classification/support; bind AISMM 3.1.0 as an aligned product-knowledge/context specification, never a second product master; use WM-SFT-007 for components/packages, WM-SFT-008 for build/release/artifact provenance, WM-SFT-009 for deployments, complete missing WM-SFT-003 for interface contracts, reference WM-SFT-012 for SBOM documents, and create one identifier-unassigned Source Repository candidate. Remove duplicated child facts from WM-SFT-001. Test SaaS, library, on-prem, container and firmware; one product with multiple repositories; no copied HR/incident/dataset facts. The available AISMM repo is 3.1.0 and contains no evidenced 3.2.0. Return <=1200 words: Verdict; product/AISMM relationship; fact mastership; build/release/artifact/SBOM; deployment; delivery profiles; version finding; invariants; blockers. Do not invent identifiers or claim canonical completeness.