← Back to catalogue
Research draft

Software product and AISMM engineering context

EM-TEC-01 · em-tec-01

Software identity, architecture, components, repositories, builds, releases and delivered artifacts. Research delegation to specialized models within the full AISMM product context.

Enterprise profiles Enterprise subject EnterpriseTEC

Research draft, second pass

A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.

Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Missing, in the backlog

Not described yet. This gap is in the card backlog.

Note: Research contour: bundles not designed yet; questions are listed as open questions.

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 Derived, awaiting review

  • A release is not equal to a deployment
  • An artifact digest is not the model's semantic fingerprint
  • Internals have a single owner of the fact

What robots and AI may and may not do Derived, awaiting review

Must not

  • Negative case: Every regional deploy creates a new SoftwareProduct.

Note: Negative case of the research brief, not yet a rule for agents.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

CTO / CIO / владелец сервиса

Master systems

  • Каталог ПО
  • Git
  • CI/CD
  • CMDB
  • observability

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 Incomplete

Identity and identifiers required Derived, awaiting review

  • SoftwareProduct
  • SoftwareComponent
  • SourceRepository
  • Build
  • Release
  • SoftwareArtifact
  • SBOMReference

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Hazards and failure modes required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Context of use required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Sources Filled

  1. AISMM/WM-SFT and ArchiMate: product, system and architecture
  2. CSDM: business application, service and runtime instance
  3. SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary

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

Card as JSON Source Card backlog vercy.card/1

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-tec-01/brief.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.