Interface, API and integration
Interaction contract, interface version, integration link, endpoint binding and exchange. The data schema and the transport are not equal to the business agreement.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 9 questions
Contract and version The logical agreement between provider and consumer and its versions.
Interface contract
A logical contract kept apart from the physical address.
Contract scope
What the interface exposes, with its schema and semantics.
- Which operations, messages and data does the contract define?
- Which business agreement, if any, governs the exchange beyond the schema?
Version compatibility
Contract versions and whether changes are backward compatible.
- Which contract version does each consumer pin?
- Is the change backward compatible, and by which rule?
Binding and exchange Where the contract is reached and what actually flows.
Endpoint binding
A physical address bound to a contract for an environment and period.
Binding
An endpoint with its environment, period and contract version.
- Which environment and period does this endpoint binding cover?
- Did the address change while the contract stayed the same?
Integration and exchange
The integration link with direction, data and owners.
Integration link
The exchange between systems with direction, data and owners.
- Which direction does data flow, and who owns each side?
- Which dataset does the exchange carry, without duplicating it?
- Which migration action does a given change require of consumers?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseTEC
- Industry
- Cross-industry
- Tags
- EM-TEC-03W1subjectInterfaceContractAPIVersionIntegrationEndpointBindingExchangeEvent
What it is Filled
Interaction contract, interface version, integration link, endpoint binding and exchange. The data schema and the transport are not equal to the business agreement.
Why it exists Filled
Interaction contract, interface version, integration link, endpoint binding and exchange. The data schema and the transport are not equal to the business agreement.
Distinguishing features Filled
- The logical contract and the physical endpoint are separate; an address change is not a new integration.
- Consumers pin a contract version, so incompatible changes are detectable.
- An integration describes a flow and does not become a copy of the dataset it carries.
- Distinct from the business agreement between parties, which the schema and transport do not replace.
What robots and AI may and may not do Filled
Must not
- Treat a new API URL as a new business integration regardless of meaning.
- Retire a contract version still pinned by a consumer without notice.
- Register an integration as a duplicate of the dataset it carries.
- Call an external endpoint with production data without authorisation.
- Put credentials or tokens into an interface record.
Only with a human decision
- Approving incompatible contract changes.
- Opening an interface to an external party.
May
- Classify a change as address-only, compatible or incompatible.
- List consumers pinned to a contract version that is being retired.
- Draw the exchange map with directions and owners.
Moral aspects Filled
- Interfaces often carry personal data, so each flow needs a known owner and purpose.
- Breaking changes can disrupt services that people rely on.
Who is affected
- Provider and consumer teams
- Data subjects whose data flows
- External partners
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-TEC-02
- EM-TEC-04
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a contract identifier and version; endpoint bindings by address, environment and validity period.
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 contract, a version, an endpoint, an environment or an exchange direction.
- Often confused with the URL alone or with the commercial agreement.
Capabilities and actions required Filled
- Compatibility rules let consumers plan migrations.
- Exchange maps support data protection and impact analysis.
Hazards and failure modes required Filled
- Silent breaking changes that reach consumers in production.
- Undocumented flows of personal data between systems.
- Orphaned endpoints that remain open after their contract is retired.
Standards and interfaces required Filled
- OpenAPI Specification from the OpenAPI Initiative.
- AsyncAPI specification for event-driven interfaces.
- CNCF CloudEvents for event metadata.
- IETF RFC 9110 HTTP Semantics.
Context of use required Filled
- Used by integration, platform and architecture teams.
- Applies to synchronous APIs, events, files and batch exchanges.
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
- OpenAPI Specification 3.1.0 - Checked live (HTTP 200) on 2026-10-07.
- OpenTelemetry Specification - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to separate the logical contract and the physical address?
- Which changes are backward compatible?
- How to represent the direction, the data and the owners of the exchange?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-tec-03/brief.json, ver-cy/world-models/card-supplements/em-tec-03.json
Still in Russian: suggested owner, blocking decisions. Translate in research/enterprise/i18n/units.en.json.