Software product and AISMM engineering context
Software identity, architecture, components, repositories, builds, releases and delivered artifacts. Research delegation to specialized models within the full AISMM product context.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 6 findings · 13 questions
Product and composition This bundle records product identity, composition, architecture and delegation boundaries.
Product identity
This layer identifies the product boundary and the records responsible for its component facts.
Product boundary
This finding distinguishes a product from its delivery profiles and deployments.
- Which software product does this record identify, and which delivery profiles does it offer?
- Does this product record incorrectly establish a separate product solely for a deployment region or tenant?
Components and repositories
This finding links product composition to repositories and authoritative records.
- Which repositories hold the source for this component?
- Which authoritative record owns the fact referenced by this component record?
Architecture and delegation
This layer records architectural context and explicit delegation of specialized research and engineering detail.
Product architecture
This finding identifies the architecture description and the decisions governing product composition.
- Which architecture description defines the component boundaries, interfaces and dependencies of this product?
- Which rationale and constraints support this architecture decision?
Specialized model delegation
This finding identifies the specialized model responsible for a delegated concern and its relationship to the product context.
- Which specialized model identifier and version does this delegation record assign to its stated research or engineering concern?
- Which authoritative record and expected result references connect this delegation to the product context?
Build and release This bundle traces releases and delivered artifacts to their source and build records.
Release chain
This layer distinguishes release identity, deployment status and artifact identity.
Build and release
This finding connects a release to its production history without implying deployment.
- Which source revision and build produced this release?
- Does this release record distinguish its publication from any deployment of it?
Artifact identity
This finding records artifact membership, byte identity and component inventory references.
- Which artifacts and digests are recorded for this release?
- Which software bill of materials describes the components inside this artifact?
- Does this artifact record incorrectly use its digest to identify the product's meaning?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseTEC
- Industry
- Cross-industry
- Tags
- EM-TEC-01W1subjectSoftwareProductSoftwareComponentSourceRepositoryBuildRelease
What it is Filled
Software identity, architecture, components, repositories, builds, releases and delivered artifacts. Research delegation to specialized models within the full AISMM product context.
Why it exists Filled
Software identity, architecture, components, repositories, builds, releases and delivered artifacts. Research delegation to specialized models within the full AISMM product context.
Distinguishing features Filled
- A release is a published version, while a deployment is one running placement of it.
- One product keeps one identity across SaaS, library, on-prem, container and firmware profiles.
- An artifact digest identifies bytes, not the semantic version or meaning of the product.
- Distinct from the business application, which describes how an organisation uses software rather than how it is built.
What robots and AI may and may not do Filled
Must not
- Create a new software product for every regional deployment.
- Treat a release as deployed because it was published.
- Copy HR, incident or dataset facts into the product record.
- Publish a release or tag on its own initiative.
- Alter an artifact or its digest after release.
Only with a human decision
- Publishing or withdrawing a release.
- Changing the product boundary or merging products.
May
- Link a release to its builds, source revisions and artifacts.
- Report which SBOM covers a given artifact.
- Flag products that were duplicated per deployment region or tenant.
- Point to the owning record for HR, incident or dataset facts instead of copying them.
Moral aspects Filled
- Inaccurate component records hide supply chain risks from customers.
- Copying personal data such as HR facts into engineering records widens exposure.
Who is affected
- Customers and operators running the software
- Engineering teams
- Security responders
Owners Filled
Steward
The CTO, the CIO or the service owner accountable for the system.
Master systems
- Software catalogue
- Source control
- CI/CD pipeline
- CMDB
- Observability platform
Links to other meta-models Filled
neighbor
- EM-PRD-03
- EM-TEC-02
- EM-TEC-04
- EM-TEC-07
- EM-WRK-06
references
- WM-SFT-001 - conceptual-candidate
- AISMM - conceptual-candidate
- WM-SFT-007 - conceptual-candidate
- WM-SFT-003 - conceptual-candidate
- WM-SFT-008 - conceptual-candidate
- WM-SFT-009 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a stable product identifier; releases by semantic version and artifacts by cryptographic digest.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a product, a repository, a build, a release version or an artifact digest.
- Often confused with the deployed service instance or the business application.
Capabilities and actions required Filled
- Releases can be traced from artifacts back to source revisions.
- One product model serves several delivery profiles without duplication.
Hazards and failure modes required Filled
- Product sprawl when deployments are registered as products.
- Supply chain blind spots when SBOMs are missing or stale.
- Conflicting facts when the same data is copied into several models.
Standards and interfaces required Filled
- SPDX, ISO/IEC 5962, for software bills of materials.
- OWASP CycloneDX for software bills of materials.
- ISO/IEC/IEEE 42010 for architecture description.
Context of use required Filled
- Used by engineering, release management and product security teams.
- Detailed engineering context is delegated to specialised software product models.
Sources Filled
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
- SPDX Specification 2.3 - Checked live (HTTP 200) on 2026-10-07.
- OpenTelemetry Specification - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How are WM-SFT-001 and AISMM related without a second product?
- What does AISMM 3.2.0 change relative to runtime 3.1.0?
- How is the common meaning preserved for SaaS, library, on-prem, container and firmware?
- Согласовать runtime и repository версии AISMM/PLMM и роль ELMM; совместимость сейчас не доказана.
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-tec-01/brief.json, ver-cy/world-models/card-supplements/em-tec-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.