EM-TEC-09 · Subject model · W2
Technologies and architecture standards
Technology catalog, adoption stages, architecture standard, adoption and conformance assessment. ADR reuses the decision model.
Partially published; research continues
Claude: complete-initial-study-plus-single-frozen-audit-remediated; Grok: complete-reconciled-visible-response-provider-truncated.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- Technology
- TechnologyAdoption
- ArchitectureStandard
- ConformanceAssessment
- ArchitectureException
Deep research 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?
Verifiable invariants
- A standard has a version and a scope
- An assessment contains evidence
- An exception has an expiry and an owner
End-to-end acceptance scenario
Two versions of a standard, an assessment of one application and a temporary exception yield different adoption and conformance statuses.
Negative case
Using a recommended language proves the whole system conforms to the architecture standard.
Approaches to compare
- 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
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.