← Back to catalogue
Published

Technologies and architecture standards

EM-TEC-09 · em-tec-09

Technology catalog, adoption stages, architecture standard, adoption and conformance assessment. ADR reuses the decision model.

Enterprise profiles Enterprise subject EnterpriseTEC

Bundle → Layer → Finding → Questions Filled

2 bundles · 4 layers · 4 findings · 10 questions

Catalogue and standards Which technologies are known, at what adoption stage, and which standards govern their use.

Technology and adoption stage

A catalogued technology and the organisation's position on it.

Technology status

The adoption stage the organisation assigns, kept apart from vendor support.

  1. Which adoption stage does the catalogue assign to this technology, and since when?
  2. Is the stage an organisational decision or a vendor support status for a product version?
  3. Which decision record justifies the current stage?

Architecture standard

A versioned rule set with a declared scope.

Standard version and scope

The standard identified by version and the systems it applies to.

  1. Which version of the standard applies, and from which date?
  2. Which systems, domains or layers fall within its scope?
Assessment and exceptions Whether a given system conforms, on what evidence, and where deviation is allowed.

Conformance

An assessment of one system against one version of a standard.

Conformance assessment

A dated judgement with the evidence it rests on.

  1. Which system and which standard version were assessed, and by whom?
  2. What evidence supports each conformance criterion?
  3. Does the assessment still hold after the standard moved to a new version?

Exception

A bounded permission to deviate from a standard.

Architecture exception

A deviation with an owner, an expiry and a defined effect.

  1. Who owns the exception, and when does it expire?
  2. Which criteria and which systems does the exception cover, and nothing beyond them?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseTEC
Industry
Cross-industry
Tags
EM-TEC-09W2subjectTechnologyTechnologyAdoptionArchitectureStandardConformanceAssessmentArchitectureException

What it is Filled

Technology catalog, adoption stages, architecture standard, adoption and conformance assessment. ADR reuses the decision model.

Why it exists Filled

Technology catalog, adoption stages, architecture standard, adoption and conformance assessment. ADR reuses the decision model.

Distinguishing features Filled

  • Adoption of a technology and conformance to a standard are separate findings; using an approved tool says nothing about the whole system.
  • A standard always carries a version and a scope, so the same system can conform to one version and fail the next.
  • An organisation's adoption stage is its own decision and differs from the vendor's support status for a product version.
  • Distinct from the business application record, which describes what runs rather than the rules it should follow.

What robots and AI may and may not do Filled

Must not

  • Declare a system conformant because it uses a recommended language or platform.
  • Treat a conformance assessment without evidence as valid.
  • Extend an exception beyond the systems and criteria it names.
  • Change the adoption stage of a technology without a recorded decision.
  • Carry an assessment over to a new version of the standard without reassessment.

Only with a human decision

  • Approving a new version of an architecture standard.
  • Granting or renewing an architecture exception.
  • Retiring a technology that systems in production still depend on.

May

  • Report the adoption stage of a technology together with the decision that set it.
  • Compare a system's recorded components against a named version of a standard.
  • Flag architecture exceptions that are expired or have no owner.
  • List systems affected when a standard moves to a new version.

Moral aspects Filled

  • Unchecked conformance claims can hide security and continuity weaknesses from those accountable for them.
  • Permanent exceptions shift risk onto teams and users who never agreed to carry it.

Who is affected

  • Engineering teams bound by the standard
  • Service owners and operators
  • Users of the affected systems

Owners Filled

Steward

The chief technology or information officer, or the service owner, who answers for architecture decisions.

Master systems

  • Software catalogue
  • Source code repository
  • CI/CD pipeline
  • Configuration management database
  • Observability platform

Links to other meta-models Filled

neighbor

  • EM-TEC-02 - Business applications and systems are the subjects of conformance assessments.
  • EM-KNW-02 - Architecture decision records reuse the decision, claim and evidence model.
  • EM-LEG-03 - Architecture exceptions follow the same bounded pattern as internal policy exceptions.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A standard is identified by its own identifier and version; an assessment by system, standard version and date.
  • A technology is identified by its catalogue entry, independent of any single product version.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • An assessment names one system, one standard version and the evidence it used.
  • Often confused with a product support lifecycle or with a technology radar entry alone.

Capabilities and actions required Filled

  • Conformance can be recomputed for every system when a standard changes version.
  • Exceptions can be listed by owner and expiry for periodic review.

Hazards and failure modes required Filled

  • False assurance when adoption of one component is reported as conformance of the whole system.
  • Exceptions that never expire and silently become the real standard.
  • Stale assessments that refer to a superseded version of the standard.

Standards and interfaces required Filled

  • ISO/IEC/IEEE 42010 for architecture descriptions.
  • ArchiMate modelling language from The Open Group.
  • SPDX from the Linux Foundation, published as ISO/IEC 5962, for software component inventories.

Context of use required Filled

  • Used by architecture boards and engineering governance in organisations with many systems.
  • Feeds security reviews, technology lifecycle planning and audit of IT controls.

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
  4. SPDX Specifications - Checked live (HTTP 200) on 2026-10-07.
  5. OpenTelemetry Specifications - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to distinguish a technology status from product version support?
  • Why does adoption not prove conformance?
  • How to limit the effect of an architecture exception?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-tec-09/brief.json, ver-cy/world-models/card-supplements/em-tec-09.json

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