AI Software Meta-Model

Product Passport

Defines the product as a distinct entity.

1. What is the product?
2. What is included in the product?
3. What is owned by the product and what is outside its responsibility?
4. What is explicitly excluded?
5. What external systems, platforms, actors, environments, and organizations surround it?
6. Which contextual entities must be referenced by other AISMM layers?
7. What is the current, in-scope definition of Product Passport?
8. Which entities, identifiers, attributes and relationships constitute Product Passport?
9. Which source or master system is authoritative for Product Passport?
10. Who owns, validates and updates Product Passport, and when was it last verified?

Product Scope

Defines what is included in the product.

1. What is the product?
2. What is included in the product?
3. What is owned by the product and what is outside its responsibility?
4. What is the current, in-scope definition of Product Scope?
5. Which entities, identifiers, attributes and relationships constitute Product Scope?
6. Which source or master system is authoritative for Product Scope?
7. Who owns, validates and updates Product Scope, and when was it last verified?

Out of Scope

Defines what is explicitly excluded from the product.

1. What is the current, in-scope definition of Out of Scope?
2. Which entities, identifiers, attributes and relationships constitute Out of Scope?
3. Which source or master system is authoritative for Out of Scope?
4. Who owns, validates and updates Out of Scope, and when was it last verified?

Product Modules

Defines high-level product modules or domains.

1. What is the product?
2. What is included in the product?
3. What is owned by the product and what is outside its responsibility?
4. What is the current, in-scope definition of Product Modules?
5. Which entities, identifiers, attributes and relationships constitute Product Modules?
6. Which source or master system is authoritative for Product Modules?
7. Who owns, validates and updates Product Modules, and when was it last verified?

External Context

Defines external entities that surround the product.

1. What external systems, platforms, actors, environments, and organizations surround it?
2. Which contextual entities must be referenced by other AISMM layers?
3. What is the current, in-scope definition of External Context?
4. Which entities, identifiers, attributes and relationships constitute External Context?
5. Which source or master system is authoritative for External Context?
6. Who owns, validates and updates External Context, and when was it last verified?

Channels and Interfaces

Defines major channels through which the product is used or integrated.

1. What is the current, in-scope definition of Channels and Interfaces?
2. Which entities, identifiers, attributes and relationships constitute Channels and Interfaces?
3. Which source or master system is authoritative for Channels and Interfaces?
4. Who owns, validates and updates Channels and Interfaces, and when was it last verified?

Environments

Defines environments relevant for understanding product boundaries.

1. What external systems, platforms, actors, environments, and organizations surround it?
2. What is the current, in-scope definition of Environments?
3. Which entities, identifiers, attributes and relationships constitute Environments?
4. Which source or master system is authoritative for Environments?
5. Who owns, validates and updates Environments, and when was it last verified?

Ownership and Responsibility Boundaries

Defines who owns what.

1. What is owned by the product and what is outside its responsibility?
2. What is the current, in-scope definition of Ownership and Responsibility Boundaries?
3. Which entities, identifiers, attributes and relationships constitute Ownership and Responsibility Boundaries?
4. Which source or master system is authoritative for Ownership and Responsibility Boundaries?
5. Who owns, validates and updates Ownership and Responsibility Boundaries, and when was it last verified?

Boundary Rules

Defines explicit rules for deciding whether something belongs to the product.

1. What is the current, in-scope definition of Boundary Rules?
2. Which entities, identifiers, attributes and relationships constitute Boundary Rules?
3. Which source or master system is authoritative for Boundary Rules?
4. Who owns, validates and updates Boundary Rules, and when was it last verified?

Assumptions

Defines contextual assumptions that other layers may depend on.

1. What is the current, in-scope definition of Assumptions?
2. Which entities, identifiers, attributes and relationships constitute Assumptions?
3. Which source or master system is authoritative for Assumptions?
4. Who owns, validates and updates Assumptions, and when was it last verified?

Constraints

Defines contextual constraints that limit product design or evolution.

1. What is the current, in-scope definition of Constraints?
2. Which entities, identifiers, attributes and relationships constitute Constraints?
3. Which source or master system is authoritative for Constraints?
4. Who owns, validates and updates Constraints, and when was it last verified?

Context Domains

Defines logical grouping of context elements.

1. Which contextual entities must be referenced by other AISMM layers?
2. What is the current, in-scope definition of Context Domains?
3. Which entities, identifiers, attributes and relationships constitute Context Domains?
4. Which source or master system is authoritative for Context Domains?
5. Who owns, validates and updates Context Domains, and when was it last verified?

Value Chains

Define high-level chains of value creation.

1. What is the current, in-scope definition of Value Chains?
2. Which entities, identifiers, attributes and relationships constitute Value Chains?
3. Which source or master system is authoritative for Value Chains?
4. Who owns, validates and updates Value Chains, and when was it last verified?

Value Stream Segments

Define meaningful segments within value chains.

1. What is the current, in-scope definition of Value Stream Segments?
2. Which entities, identifiers, attributes and relationships constitute Value Stream Segments?
3. Which source or master system is authoritative for Value Stream Segments?
4. Who owns, validates and updates Value Stream Segments, and when was it last verified?

Entry and Exit Points

Define where value flows begin and where meaningful outcomes appear.

1. What is the current, in-scope definition of Entry and Exit Points?
2. Which entities, identifiers, attributes and relationships constitute Entry and Exit Points?
3. Which source or master system is authoritative for Entry and Exit Points?
4. Who owns, validates and updates Entry and Exit Points, and when was it last verified?

Value Elements

Define:

1. What is the current, in-scope definition of Value Elements?
2. Which entities, identifiers, attributes and relationships constitute Value Elements?
3. Which source or master system is authoritative for Value Elements?
4. Who owns, validates and updates Value Elements, and when was it last verified?

Converters

Define entities that transform value.

1. What is the current, in-scope definition of Converters?
2. Which entities, identifiers, attributes and relationships constitute Converters?
3. Which source or master system is authoritative for Converters?
4. Who owns, validates and updates Converters, and when was it last verified?

Value Flows

Define how value moves.

1. What is the current, in-scope definition of Value Flows?
2. Which entities, identifiers, attributes and relationships constitute Value Flows?
3. Which source or master system is authoritative for Value Flows?
4. Who owns, validates and updates Value Flows, and when was it last verified?

Participants

Define entities that:

1. What is the current, in-scope definition of Participants?
2. Which entities, identifiers, attributes and relationships constitute Participants?
3. Which source or master system is authoritative for Participants?
4. Who owns, validates and updates Participants, and when was it last verified?

Value Transformations

Describe:

1. What is the current, in-scope definition of Value Transformations?
2. Which entities, identifiers, attributes and relationships constitute Value Transformations?
3. Which source or master system is authoritative for Value Transformations?
4. Who owns, validates and updates Value Transformations, and when was it last verified?

Anti-Value Sources

Define:

1. What is the current, in-scope definition of Anti-Value Sources?
2. Which entities, identifiers, attributes and relationships constitute Anti-Value Sources?
3. Which source or master system is authoritative for Anti-Value Sources?
4. Who owns, validates and updates Anti-Value Sources, and when was it last verified?

Key Results

Define observable or measurable outcomes that confirm value delivery.

1. What is the current, in-scope definition of Key Results?
2. Which entities, identifiers, attributes and relationships constitute Key Results?
3. Which source or master system is authoritative for Key Results?
4. Who owns, validates and updates Key Results, and when was it last verified?

Metrics

Define measurable aspects:

1. What is the current, in-scope definition of Metrics?
2. Which entities, identifiers, attributes and relationships constitute Metrics?
3. Which source or master system is authoritative for Metrics?
4. Who owns, validates and updates Metrics, and when was it last verified?

Stakeholders

For each stakeholder:

1. What is the current, in-scope definition of Stakeholders?
2. Which entities, identifiers, attributes and relationships constitute Stakeholders?
3. Which source or master system is authoritative for Stakeholders?
4. Who owns, validates and updates Stakeholders, and when was it last verified?

Roles

Define all roles used by stakeholders.

1. What is the current, in-scope definition of Roles?
2. Which entities, identifiers, attributes and relationships constitute Roles?
3. Which source or master system is authoritative for Roles?
4. Who owns, validates and updates Roles, and when was it last verified?

Goals

For each goal:

1. What is the current, in-scope definition of Goals?
2. Which entities, identifiers, attributes and relationships constitute Goals?
3. Which source or master system is authoritative for Goals?
4. Who owns, validates and updates Goals, and when was it last verified?

Motivations

Describe:

1. What is the current, in-scope definition of Motivations?
2. Which entities, identifiers, attributes and relationships constitute Motivations?
3. Which source or master system is authoritative for Motivations?
4. Who owns, validates and updates Motivations, and when was it last verified?

Expectations and Success Criteria

Define:

1. What is the current, in-scope definition of Expectations and Success Criteria?
2. Which entities, identifiers, attributes and relationships constitute Expectations and Success Criteria?
3. Which source or master system is authoritative for Expectations and Success Criteria?
4. Who owns, validates and updates Expectations and Success Criteria, and when was it last verified?

Change Drivers

Define:

1. What is the current, in-scope definition of Change Drivers?
2. Which entities, identifiers, attributes and relationships constitute Change Drivers?
3. Which source or master system is authoritative for Change Drivers?
4. Who owns, validates and updates Change Drivers, and when was it last verified?

Value Perception

Define:

1. What is the current, in-scope definition of Value Perception?
2. Which entities, identifiers, attributes and relationships constitute Value Perception?
3. Which source or master system is authoritative for Value Perception?
4. Who owns, validates and updates Value Perception, and when was it last verified?

Relationships

Define:

1. What is the current, in-scope definition of Relationships?
2. Which entities, identifiers, attributes and relationships constitute Relationships?
3. Which source or master system is authoritative for Relationships?
4. Who owns, validates and updates Relationships, and when was it last verified?

Domains

identifier - description - capabilities - services - ownership

1. What is the current, in-scope definition of Domains?
2. Which entities, identifiers, attributes and relationships constitute Domains?
3. Which source or master system is authoritative for Domains?
4. Who owns, validates and updates Domains, and when was it last verified?

Capabilities

identifier - description - domain - related entities - supported functions

1. What is the current, in-scope definition of Capabilities?
2. Which entities, identifiers, attributes and relationships constitute Capabilities?
3. Which source or master system is authoritative for Capabilities?
4. Who owns, validates and updates Capabilities, and when was it last verified?

Business Functions

identifier - description - domain - related capabilities

1. What is the current, in-scope definition of Business Functions?
2. Which entities, identifiers, attributes and relationships constitute Business Functions?
3. Which source or master system is authoritative for Business Functions?
4. Who owns, validates and updates Business Functions, and when was it last verified?

Business Services

identifier - description - provided capability - inputs/outputs (conceptual) - consumers

1. What is the current, in-scope definition of Business Services?
2. Which entities, identifiers, attributes and relationships constitute Business Services?
3. Which source or master system is authoritative for Business Services?
4. Who owns, validates and updates Business Services, and when was it last verified?

Business Entities

identifier - description - role in business logic

1. What is the current, in-scope definition of Business Entities?
2. Which entities, identifiers, attributes and relationships constitute Business Entities?
3. Which source or master system is authoritative for Business Entities?
4. Who owns, validates and updates Business Entities, and when was it last verified?

Roles

identifier - description - related services

1. What is the current, in-scope definition of Roles?
2. Which entities, identifiers, attributes and relationships constitute Roles?
3. Which source or master system is authoritative for Roles?
4. Who owns, validates and updates Roles, and when was it last verified?

Ownership

ownership zones - responsibilities - shared ownership rules

1. What is the current, in-scope definition of Ownership?
2. Which entities, identifiers, attributes and relationships constitute Ownership?
3. Which source or master system is authoritative for Ownership?
4. Who owns, validates and updates Ownership, and when was it last verified?

Relationships

Define:

1. What is the current, in-scope definition of Relationships?
2. Which entities, identifiers, attributes and relationships constitute Relationships?
3. Which source or master system is authoritative for Relationships?
4. Who owns, validates and updates Relationships, and when was it last verified?

Critical Steps

identifier - description - role in value creation

1. What is the current, in-scope definition of Critical Steps?
2. Which entities, identifiers, attributes and relationships constitute Critical Steps?
3. Which source or master system is authoritative for Critical Steps?
4. Who owns, validates and updates Critical Steps, and when was it last verified?

Sequence Definition

ordered list of steps

1. What is the current, in-scope definition of Sequence Definition?
2. Which entities, identifiers, attributes and relationships constitute Sequence Definition?
3. Which source or master system is authoritative for Sequence Definition?
4. Who owns, validates and updates Sequence Definition, and when was it last verified?

Dependencies

step dependencies

1. What is the current, in-scope definition of Dependencies?
2. Which entities, identifiers, attributes and relationships constitute Dependencies?
3. Which source or master system is authoritative for Dependencies?
4. Who owns, validates and updates Dependencies, and when was it last verified?

Inputs and Outputs

consumed inputs - produced outputs

1. What is the current, in-scope definition of Inputs and Outputs?
2. Which entities, identifiers, attributes and relationships constitute Inputs and Outputs?
3. Which source or master system is authoritative for Inputs and Outputs?
4. Who owns, validates and updates Inputs and Outputs, and when was it last verified?

Value Mapping

value transformation per step

1. What is the current, in-scope definition of Value Mapping?
2. Which entities, identifiers, attributes and relationships constitute Value Mapping?
3. Which source or master system is authoritative for Value Mapping?
4. Who owns, validates and updates Value Mapping, and when was it last verified?

Bottlenecks

known constraints

1. What is the current, in-scope definition of Bottlenecks?
2. Which entities, identifiers, attributes and relationships constitute Bottlenecks?
3. Which source or master system is authoritative for Bottlenecks?
4. Who owns, validates and updates Bottlenecks, and when was it last verified?

Failure Handling

what happens on failure - retry / fallback / escalation

1. What is the current, in-scope definition of Failure Handling?
2. Which entities, identifiers, attributes and relationships constitute Failure Handling?
3. Which source or master system is authoritative for Failure Handling?
4. Who owns, validates and updates Failure Handling, and when was it last verified?

Degraded Routes

alternative execution paths - reduced value scenarios

1. What is the current, in-scope definition of Degraded Routes?
2. Which entities, identifiers, attributes and relationships constitute Degraded Routes?
3. Which source or master system is authoritative for Degraded Routes?
4. Who owns, validates and updates Degraded Routes, and when was it last verified?

Recovery Routes

how system returns to normal

1. What is the current, in-scope definition of Recovery Routes?
2. Which entities, identifiers, attributes and relationships constitute Recovery Routes?
3. Which source or master system is authoritative for Recovery Routes?
4. Who owns, validates and updates Recovery Routes, and when was it last verified?

Continuity Contracts

guarantees of value delivery

1. What is the current, in-scope definition of Continuity Contracts?
2. Which entities, identifiers, attributes and relationships constitute Continuity Contracts?
3. Which source or master system is authoritative for Continuity Contracts?
4. Who owns, validates and updates Continuity Contracts, and when was it last verified?

Revenue Streams

identifier - description - pricing model - driver

1. What is the current, in-scope definition of Revenue Streams?
2. Which entities, identifiers, attributes and relationships constitute Revenue Streams?
3. Which source or master system is authoritative for Revenue Streams?
4. Who owns, validates and updates Revenue Streams, and when was it last verified?

Cost Structure

identifier - description - category - driver

1. What is the current, in-scope definition of Cost Structure?
2. Which entities, identifiers, attributes and relationships constitute Cost Structure?
3. Which source or master system is authoritative for Cost Structure?
4. Who owns, validates and updates Cost Structure, and when was it last verified?

Drivers

cost drivers - revenue drivers

1. What is the current, in-scope definition of Drivers?
2. Which entities, identifiers, attributes and relationships constitute Drivers?
3. Which source or master system is authoritative for Drivers?
4. Who owns, validates and updates Drivers, and when was it last verified?

Unit Economics

per unit metrics - margins

1. What is the current, in-scope definition of Unit Economics?
2. Which entities, identifiers, attributes and relationships constitute Unit Economics?
3. Which source or master system is authoritative for Unit Economics?
4. Who owns, validates and updates Unit Economics, and when was it last verified?

Constraints

budget limits - cost ceilings - pricing constraints

1. What is the current, in-scope definition of Constraints?
2. Which entities, identifiers, attributes and relationships constitute Constraints?
3. Which source or master system is authoritative for Constraints?
4. Who owns, validates and updates Constraints, and when was it last verified?

Guardrails

acceptable thresholds - limits for decisions

1. What is the current, in-scope definition of Guardrails?
2. Which entities, identifiers, attributes and relationships constitute Guardrails?
3. Which source or master system is authoritative for Guardrails?
4. Who owns, validates and updates Guardrails, and when was it last verified?

Economic Impact

change impact - initiative impact - scenario analysis

1. What is the current, in-scope definition of Economic Impact?
2. Which entities, identifiers, attributes and relationships constitute Economic Impact?
3. Which source or master system is authoritative for Economic Impact?
4. Who owns, validates and updates Economic Impact, and when was it last verified?

Subject Domain

id, name, scope, why it matters to the product - maturity / stability of domain knowledge - SME owner reference

1. What is the current, in-scope definition of Subject Domain?
2. Which entities, identifiers, attributes and relationships constitute Subject Domain?
3. Which source or master system is authoritative for Subject Domain?
4. Who owns, validates and updates Subject Domain, and when was it last verified?

Domain Concepts and Terms

id, name, real-world definition - synonyms / disambiguation - canonical term link to b9.906

1. What is the current, in-scope definition of Domain Concepts and Terms?
2. Which entities, identifiers, attributes and relationships constitute Domain Concepts and Terms?
3. Which source or master system is authoritative for Domain Concepts and Terms?
4. Who owns, validates and updates Domain Concepts and Terms, and when was it last verified?

Domain Processes and Rules

id, description, real-world source - whether the product automates it (and where)

1. What is the current, in-scope definition of Domain Processes and Rules?
2. Which entities, identifiers, attributes and relationships constitute Domain Processes and Rules?
3. Which source or master system is authoritative for Domain Processes and Rules?
4. Who owns, validates and updates Domain Processes and Rules, and when was it last verified?

Authoritative References

id, title, source, url/file reference - authority class and freshness

1. What is the current, in-scope definition of Authoritative References?
2. Which entities, identifiers, attributes and relationships constitute Authoritative References?
3. Which source or master system is authoritative for Authoritative References?
4. Who owns, validates and updates Authoritative References, and when was it last verified?

Automation Mapping

automates links to b2.207 bounded contexts and b2.201 components - realizesdomainrule links to b4.402

1. What is the current, in-scope definition of Automation Mapping?
2. Which entities, identifiers, attributes and relationships constitute Automation Mapping?
3. Which source or master system is authoritative for Automation Mapping?
4. Who owns, validates and updates Automation Mapping, and when was it last verified?

Hypothesis

id - statement - rationale - businesssignal - decisionhorizon - impactscope

1. What is the current, in-scope definition of Hypothesis?
2. Which entities, identifiers, attributes and relationships constitute Hypothesis?
3. Which source or master system is authoritative for Hypothesis?
4. Who owns, validates and updates Hypothesis, and when was it last verified?

Assumptions

id - statement - confidence

1. What is the current, in-scope definition of Assumptions?
2. Which entities, identifiers, attributes and relationships constitute Assumptions?
3. Which source or master system is authoritative for Assumptions?
4. Who owns, validates and updates Assumptions, and when was it last verified?

Expected Outcomes

id - description - related value/economics

1. What is the current, in-scope definition of Expected Outcomes?
2. Which entities, identifiers, attributes and relationships constitute Expected Outcomes?
3. Which source or master system is authoritative for Expected Outcomes?
4. Who owns, validates and updates Expected Outcomes, and when was it last verified?

Validation Plan

method - metrics - thresholds - timeframe

1. What is the current, in-scope definition of Validation Plan?
2. Which entities, identifiers, attributes and relationships constitute Validation Plan?
3. Which source or master system is authoritative for Validation Plan?
4. Who owns, validates and updates Validation Plan, and when was it last verified?

Metrics

definition - source - interpretation

1. What is the current, in-scope definition of Metrics?
2. Which entities, identifiers, attributes and relationships constitute Metrics?
3. Which source or master system is authoritative for Metrics?
4. Who owns, validates and updates Metrics, and when was it last verified?

Evidence

source - reliability - summary

1. What is the current, in-scope definition of Evidence?
2. Which entities, identifiers, attributes and relationships constitute Evidence?
3. Which source or master system is authoritative for Evidence?
4. Who owns, validates and updates Evidence, and when was it last verified?

Decision Logic

continue / stop / pivot / scale

1. What is the current, in-scope definition of Decision Logic?
2. Which entities, identifiers, attributes and relationships constitute Decision Logic?
3. Which source or master system is authoritative for Decision Logic?
4. Who owns, validates and updates Decision Logic, and when was it last verified?

Status

draft - validating - validated - invalidated - archived

1. What is the current, in-scope definition of Status?
2. Which entities, identifiers, attributes and relationships constitute Status?
3. Which source or master system is authoritative for Status?
4. Who owns, validates and updates Status, and when was it last verified?

Strategy

id - description - basedon hypotheses

1. What is the current, in-scope definition of Strategy?
2. Which entities, identifiers, attributes and relationships constitute Strategy?
3. Which source or master system is authoritative for Strategy?
4. Who owns, validates and updates Strategy, and when was it last verified?

Objectives

id - metric - target

1. What is the current, in-scope definition of Objectives?
2. Which entities, identifiers, attributes and relationships constitute Objectives?
3. Which source or master system is authoritative for Objectives?
4. Who owns, validates and updates Objectives, and when was it last verified?

Initiatives

id - derivedfrom hypotheses - valuetarget - economictarget

1. What is the current, in-scope definition of Initiatives?
2. Which entities, identifiers, attributes and relationships constitute Initiatives?
3. Which source or master system is authoritative for Initiatives?
4. Who owns, validates and updates Initiatives, and when was it last verified?

Roadmap

items - dependencies - sequence

1. What is the current, in-scope definition of Roadmap?
2. Which entities, identifiers, attributes and relationships constitute Roadmap?
3. Which source or master system is authoritative for Roadmap?
4. Who owns, validates and updates Roadmap, and when was it last verified?

Versions

version id - included items

1. What is the current, in-scope definition of Versions?
2. Which entities, identifiers, attributes and relationships constitute Versions?
3. Which source or master system is authoritative for Versions?
4. Who owns, validates and updates Versions, and when was it last verified?

Prioritization

rules - trade-offs

1. What is the current, in-scope definition of Prioritization?
2. Which entities, identifiers, attributes and relationships constitute Prioritization?
3. Which source or master system is authoritative for Prioritization?
4. Who owns, validates and updates Prioritization, and when was it last verified?

Processes

id - level - parent - related processes

1. What is the current, in-scope definition of Processes?
2. Which entities, identifiers, attributes and relationships constitute Processes?
3. Which source or master system is authoritative for Processes?
4. Who owns, validates and updates Processes, and when was it last verified?

Steps

sequence - executor - input/output

1. What is the current, in-scope definition of Steps?
2. Which entities, identifiers, attributes and relationships constitute Steps?
3. Which source or master system is authoritative for Steps?
4. Who owns, validates and updates Steps, and when was it last verified?

Events

triggers - start/end

1. What is the current, in-scope definition of Events?
2. Which entities, identifiers, attributes and relationships constitute Events?
3. Which source or master system is authoritative for Events?
4. Who owns, validates and updates Events, and when was it last verified?

Gateways

decision logic

1. What is the current, in-scope definition of Gateways?
2. Which entities, identifiers, attributes and relationships constitute Gateways?
3. Which source or master system is authoritative for Gateways?
4. Who owns, validates and updates Gateways, and when was it last verified?

Orchestration

process coordination - dependencies

1. What is the current, in-scope definition of Orchestration?
2. Which entities, identifiers, attributes and relationships constitute Orchestration?
3. Which source or master system is authoritative for Orchestration?
4. Who owns, validates and updates Orchestration, and when was it last verified?

Exception Flows

failure paths - recovery behavior

1. What is the current, in-scope definition of Exception Flows?
2. Which entities, identifiers, attributes and relationships constitute Exception Flows?
3. Which source or master system is authoritative for Exception Flows?
4. Who owns, validates and updates Exception Flows, and when was it last verified?

Parallel Flows

concurrent execution

1. What is the current, in-scope definition of Parallel Flows?
2. Which entities, identifiers, attributes and relationships constitute Parallel Flows?
3. Which source or master system is authoritative for Parallel Flows?
4. Who owns, validates and updates Parallel Flows, and when was it last verified?

Outcome

id, evaluates (hypothesis/goal/initiative ref) - expected outcome ref, observed value, measurement window, source metric ref - attributionconfidence

1. What is the current, in-scope definition of Outcome?
2. Which entities, identifiers, attributes and relationships constitute Outcome?
3. Which source or master system is authoritative for Outcome?
4. Who owns, validates and updates Outcome, and when was it last verified?

Verdict

id, value: validated|refuted|inconclusive|superseded - evidence refs (b9.903)

1. What is the current, in-scope definition of Verdict?
2. Which entities, identifiers, attributes and relationships constitute Verdict?
3. Which source or master system is authoritative for Verdict?
4. Who owns, validates and updates Verdict, and when was it last verified?

Value Realization

id, intended value ref (b0.002/b0.006), realized assessment

1. What is the current, in-scope definition of Value Realization?
2. Which entities, identifiers, attributes and relationships constitute Value Realization?
3. Which source or master system is authoritative for Value Realization?
4. Who owns, validates and updates Value Realization, and when was it last verified?

Follow-on Decision

id, decision: persevere|pivot|scale|kill|re-test - rationale, linked decision record (b8.805)

1. What is the current, in-scope definition of Follow-on Decision?
2. Which entities, identifiers, attributes and relationships constitute Follow-on Decision?
3. Which source or master system is authoritative for Follow-on Decision?
4. Who owns, validates and updates Follow-on Decision, and when was it last verified?

Systems

id - boundary - owned capabilities

1. What is the current, in-scope definition of Systems?
2. Which entities, identifiers, attributes and relationships constitute Systems?
3. Which source or master system is authoritative for Systems?
4. Who owns, validates and updates Systems, and when was it last verified?

Applications

system - responsibilities

1. What is the current, in-scope definition of Applications?
2. Which entities, identifiers, attributes and relationships constitute Applications?
3. Which source or master system is authoritative for Applications?
4. Who owns, validates and updates Applications, and when was it last verified?

Components

application - responsibility - execution ownership - implements capabilities/services

1. What is the current, in-scope definition of Components?
2. Which entities, identifiers, attributes and relationships constitute Components?
3. Which source or master system is authoritative for Components?
4. Who owns, validates and updates Components, and when was it last verified?

Modules

grouping

1. What is the current, in-scope definition of Modules?
2. Which entities, identifiers, attributes and relationships constitute Modules?
3. Which source or master system is authoritative for Modules?
4. Who owns, validates and updates Modules, and when was it last verified?

Deployment Units

runtime structure

1. What is the current, in-scope definition of Deployment Units?
2. Which entities, identifiers, attributes and relationships constitute Deployment Units?
3. Which source or master system is authoritative for Deployment Units?
4. Who owns, validates and updates Deployment Units, and when was it last verified?

Responsibility Mapping

component → capability - component → service - component → process step - component → critical step

1. What is the current, in-scope definition of Responsibility Mapping?
2. Which entities, identifiers, attributes and relationships constitute Responsibility Mapping?
3. Which source or master system is authoritative for Responsibility Mapping?
4. Who owns, validates and updates Responsibility Mapping, and when was it last verified?

Data Domains

id - description - entities

1. What is the current, in-scope definition of Data Domains?
2. Which entities, identifiers, attributes and relationships constitute Data Domains?
3. Which source or master system is authoritative for Data Domains?
4. Who owns, validates and updates Data Domains, and when was it last verified?

Entities

id - domain - attributes - states (optional) - lifecycle

1. What is the current, in-scope definition of Entities?
2. Which entities, identifiers, attributes and relationships constitute Entities?
3. Which source or master system is authoritative for Entities?
4. Who owns, validates and updates Entities, and when was it last verified?

Attributes

name - type - meaning - constraints

1. What is the current, in-scope definition of Attributes?
2. Which entities, identifiers, attributes and relationships constitute Attributes?
3. Which source or master system is authoritative for Attributes?
4. Who owns, validates and updates Attributes, and when was it last verified?

Relationships

type - cardinality

1. What is the current, in-scope definition of Relationships?
2. Which entities, identifiers, attributes and relationships constitute Relationships?
3. Which source or master system is authoritative for Relationships?
4. Who owns, validates and updates Relationships, and when was it last verified?

Ownership

component owner - source of truth - access rules

1. What is the current, in-scope definition of Ownership?
2. Which entities, identifiers, attributes and relationships constitute Ownership?
3. Which source or master system is authoritative for Ownership?
4. Who owns, validates and updates Ownership, and when was it last verified?

Data Flows

source component - target component - entities transferred

1. What is the current, in-scope definition of Data Flows?
2. Which entities, identifiers, attributes and relationships constitute Data Flows?
3. Which source or master system is authoritative for Data Flows?
4. Who owns, validates and updates Data Flows, and when was it last verified?

Lifecycle

states - transitions - triggers

1. What is the current, in-scope definition of Lifecycle?
2. Which entities, identifiers, attributes and relationships constitute Lifecycle?
3. Which source or master system is authoritative for Lifecycle?
4. Who owns, validates and updates Lifecycle, and when was it last verified?

Consistency Rules

consistency type - synchronization rules

1. What is the current, in-scope definition of Consistency Rules?
2. Which entities, identifiers, attributes and relationships constitute Consistency Rules?
3. Which source or master system is authoritative for Consistency Rules?
4. Who owns, validates and updates Consistency Rules, and when was it last verified?

APIs

id - owner component - exposure type

1. What is the current, in-scope definition of APIs?
2. Which entities, identifiers, attributes and relationships constitute APIs?
3. Which source or master system is authoritative for APIs?
4. Who owns, validates and updates APIs, and when was it last verified?

Operations

id - purpose - request - response - interaction pattern

1. What is the current, in-scope definition of Operations?
2. Which entities, identifiers, attributes and relationships constitute Operations?
3. Which source or master system is authoritative for Operations?
4. Who owns, validates and updates Operations, and when was it last verified?

Requests / Responses

structure - validation rules

1. What is the current, in-scope definition of Requests / Responses?
2. Which entities, identifiers, attributes and relationships constitute Requests / Responses?
3. Which source or master system is authoritative for Requests / Responses?
4. Who owns, validates and updates Requests / Responses, and when was it last verified?

Commands

intent - mapped logic

1. What is the current, in-scope definition of Commands?
2. Which entities, identifiers, attributes and relationships constitute Commands?
3. Which source or master system is authoritative for Commands?
4. Who owns, validates and updates Commands, and when was it last verified?

Events

type - payload - producer

1. What is the current, in-scope definition of Events?
2. Which entities, identifiers, attributes and relationships constitute Events?
3. Which source or master system is authoritative for Events?
4. Who owns, validates and updates Events, and when was it last verified?

Contracts

structure - compatibility rules - versioning

1. What is the current, in-scope definition of Contracts?
2. Which entities, identifiers, attributes and relationships constitute Contracts?
3. Which source or master system is authoritative for Contracts?
4. Who owns, validates and updates Contracts, and when was it last verified?

Integrations

id - purpose - connected systems - topology

1. What is the current, in-scope definition of Integrations?
2. Which entities, identifiers, attributes and relationships constitute Integrations?
3. Which source or master system is authoritative for Integrations?
4. Who owns, validates and updates Integrations, and when was it last verified?

Systems

description - ownership - role

1. What is the current, in-scope definition of Systems?
2. Which entities, identifiers, attributes and relationships constitute Systems?
3. Which source or master system is authoritative for Systems?
4. Who owns, validates and updates Systems, and when was it last verified?

Communication Patterns

type - interaction style

1. What is the current, in-scope definition of Communication Patterns?
2. Which entities, identifiers, attributes and relationships constitute Communication Patterns?
3. Which source or master system is authoritative for Communication Patterns?
4. Who owns, validates and updates Communication Patterns, and when was it last verified?

Protocols

protocol - constraints

1. What is the current, in-scope definition of Protocols?
2. Which entities, identifiers, attributes and relationships constitute Protocols?
3. Which source or master system is authoritative for Protocols?
4. Who owns, validates and updates Protocols, and when was it last verified?

Channels

type - endpoints / topics / queues

1. What is the current, in-scope definition of Channels?
2. Which entities, identifiers, attributes and relationships constitute Channels?
3. Which source or master system is authoritative for Channels?
4. Who owns, validates and updates Channels, and when was it last verified?

Messages / Events

payload - source - destination

1. What is the current, in-scope definition of Messages / Events?
2. Which entities, identifiers, attributes and relationships constitute Messages / Events?
3. Which source or master system is authoritative for Messages / Events?
4. Who owns, validates and updates Messages / Events, and when was it last verified?

Reliability

delivery guarantees - retry policy - failure handling

1. What is the current, in-scope definition of Reliability?
2. Which entities, identifiers, attributes and relationships constitute Reliability?
3. Which source or master system is authoritative for Reliability?
4. Who owns, validates and updates Reliability, and when was it last verified?

External Systems and Ecosystem Surface

Structured external systems and ecosystem surface entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of External Systems and Ecosystem Surface?
2. Which entities, identifiers, attributes and relationships constitute External Systems and Ecosystem Surface?
3. Which source or master system is authoritative for External Systems and Ecosystem Surface?
4. Who owns, validates and updates External Systems and Ecosystem Surface, and when was it last verified?

Event Catalog and Event Mesh

Structured event catalog and event mesh entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Event Catalog and Event Mesh?
2. Which entities, identifiers, attributes and relationships constitute Event Catalog and Event Mesh?
3. Which source or master system is authoritative for Event Catalog and Event Mesh?
4. Who owns, validates and updates Event Catalog and Event Mesh, and when was it last verified?

Bounded Contexts and Domain Architecture

Structured bounded contexts and domain architecture entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Bounded Contexts and Domain Architecture?
2. Which entities, identifiers, attributes and relationships constitute Bounded Contexts and Domain Architecture?
3. Which source or master system is authoritative for Bounded Contexts and Domain Architecture?
4. Who owns, validates and updates Bounded Contexts and Domain Architecture, and when was it last verified?

Technologies

id - type - purpose

1. What is the current, in-scope definition of Technologies?
2. Which entities, identifiers, attributes and relationships constitute Technologies?
3. Which source or master system is authoritative for Technologies?
4. Who owns, validates and updates Technologies, and when was it last verified?

Runtimes

id - supported technologies - execution model

1. What is the current, in-scope definition of Runtimes?
2. Which entities, identifiers, attributes and relationships constitute Runtimes?
3. Which source or master system is authoritative for Runtimes?
4. Who owns, validates and updates Runtimes, and when was it last verified?

Frameworks & Libraries

language - usage context

1. What is the current, in-scope definition of Frameworks & Libraries?
2. Which entities, identifiers, attributes and relationships constitute Frameworks & Libraries?
3. Which source or master system is authoritative for Frameworks & Libraries?
4. Who owns, validates and updates Frameworks & Libraries, and when was it last verified?

Storage

type (relational / NoSQL / object / cache) - purpose

1. What is the current, in-scope definition of Storage?
2. Which entities, identifiers, attributes and relationships constitute Storage?
3. Which source or master system is authoritative for Storage?
4. Who owns, validates and updates Storage, and when was it last verified?

Messaging

type (queue / pub-sub / streaming) - usage

1. What is the current, in-scope definition of Messaging?
2. Which entities, identifiers, attributes and relationships constitute Messaging?
3. Which source or master system is authoritative for Messaging?
4. Who owns, validates and updates Messaging, and when was it last verified?

Platforms

environment type - hosting model

1. What is the current, in-scope definition of Platforms?
2. Which entities, identifiers, attributes and relationships constitute Platforms?
3. Which source or master system is authoritative for Platforms?
4. Who owns, validates and updates Platforms, and when was it last verified?

Constraints

limitation - affected components

1. What is the current, in-scope definition of Constraints?
2. Which entities, identifiers, attributes and relationships constitute Constraints?
3. Which source or master system is authoritative for Constraints?
4. Who owns, validates and updates Constraints, and when was it last verified?

Capabilities

strength - use cases

1. What is the current, in-scope definition of Capabilities?
2. Which entities, identifiers, attributes and relationships constitute Capabilities?
3. Which source or master system is authoritative for Capabilities?
4. Who owns, validates and updates Capabilities, and when was it last verified?

Repositories

id - location - purpose

1. What is the current, in-scope definition of Repositories?
2. Which entities, identifiers, attributes and relationships constitute Repositories?
3. Which source or master system is authoritative for Repositories?
4. Who owns, validates and updates Repositories, and when was it last verified?

Codebases

repository - scope

1. What is the current, in-scope definition of Codebases?
2. Which entities, identifiers, attributes and relationships constitute Codebases?
3. Which source or master system is authoritative for Codebases?
4. Who owns, validates and updates Codebases, and when was it last verified?

Modules

codebase - responsibility

1. What is the current, in-scope definition of Modules?
2. Which entities, identifiers, attributes and relationships constitute Modules?
3. Which source or master system is authoritative for Modules?
4. Who owns, validates and updates Modules, and when was it last verified?

Implementation Units

type - module - purpose

1. What is the current, in-scope definition of Implementation Units?
2. Which entities, identifiers, attributes and relationships constitute Implementation Units?
3. Which source or master system is authoritative for Implementation Units?
4. Who owns, validates and updates Implementation Units, and when was it last verified?

Code Mapping

module → component - function → operation - class → entity - handler → process step

1. What is the current, in-scope definition of Code Mapping?
2. Which entities, identifiers, attributes and relationships constitute Code Mapping?
3. Which source or master system is authoritative for Code Mapping?
4. Who owns, validates and updates Code Mapping, and when was it last verified?

Tests

type - validates - coverage

1. What is the current, in-scope definition of Tests?
2. Which entities, identifiers, attributes and relationships constitute Tests?
3. Which source or master system is authoritative for Tests?
4. Who owns, validates and updates Tests, and when was it last verified?

Dependencies

internal dependencies - external libraries

1. What is the current, in-scope definition of Dependencies?
2. Which entities, identifiers, attributes and relationships constitute Dependencies?
3. Which source or master system is authoritative for Dependencies?
4. Who owns, validates and updates Dependencies, and when was it last verified?

Build

id - input code - output artifact

1. What is the current, in-scope definition of Build?
2. Which entities, identifiers, attributes and relationships constitute Build?
3. Which source or master system is authoritative for Build?
4. Who owns, validates and updates Build, and when was it last verified?

Artifacts

id - type - version

1. What is the current, in-scope definition of Artifacts?
2. Which entities, identifiers, attributes and relationships constitute Artifacts?
3. Which source or master system is authoritative for Artifacts?
4. Who owns, validates and updates Artifacts, and when was it last verified?

Packaging

format - structure

1. What is the current, in-scope definition of Packaging?
2. Which entities, identifiers, attributes and relationships constitute Packaging?
3. Which source or master system is authoritative for Packaging?
4. Who owns, validates and updates Packaging, and when was it last verified?

Deployment

unit - target environment

1. What is the current, in-scope definition of Deployment?
2. Which entities, identifiers, attributes and relationships constitute Deployment?
3. Which source or master system is authoritative for Deployment?
4. Who owns, validates and updates Deployment, and when was it last verified?

Runtime

instances - scaling model

1. What is the current, in-scope definition of Runtime?
2. Which entities, identifiers, attributes and relationships constitute Runtime?
3. Which source or master system is authoritative for Runtime?
4. Who owns, validates and updates Runtime, and when was it last verified?

Pipeline

stages - triggers - dependencies

1. What is the current, in-scope definition of Pipeline?
2. Which entities, identifiers, attributes and relationships constitute Pipeline?
3. Which source or master system is authoritative for Pipeline?
4. Who owns, validates and updates Pipeline, and when was it last verified?

Environments

name - purpose

1. What is the current, in-scope definition of Environments?
2. Which entities, identifiers, attributes and relationships constitute Environments?
3. Which source or master system is authoritative for Environments?
4. Who owns, validates and updates Environments, and when was it last verified?

Dependency Inventory, SBOM and Reproducibility

Structured dependency inventory, sbom and reproducibility entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Dependency Inventory, SBOM and Reproducibility?
2. Which entities, identifiers, attributes and relationships constitute Dependency Inventory, SBOM and Reproducibility?
3. Which source or master system is authoritative for Dependency Inventory, SBOM and Reproducibility?
4. Who owns, validates and updates Dependency Inventory, SBOM and Reproducibility, and when was it last verified?

Configuration, Feature Flags and Environment Variants

Structured configuration, feature flags and environment variants entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Configuration, Feature Flags and Environment Variants?
2. Which entities, identifiers, attributes and relationships constitute Configuration, Feature Flags and Environment Variants?
3. Which source or master system is authoritative for Configuration, Feature Flags and Environment Variants?
4. Who owns, validates and updates Configuration, Feature Flags and Environment Variants, and when was it last verified?

Requirements

id - type - description - priority

1. What is the current, in-scope definition of Requirements?
2. Which entities, identifiers, attributes and relationships constitute Requirements?
3. Which source or master system is authoritative for Requirements?
4. Who owns, validates and updates Requirements, and when was it last verified?

Acceptance Criteria

condition - expected result

1. What is the current, in-scope definition of Acceptance Criteria?
2. Which entities, identifiers, attributes and relationships constitute Acceptance Criteria?
3. Which source or master system is authoritative for Acceptance Criteria?
4. Who owns, validates and updates Acceptance Criteria, and when was it last verified?

Scenarios

context (given) - action (when) - outcome (then)

1. What is the current, in-scope definition of Scenarios?
2. Which entities, identifiers, attributes and relationships constitute Scenarios?
3. Which source or master system is authoritative for Scenarios?
4. Who owns, validates and updates Scenarios, and when was it last verified?

Constraints

type - limitation

1. What is the current, in-scope definition of Constraints?
2. Which entities, identifiers, attributes and relationships constitute Constraints?
3. Which source or master system is authoritative for Constraints?
4. Who owns, validates and updates Constraints, and when was it last verified?

Traceability

linked initiative - linked value - linked process

1. What is the current, in-scope definition of Traceability?
2. Which entities, identifiers, attributes and relationships constitute Traceability?
3. Which source or master system is authoritative for Traceability?
4. Who owns, validates and updates Traceability, and when was it last verified?

Domain Entities

id - attributes - relationships

1. What is the current, in-scope definition of Domain Entities?
2. Which entities, identifiers, attributes and relationships constitute Domain Entities?
3. Which source or master system is authoritative for Domain Entities?
4. Who owns, validates and updates Domain Entities, and when was it last verified?

Attributes

name - type - constraints

1. What is the current, in-scope definition of Attributes?
2. Which entities, identifiers, attributes and relationships constitute Attributes?
3. Which source or master system is authoritative for Attributes?
4. Who owns, validates and updates Attributes, and when was it last verified?

Relationships

type - cardinality

1. What is the current, in-scope definition of Relationships?
2. Which entities, identifiers, attributes and relationships constitute Relationships?
3. Which source or master system is authoritative for Relationships?
4. Who owns, validates and updates Relationships, and when was it last verified?

Business Rules

condition - outcome

1. What is the current, in-scope definition of Business Rules?
2. Which entities, identifiers, attributes and relationships constitute Business Rules?
3. Which source or master system is authoritative for Business Rules?
4. Who owns, validates and updates Business Rules, and when was it last verified?

Invariants

rule - validation

1. What is the current, in-scope definition of Invariants?
2. Which entities, identifiers, attributes and relationships constitute Invariants?
3. Which source or master system is authoritative for Invariants?
4. Who owns, validates and updates Invariants, and when was it last verified?

Lifecycle

states - transitions

1. What is the current, in-scope definition of Lifecycle?
2. Which entities, identifiers, attributes and relationships constitute Lifecycle?
3. Which source or master system is authoritative for Lifecycle?
4. Who owns, validates and updates Lifecycle, and when was it last verified?

Decision Models

inputs - rules - outputs

1. What is the current, in-scope definition of Decision Models?
2. Which entities, identifiers, attributes and relationships constitute Decision Models?
3. Which source or master system is authoritative for Decision Models?
4. Who owns, validates and updates Decision Models, and when was it last verified?

Actors

id - type - attributes

1. What is the current, in-scope definition of Actors?
2. Which entities, identifiers, attributes and relationships constitute Actors?
3. Which source or master system is authoritative for Actors?
4. Who owns, validates and updates Actors, and when was it last verified?

Roles

id - assigned permissions

1. What is the current, in-scope definition of Roles?
2. Which entities, identifiers, attributes and relationships constitute Roles?
3. Which source or master system is authoritative for Roles?
4. Who owns, validates and updates Roles, and when was it last verified?

Permissions

action - resource

1. What is the current, in-scope definition of Permissions?
2. Which entities, identifiers, attributes and relationships constitute Permissions?
3. Which source or master system is authoritative for Permissions?
4. Who owns, validates and updates Permissions, and when was it last verified?

Policies

rule - applicable roles - conditions

1. What is the current, in-scope definition of Policies?
2. Which entities, identifiers, attributes and relationships constitute Policies?
3. Which source or master system is authoritative for Policies?
4. Who owns, validates and updates Policies, and when was it last verified?

Conditions

logic - parameters

1. What is the current, in-scope definition of Conditions?
2. Which entities, identifiers, attributes and relationships constitute Conditions?
3. Which source or master system is authoritative for Conditions?
4. Who owns, validates and updates Conditions, and when was it last verified?

Scope

boundaries - limitations

1. What is the current, in-scope definition of Scope?
2. Which entities, identifiers, attributes and relationships constitute Scope?
3. Which source or master system is authoritative for Scope?
4. Who owns, validates and updates Scope, and when was it last verified?

Quality Attributes

type - description

1. What is the current, in-scope definition of Quality Attributes?
2. Which entities, identifiers, attributes and relationships constitute Quality Attributes?
3. Which source or master system is authoritative for Quality Attributes?
4. Who owns, validates and updates Quality Attributes, and when was it last verified?

NFRs

requirement - metric - threshold

1. What is the current, in-scope definition of NFRs?
2. Which entities, identifiers, attributes and relationships constitute NFRs?
3. Which source or master system is authoritative for NFRs?
4. Who owns, validates and updates NFRs, and when was it last verified?

Scenarios

stimulus - environment - response - measure

1. What is the current, in-scope definition of Scenarios?
2. Which entities, identifiers, attributes and relationships constitute Scenarios?
3. Which source or master system is authoritative for Scenarios?
4. Who owns, validates and updates Scenarios, and when was it last verified?

Metrics

definition - unit

1. What is the current, in-scope definition of Metrics?
2. Which entities, identifiers, attributes and relationships constitute Metrics?
3. Which source or master system is authoritative for Metrics?
4. Who owns, validates and updates Metrics, and when was it last verified?

Thresholds

acceptable range

1. What is the current, in-scope definition of Thresholds?
2. Which entities, identifiers, attributes and relationships constitute Thresholds?
3. Which source or master system is authoritative for Thresholds?
4. Who owns, validates and updates Thresholds, and when was it last verified?

SLA / SLO

target values - measurement method

1. What is the current, in-scope definition of SLA / SLO?
2. Which entities, identifiers, attributes and relationships constitute SLA / SLO?
3. Which source or master system is authoritative for SLA / SLO?
4. Who owns, validates and updates SLA / SLO, and when was it last verified?

State Machines and Lifecycles

Structured state machines and lifecycles entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of State Machines and Lifecycles?
2. Which entities, identifiers, attributes and relationships constitute State Machines and Lifecycles?
3. Which source or master system is authoritative for State Machines and Lifecycles?
4. Who owns, validates and updates State Machines and Lifecycles, and when was it last verified?

Behavioral Contracts and Invariants

Structured behavioral contracts and invariants entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Behavioral Contracts and Invariants?
2. Which entities, identifiers, attributes and relationships constitute Behavioral Contracts and Invariants?
3. Which source or master system is authoritative for Behavioral Contracts and Invariants?
4. Who owns, validates and updates Behavioral Contracts and Invariants, and when was it last verified?

Error Taxonomy and Failure Behavior

Structured error taxonomy and failure behavior entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Error Taxonomy and Failure Behavior?
2. Which entities, identifiers, attributes and relationships constitute Error Taxonomy and Failure Behavior?
3. Which source or master system is authoritative for Error Taxonomy and Failure Behavior?
4. Who owns, validates and updates Error Taxonomy and Failure Behavior, and when was it last verified?

User Goals

id - description - actor

1. What is the current, in-scope definition of User Goals?
2. Which entities, identifiers, attributes and relationships constitute User Goals?
3. Which source or master system is authoritative for User Goals?
4. Who owns, validates and updates User Goals, and when was it last verified?

Scenarios

context - goal - steps

1. What is the current, in-scope definition of Scenarios?
2. Which entities, identifiers, attributes and relationships constitute Scenarios?
3. Which source or master system is authoritative for Scenarios?
4. Who owns, validates and updates Scenarios, and when was it last verified?

Interaction Flows

ordered steps - decision points

1. What is the current, in-scope definition of Interaction Flows?
2. Which entities, identifiers, attributes and relationships constitute Interaction Flows?
3. Which source or master system is authoritative for Interaction Flows?
4. Who owns, validates and updates Interaction Flows, and when was it last verified?

Journeys

multiple scenarios - touchpoints

1. What is the current, in-scope definition of Journeys?
2. Which entities, identifiers, attributes and relationships constitute Journeys?
3. Which source or master system is authoritative for Journeys?
4. Who owns, validates and updates Journeys, and when was it last verified?

UX Decisions

decision - rationale

1. What is the current, in-scope definition of UX Decisions?
2. Which entities, identifiers, attributes and relationships constitute UX Decisions?
3. Which source or master system is authoritative for UX Decisions?
4. Who owns, validates and updates UX Decisions, and when was it last verified?

Interface Areas

id - purpose - contained pages

1. What is the current, in-scope definition of Interface Areas?
2. Which entities, identifiers, attributes and relationships constitute Interface Areas?
3. Which source or master system is authoritative for Interface Areas?
4. Who owns, validates and updates Interface Areas, and when was it last verified?

Pages

id - route - layout

1. What is the current, in-scope definition of Pages?
2. Which entities, identifiers, attributes and relationships constitute Pages?
3. Which source or master system is authoritative for Pages?
4. Who owns, validates and updates Pages, and when was it last verified?

Navigation

nodes - hierarchy

1. What is the current, in-scope definition of Navigation?
2. Which entities, identifiers, attributes and relationships constitute Navigation?
3. Which source or master system is authoritative for Navigation?
4. Who owns, validates and updates Navigation, and when was it last verified?

Routes

path - target page

1. What is the current, in-scope definition of Routes?
2. Which entities, identifiers, attributes and relationships constitute Routes?
3. Which source or master system is authoritative for Routes?
4. Who owns, validates and updates Routes, and when was it last verified?

Layout

regions - composition

1. What is the current, in-scope definition of Layout?
2. Which entities, identifiers, attributes and relationships constitute Layout?
3. Which source or master system is authoritative for Layout?
4. Who owns, validates and updates Layout, and when was it last verified?

Screens

id - purpose - linked page

1. What is the current, in-scope definition of Screens?
2. Which entities, identifiers, attributes and relationships constitute Screens?
3. Which source or master system is authoritative for Screens?
4. Who owns, validates and updates Screens, and when was it last verified?

Forms

fields - validation

1. What is the current, in-scope definition of Forms?
2. Which entities, identifiers, attributes and relationships constitute Forms?
3. Which source or master system is authoritative for Forms?
4. Who owns, validates and updates Forms, and when was it last verified?

Fields

type - constraints

1. What is the current, in-scope definition of Fields?
2. Which entities, identifiers, attributes and relationships constitute Fields?
3. Which source or master system is authoritative for Fields?
4. Who owns, validates and updates Fields, and when was it last verified?

Components

type - reuse

1. What is the current, in-scope definition of Components?
2. Which entities, identifiers, attributes and relationships constitute Components?
3. Which source or master system is authoritative for Components?
4. Who owns, validates and updates Components, and when was it last verified?

States

type - triggers

1. What is the current, in-scope definition of States?
2. Which entities, identifiers, attributes and relationships constitute States?
3. Which source or master system is authoritative for States?
4. Who owns, validates and updates States, and when was it last verified?

Validation

rules - messages

1. What is the current, in-scope definition of Validation?
2. Which entities, identifiers, attributes and relationships constitute Validation?
3. Which source or master system is authoritative for Validation?
4. Who owns, validates and updates Validation, and when was it last verified?

Feedback

message - condition

1. What is the current, in-scope definition of Feedback?
2. Which entities, identifiers, attributes and relationships constitute Feedback?
3. Which source or master system is authoritative for Feedback?
4. Who owns, validates and updates Feedback, and when was it last verified?

Design System and UI Components

Structured design system and ui components entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Design System and UI Components?
2. Which entities, identifiers, attributes and relationships constitute Design System and UI Components?
3. Which source or master system is authoritative for Design System and UI Components?
4. Who owns, validates and updates Design System and UI Components, and when was it last verified?

Accessibility, Localization and Notifications

Structured accessibility, localization and notifications entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Accessibility, Localization and Notifications?
2. Which entities, identifiers, attributes and relationships constitute Accessibility, Localization and Notifications?
3. Which source or master system is authoritative for Accessibility, Localization and Notifications?
4. Who owns, validates and updates Accessibility, Localization and Notifications, and when was it last verified?

Runtime Instances

id - deployment unit - environment

1. What is the current, in-scope definition of Runtime Instances?
2. Which entities, identifiers, attributes and relationships constitute Runtime Instances?
3. Which source or master system is authoritative for Runtime Instances?
4. Who owns, validates and updates Runtime Instances, and when was it last verified?

Services

service instances - mapped components

1. What is the current, in-scope definition of Services?
2. Which entities, identifiers, attributes and relationships constitute Services?
3. Which source or master system is authoritative for Services?
4. Who owns, validates and updates Services, and when was it last verified?

Nodes

type - capacity

1. What is the current, in-scope definition of Nodes?
2. Which entities, identifiers, attributes and relationships constitute Nodes?
3. Which source or master system is authoritative for Nodes?
4. Who owns, validates and updates Nodes, and when was it last verified?

Clusters

nodes - orchestration

1. What is the current, in-scope definition of Clusters?
2. Which entities, identifiers, attributes and relationships constitute Clusters?
3. Which source or master system is authoritative for Clusters?
4. Who owns, validates and updates Clusters, and when was it last verified?

Regions / Zones

location - redundancy

1. What is the current, in-scope definition of Regions / Zones?
2. Which entities, identifiers, attributes and relationships constitute Regions / Zones?
3. Which source or master system is authoritative for Regions / Zones?
4. Who owns, validates and updates Regions / Zones, and when was it last verified?

Topology

distribution of services - dependencies

1. What is the current, in-scope definition of Topology?
2. Which entities, identifiers, attributes and relationships constitute Topology?
3. Which source or master system is authoritative for Topology?
4. Who owns, validates and updates Topology, and when was it last verified?

Network

connections - protocols

1. What is the current, in-scope definition of Network?
2. Which entities, identifiers, attributes and relationships constitute Network?
3. Which source or master system is authoritative for Network?
4. Who owns, validates and updates Network, and when was it last verified?

Metrics

name - unit - source

1. What is the current, in-scope definition of Metrics?
2. Which entities, identifiers, attributes and relationships constitute Metrics?
3. Which source or master system is authoritative for Metrics?
4. Who owns, validates and updates Metrics, and when was it last verified?

Logs

source - structure

1. What is the current, in-scope definition of Logs?
2. Which entities, identifiers, attributes and relationships constitute Logs?
3. Which source or master system is authoritative for Logs?
4. Who owns, validates and updates Logs, and when was it last verified?

Traces

spans - services

1. What is the current, in-scope definition of Traces?
2. Which entities, identifiers, attributes and relationships constitute Traces?
3. Which source or master system is authoritative for Traces?
4. Who owns, validates and updates Traces, and when was it last verified?

Alerts

condition - severity

1. What is the current, in-scope definition of Alerts?
2. Which entities, identifiers, attributes and relationships constitute Alerts?
3. Which source or master system is authoritative for Alerts?
4. Who owns, validates and updates Alerts, and when was it last verified?

Dashboards

metrics - visualizations

1. What is the current, in-scope definition of Dashboards?
2. Which entities, identifiers, attributes and relationships constitute Dashboards?
3. Which source or master system is authoritative for Dashboards?
4. Who owns, validates and updates Dashboards, and when was it last verified?

Instrumentation

data source - collection method

1. What is the current, in-scope definition of Instrumentation?
2. Which entities, identifiers, attributes and relationships constitute Instrumentation?
3. Which source or master system is authoritative for Instrumentation?
4. Who owns, validates and updates Instrumentation, and when was it last verified?

Incidents

id - type - severity - status

1. What is the current, in-scope definition of Incidents?
2. Which entities, identifiers, attributes and relationships constitute Incidents?
3. Which source or master system is authoritative for Incidents?
4. Who owns, validates and updates Incidents, and when was it last verified?

Detection

source (alert, user, system) - trigger

1. What is the current, in-scope definition of Detection?
2. Which entities, identifiers, attributes and relationships constitute Detection?
3. Which source or master system is authoritative for Detection?
4. Who owns, validates and updates Detection, and when was it last verified?

Response

assigned responders - steps - timeline

1. What is the current, in-scope definition of Response?
2. Which entities, identifiers, attributes and relationships constitute Response?
3. Which source or master system is authoritative for Response?
4. Who owns, validates and updates Response, and when was it last verified?

Runbooks

actions - conditions

1. What is the current, in-scope definition of Runbooks?
2. Which entities, identifiers, attributes and relationships constitute Runbooks?
3. Which source or master system is authoritative for Runbooks?
4. Who owns, validates and updates Runbooks, and when was it last verified?

Escalation

levels - rules

1. What is the current, in-scope definition of Escalation?
2. Which entities, identifiers, attributes and relationships constitute Escalation?
3. Which source or master system is authoritative for Escalation?
4. Who owns, validates and updates Escalation, and when was it last verified?

Postmortem

root cause - impact - lessons learned

1. What is the current, in-scope definition of Postmortem?
2. Which entities, identifiers, attributes and relationships constitute Postmortem?
3. Which source or master system is authoritative for Postmortem?
4. Who owns, validates and updates Postmortem, and when was it last verified?

SLA

service - target metric - guaranteed value

1. What is the current, in-scope definition of SLA?
2. Which entities, identifiers, attributes and relationships constitute SLA?
3. Which source or master system is authoritative for SLA?
4. Who owns, validates and updates SLA, and when was it last verified?

SLO

metric - target - measurement period

1. What is the current, in-scope definition of SLO?
2. Which entities, identifiers, attributes and relationships constitute SLO?
3. Which source or master system is authoritative for SLO?
4. Who owns, validates and updates SLO, and when was it last verified?

Error Budget

allowed failure - time window

1. What is the current, in-scope definition of Error Budget?
2. Which entities, identifiers, attributes and relationships constitute Error Budget?
3. Which source or master system is authoritative for Error Budget?
4. Who owns, validates and updates Error Budget, and when was it last verified?

Policies

rules - scope

1. What is the current, in-scope definition of Policies?
2. Which entities, identifiers, attributes and relationships constitute Policies?
3. Which source or master system is authoritative for Policies?
4. Who owns, validates and updates Policies, and when was it last verified?

Risk

type - probability - impact

1. What is the current, in-scope definition of Risk?
2. Which entities, identifiers, attributes and relationships constitute Risk?
3. Which source or master system is authoritative for Risk?
4. Who owns, validates and updates Risk, and when was it last verified?

Compliance

requirement - validation

1. What is the current, in-scope definition of Compliance?
2. Which entities, identifiers, attributes and relationships constitute Compliance?
3. Which source or master system is authoritative for Compliance?
4. Who owns, validates and updates Compliance, and when was it last verified?

Capacity, Scaling and Performance Engineering

Structured capacity, scaling and performance engineering entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Capacity, Scaling and Performance Engineering?
2. Which entities, identifiers, attributes and relationships constitute Capacity, Scaling and Performance Engineering?
3. Which source or master system is authoritative for Capacity, Scaling and Performance Engineering?
4. Who owns, validates and updates Capacity, Scaling and Performance Engineering, and when was it last verified?

Disaster Recovery, Backup and Continuity

Structured disaster recovery, backup and continuity entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Disaster Recovery, Backup and Continuity?
2. Which entities, identifiers, attributes and relationships constitute Disaster Recovery, Backup and Continuity?
3. Which source or master system is authoritative for Disaster Recovery, Backup and Continuity?
4. Who owns, validates and updates Disaster Recovery, Backup and Continuity, and when was it last verified?

Operational Readiness and Drills

Structured operational readiness and drills entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Operational Readiness and Drills?
2. Which entities, identifiers, attributes and relationships constitute Operational Readiness and Drills?
3. Which source or master system is authoritative for Operational Readiness and Drills?
4. Who owns, validates and updates Operational Readiness and Drills, and when was it last verified?

Test Strategy

levels - types - tools

1. What is the current, in-scope definition of Test Strategy?
2. Which entities, identifiers, attributes and relationships constitute Test Strategy?
3. Which source or master system is authoritative for Test Strategy?
4. Who owns, validates and updates Test Strategy, and when was it last verified?

Test Plans

scope - environments - schedule

1. What is the current, in-scope definition of Test Plans?
2. Which entities, identifiers, attributes and relationships constitute Test Plans?
3. Which source or master system is authoritative for Test Plans?
4. Who owns, validates and updates Test Plans, and when was it last verified?

Test Suites

test cases - grouping

1. What is the current, in-scope definition of Test Suites?
2. Which entities, identifiers, attributes and relationships constitute Test Suites?
3. Which source or master system is authoritative for Test Suites?
4. Who owns, validates and updates Test Suites, and when was it last verified?

Test Cases

steps - expected result

1. What is the current, in-scope definition of Test Cases?
2. Which entities, identifiers, attributes and relationships constitute Test Cases?
3. Which source or master system is authoritative for Test Cases?
4. Who owns, validates and updates Test Cases, and when was it last verified?

Coverage

requirements covered - scenarios covered

1. What is the current, in-scope definition of Coverage?
2. Which entities, identifiers, attributes and relationships constitute Coverage?
3. Which source or master system is authoritative for Coverage?
4. Who owns, validates and updates Coverage, and when was it last verified?

Defects

severity - status

1. What is the current, in-scope definition of Defects?
2. Which entities, identifiers, attributes and relationships constitute Defects?
3. Which source or master system is authoritative for Defects?
4. Who owns, validates and updates Defects, and when was it last verified?

Quality Gates

conditions - thresholds

1. What is the current, in-scope definition of Quality Gates?
2. Which entities, identifiers, attributes and relationships constitute Quality Gates?
3. Which source or master system is authoritative for Quality Gates?
4. Who owns, validates and updates Quality Gates, and when was it last verified?

Risks

id - description - source

1. What is the current, in-scope definition of Risks?
2. Which entities, identifiers, attributes and relationships constitute Risks?
3. Which source or master system is authoritative for Risks?
4. Who owns, validates and updates Risks, and when was it last verified?

Assessment

probability - impact - risk level

1. What is the current, in-scope definition of Assessment?
2. Which entities, identifiers, attributes and relationships constitute Assessment?
3. Which source or master system is authoritative for Assessment?
4. Who owns, validates and updates Assessment, and when was it last verified?

Mitigation

strategy - actions

1. What is the current, in-scope definition of Mitigation?
2. Which entities, identifiers, attributes and relationships constitute Mitigation?
3. Which source or master system is authoritative for Mitigation?
4. Who owns, validates and updates Mitigation, and when was it last verified?

Controls

mechanisms - enforcement

1. What is the current, in-scope definition of Controls?
2. Which entities, identifiers, attributes and relationships constitute Controls?
3. Which source or master system is authoritative for Controls?
4. Who owns, validates and updates Controls, and when was it last verified?

Residual Risk

remaining level - acceptance

1. What is the current, in-scope definition of Residual Risk?
2. Which entities, identifiers, attributes and relationships constitute Residual Risk?
3. Which source or master system is authoritative for Residual Risk?
4. Who owns, validates and updates Residual Risk, and when was it last verified?

Assets

id - type - sensitivity

1. What is the current, in-scope definition of Assets?
2. Which entities, identifiers, attributes and relationships constitute Assets?
3. Which source or master system is authoritative for Assets?
4. Who owns, validates and updates Assets, and when was it last verified?

Threats

target asset - attack vector

1. What is the current, in-scope definition of Threats?
2. Which entities, identifiers, attributes and relationships constitute Threats?
3. Which source or master system is authoritative for Threats?
4. Who owns, validates and updates Threats, and when was it last verified?

Vulnerabilities

affected component - severity

1. What is the current, in-scope definition of Vulnerabilities?
2. Which entities, identifiers, attributes and relationships constitute Vulnerabilities?
3. Which source or master system is authoritative for Vulnerabilities?
4. Who owns, validates and updates Vulnerabilities, and when was it last verified?

Controls

type - mechanism

1. What is the current, in-scope definition of Controls?
2. Which entities, identifiers, attributes and relationships constitute Controls?
3. Which source or master system is authoritative for Controls?
4. Who owns, validates and updates Controls, and when was it last verified?

Privacy

data type - protection rule

1. What is the current, in-scope definition of Privacy?
2. Which entities, identifiers, attributes and relationships constitute Privacy?
3. Which source or master system is authoritative for Privacy?
4. Who owns, validates and updates Privacy, and when was it last verified?

Boundaries

trust zones - data flow restrictions

1. What is the current, in-scope definition of Boundaries?
2. Which entities, identifiers, attributes and relationships constitute Boundaries?
3. Which source or master system is authoritative for Boundaries?
4. Who owns, validates and updates Boundaries, and when was it last verified?

Compliance Requirements

source - description - applicability

1. What is the current, in-scope definition of Compliance Requirements?
2. Which entities, identifiers, attributes and relationships constitute Compliance Requirements?
3. Which source or master system is authoritative for Compliance Requirements?
4. Who owns, validates and updates Compliance Requirements, and when was it last verified?

Controls

objective - mapping to requirement

1. What is the current, in-scope definition of Controls?
2. Which entities, identifiers, attributes and relationships constitute Controls?
3. Which source or master system is authoritative for Controls?
4. Who owns, validates and updates Controls, and when was it last verified?

Evidence

type - source - storage

1. What is the current, in-scope definition of Evidence?
2. Which entities, identifiers, attributes and relationships constitute Evidence?
3. Which source or master system is authoritative for Evidence?
4. Who owns, validates and updates Evidence, and when was it last verified?

Audit

scope - method - result

1. What is the current, in-scope definition of Audit?
2. Which entities, identifiers, attributes and relationships constitute Audit?
3. Which source or master system is authoritative for Audit?
4. Who owns, validates and updates Audit, and when was it last verified?

Findings

severity - description

1. What is the current, in-scope definition of Findings?
2. Which entities, identifiers, attributes and relationships constitute Findings?
3. Which source or master system is authoritative for Findings?
4. Who owns, validates and updates Findings, and when was it last verified?

Remediation

action - status

1. What is the current, in-scope definition of Remediation?
2. Which entities, identifiers, attributes and relationships constitute Remediation?
3. Which source or master system is authoritative for Remediation?
4. Who owns, validates and updates Remediation, and when was it last verified?

Threat Modeling and Attack Surface

Structured threat modeling and attack surface entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Threat Modeling and Attack Surface?
2. Which entities, identifiers, attributes and relationships constitute Threat Modeling and Attack Surface?
3. Which source or master system is authoritative for Threat Modeling and Attack Surface?
4. Who owns, validates and updates Threat Modeling and Attack Surface, and when was it last verified?

Vulnerability Management and Disclosure

Structured vulnerability management and disclosure entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Vulnerability Management and Disclosure?
2. Which entities, identifiers, attributes and relationships constitute Vulnerability Management and Disclosure?
3. Which source or master system is authoritative for Vulnerability Management and Disclosure?
4. Who owns, validates and updates Vulnerability Management and Disclosure, and when was it last verified?

Privacy Rights and DPIA

Structured privacy rights and dpia entities with stable IDs, typed relationships, and cross-layer links.

1. What is the current, in-scope definition of Privacy Rights and DPIA?
2. Which entities, identifiers, attributes and relationships constitute Privacy Rights and DPIA?
3. Which source or master system is authoritative for Privacy Rights and DPIA?
4. Who owns, validates and updates Privacy Rights and DPIA, and when was it last verified?

Work Items

id - type - status

1. What is the current, in-scope definition of Work Items?
2. Which entities, identifiers, attributes and relationships constitute Work Items?
3. Which source or master system is authoritative for Work Items?
4. Who owns, validates and updates Work Items, and when was it last verified?

Change Requests

intent - scope - priority

1. What is the current, in-scope definition of Change Requests?
2. Which entities, identifiers, attributes and relationships constitute Change Requests?
3. Which source or master system is authoritative for Change Requests?
4. Who owns, validates and updates Change Requests, and when was it last verified?

Context

linked requirements - linked components

1. What is the current, in-scope definition of Context?
2. Which entities, identifiers, attributes and relationships constitute Context?
3. Which source or master system is authoritative for Context?
4. Who owns, validates and updates Context, and when was it last verified?

Decision

chosen solution - reasoning

1. What is the current, in-scope definition of Decision?
2. Which entities, identifiers, attributes and relationships constitute Decision?
3. Which source or master system is authoritative for Decision?
4. Who owns, validates and updates Decision, and when was it last verified?

Summary

discussion summary - alternatives

1. What is the current, in-scope definition of Summary?
2. Which entities, identifiers, attributes and relationships constitute Summary?
3. Which source or master system is authoritative for Summary?
4. Who owns, validates and updates Summary, and when was it last verified?

Plans

scope - timeline

1. What is the current, in-scope definition of Plans?
2. Which entities, identifiers, attributes and relationships constitute Plans?
3. Which source or master system is authoritative for Plans?
4. Who owns, validates and updates Plans, and when was it last verified?

Iterations

duration - goals

1. What is the current, in-scope definition of Iterations?
2. Which entities, identifiers, attributes and relationships constitute Iterations?
3. Which source or master system is authoritative for Iterations?
4. Who owns, validates and updates Iterations, and when was it last verified?

Milestones

target date - deliverables

1. What is the current, in-scope definition of Milestones?
2. Which entities, identifiers, attributes and relationships constitute Milestones?
3. Which source or master system is authoritative for Milestones?
4. Who owns, validates and updates Milestones, and when was it last verified?

Flow

stages - transitions

1. What is the current, in-scope definition of Flow?
2. Which entities, identifiers, attributes and relationships constitute Flow?
3. Which source or master system is authoritative for Flow?
4. Who owns, validates and updates Flow, and when was it last verified?

Dependencies

source - target

1. What is the current, in-scope definition of Dependencies?
2. Which entities, identifiers, attributes and relationships constitute Dependencies?
3. Which source or master system is authoritative for Dependencies?
4. Who owns, validates and updates Dependencies, and when was it last verified?

Capacity

allocation - limits

1. What is the current, in-scope definition of Capacity?
2. Which entities, identifiers, attributes and relationships constitute Capacity?
3. Which source or master system is authoritative for Capacity?
4. Who owns, validates and updates Capacity, and when was it last verified?

Test Runs

executed test cases - environment - results

1. What is the current, in-scope definition of Test Runs?
2. Which entities, identifiers, attributes and relationships constitute Test Runs?
3. Which source or master system is authoritative for Test Runs?
4. Who owns, validates and updates Test Runs, and when was it last verified?

Acceptance

scope - decision

1. What is the current, in-scope definition of Acceptance?
2. Which entities, identifiers, attributes and relationships constitute Acceptance?
3. Which source or master system is authoritative for Acceptance?
4. Who owns, validates and updates Acceptance, and when was it last verified?

Validation

checks performed - outcome

1. What is the current, in-scope definition of Validation?
2. Which entities, identifiers, attributes and relationships constitute Validation?
3. Which source or master system is authoritative for Validation?
4. Who owns, validates and updates Validation, and when was it last verified?

Approval

status - approver

1. What is the current, in-scope definition of Approval?
2. Which entities, identifiers, attributes and relationships constitute Approval?
3. Which source or master system is authoritative for Approval?
4. Who owns, validates and updates Approval, and when was it last verified?

Releases

version - scope - status

1. What is the current, in-scope definition of Releases?
2. Which entities, identifiers, attributes and relationships constitute Releases?
3. Which source or master system is authoritative for Releases?
4. Who owns, validates and updates Releases, and when was it last verified?

Versions

identifier - components included

1. What is the current, in-scope definition of Versions?
2. Which entities, identifiers, attributes and relationships constitute Versions?
3. Which source or master system is authoritative for Versions?
4. Who owns, validates and updates Versions, and when was it last verified?

Rollout

strategy - stages

1. What is the current, in-scope definition of Rollout?
2. Which entities, identifiers, attributes and relationships constitute Rollout?
3. Which source or master system is authoritative for Rollout?
4. Who owns, validates and updates Rollout, and when was it last verified?

Deployment

window - environment

1. What is the current, in-scope definition of Deployment?
2. Which entities, identifiers, attributes and relationships constitute Deployment?
3. Which source or master system is authoritative for Deployment?
4. Who owns, validates and updates Deployment, and when was it last verified?

Rollback

trigger conditions - actions

1. What is the current, in-scope definition of Rollback?
2. Which entities, identifiers, attributes and relationships constitute Rollback?
3. Which source or master system is authoritative for Rollback?
4. Who owns, validates and updates Rollback, and when was it last verified?

Change Events

id - type - related release

1. What is the current, in-scope definition of Change Events?
2. Which entities, identifiers, attributes and relationships constitute Change Events?
3. Which source or master system is authoritative for Change Events?
4. Who owns, validates and updates Change Events, and when was it last verified?

Decisions

description - rationale

1. What is the current, in-scope definition of Decisions?
2. Which entities, identifiers, attributes and relationships constitute Decisions?
3. Which source or master system is authoritative for Decisions?
4. Who owns, validates and updates Decisions, and when was it last verified?

Context

constraints - assumptions

1. What is the current, in-scope definition of Context?
2. Which entities, identifiers, attributes and relationships constitute Context?
3. Which source or master system is authoritative for Context?
4. Who owns, validates and updates Context, and when was it last verified?

Traceability

links to work items - links to releases

1. What is the current, in-scope definition of Traceability?
2. Which entities, identifiers, attributes and relationships constitute Traceability?
3. Which source or master system is authoritative for Traceability?
4. Who owns, validates and updates Traceability, and when was it last verified?

Knowledge Retention and History Compaction (Value-Based)

This layer connects:

1. What is the current, in-scope definition of Knowledge Retention and History Compaction (Value-Based)?
2. Which entities, identifiers, attributes and relationships constitute Knowledge Retention and History Compaction (Value-Based)?
3. Which source or master system is authoritative for Knowledge Retention and History Compaction (Value-Based)?
4. Who owns, validates and updates Knowledge Retention and History Compaction (Value-Based), and when was it last verified?

feedbackloop

A tracked path from an operational signal to a product or model improvement.

1. What is the current, in-scope definition of feedbackloop?
2. Which entities, identifiers, attributes and relationships constitute feedbackloop?
3. Which source or master system is authoritative for feedbackloop?
4. Who owns, validates and updates feedbackloop, and when was it last verified?

feedbacksignal

The originating event or observation that triggers a feedback loop (incident, metric alert, audit finding, user complaint, test failure, retrieval failure).

1. What is the current, in-scope definition of feedbacksignal?
2. Which entities, identifiers, attributes and relationships constitute feedbacksignal?
3. Which source or master system is authoritative for feedbacksignal?
4. Who owns, validates and updates feedbacksignal, and when was it last verified?

learningcycle

A completed feedback loop that has produced a validated outcome and knowledge artifact.

1. What is the current, in-scope definition of learningcycle?
2. Which entities, identifiers, attributes and relationships constitute learningcycle?
3. Which source or master system is authoritative for learningcycle?
4. Who owns, validates and updates learningcycle, and when was it last verified?

rootcauselink

A traced connection between a signal and its identified root cause entity.

1. What is the current, in-scope definition of rootcauselink?
2. Which entities, identifiers, attributes and relationships constitute rootcauselink?
3. Which source or master system is authoritative for rootcauselink?
4. Who owns, validates and updates rootcauselink, and when was it last verified?

improvementaction

A structured action taken as a result of a feedback loop (change request, requirement update, control update, knowledge update).

1. What is the current, in-scope definition of improvementaction?
2. Which entities, identifiers, attributes and relationships constitute improvementaction?
3. Which source or master system is authoritative for improvementaction?
4. Who owns, validates and updates improvementaction, and when was it last verified?

looptrigger

The condition or threshold that activates a feedback loop.

1. What is the current, in-scope definition of looptrigger?
2. Which entities, identifiers, attributes and relationships constitute looptrigger?
3. Which source or master system is authoritative for looptrigger?
4. Who owns, validates and updates looptrigger, and when was it last verified?

loopoutcome

The documented result of a feedback loop: resolved, deferred, insufficientsignal, or ongoing.

1. What is the current, in-scope definition of loopoutcome?
2. Which entities, identifiers, attributes and relationships constitute loopoutcome?
3. Which source or master system is authoritative for loopoutcome?
4. Who owns, validates and updates loopoutcome, and when was it last verified?

pipeline

An automated sequence of stages that validates and promotes a change from source to production.

1. What is the current, in-scope definition of pipeline?
2. Which entities, identifiers, attributes and relationships constitute pipeline?
3. Which source or master system is authoritative for pipeline?
4. Who owns, validates and updates pipeline, and when was it last verified?

pipelinestage

A discrete phase of the pipeline (build, test, scan, deploy, smoke test, promote).

1. What is the current, in-scope definition of pipelinestage?
2. Which entities, identifiers, attributes and relationships constitute pipelinestage?
3. Which source or master system is authoritative for pipelinestage?
4. Who owns, validates and updates pipelinestage, and when was it last verified?

automationgate

A quality gate that must pass before the pipeline can proceed to the next stage.

1. What is the current, in-scope definition of automationgate?
2. Which entities, identifiers, attributes and relationships constitute automationgate?
3. Which source or master system is authoritative for automationgate?
4. Who owns, validates and updates automationgate, and when was it last verified?

qualitygateexecution

A recorded execution of an automation gate with result and metrics.

1. What is the current, in-scope definition of qualitygateexecution?
2. Which entities, identifiers, attributes and relationships constitute qualitygateexecution?
3. Which source or master system is authoritative for qualitygateexecution?
4. Who owns, validates and updates qualitygateexecution, and when was it last verified?

promotionrule

A rule defining when a version may be promoted to the next environment.

1. What is the current, in-scope definition of promotionrule?
2. Which entities, identifiers, attributes and relationships constitute promotionrule?
3. Which source or master system is authoritative for promotionrule?
4. Who owns, validates and updates promotionrule, and when was it last verified?

environmentpromotion

A recorded movement of a version from one environment to another.

1. What is the current, in-scope definition of environmentpromotion?
2. Which entities, identifiers, attributes and relationships constitute environmentpromotion?
3. Which source or master system is authoritative for environmentpromotion?
4. Who owns, validates and updates environmentpromotion, and when was it last verified?

rollbacktrigger

A condition that activates an automated or manual rollback.

1. What is the current, in-scope definition of rollbacktrigger?
2. Which entities, identifiers, attributes and relationships constitute rollbacktrigger?
3. Which source or master system is authoritative for rollbacktrigger?
4. Who owns, validates and updates rollbacktrigger, and when was it last verified?

pipelinerun

A recorded execution of the full pipeline.

1. What is the current, in-scope definition of pipelinerun?
2. Which entities, identifiers, attributes and relationships constitute pipelinerun?
3. Which source or master system is authoritative for pipelinerun?
4. Who owns, validates and updates pipelinerun, and when was it last verified?

pipelineartifact

An artifact produced by a pipeline run (binary, image, report, SBOM).

1. What is the current, in-scope definition of pipelineartifact?
2. Which entities, identifiers, attributes and relationships constitute pipelineartifact?
3. Which source or master system is authoritative for pipelineartifact?
4. Who owns, validates and updates pipelineartifact, and when was it last verified?

migrationplan

A structured plan for a multi-step system or data migration.

1. What is the current, in-scope definition of migrationplan?
2. Which entities, identifiers, attributes and relationships constitute migrationplan?
3. Which source or master system is authoritative for migrationplan?
4. Who owns, validates and updates migrationplan, and when was it last verified?

schemamigration

A specific migration affecting database or API schema.

1. What is the current, in-scope definition of schemamigration?
2. Which entities, identifiers, attributes and relationships constitute schemamigration?
3. Which source or master system is authoritative for schemamigration?
4. Who owns, validates and updates schemamigration, and when was it last verified?

databackfill

A targeted operation to populate or transform existing data in place.

1. What is the current, in-scope definition of databackfill?
2. Which entities, identifiers, attributes and relationships constitute databackfill?
3. Which source or master system is authoritative for databackfill?
4. Who owns, validates and updates databackfill, and when was it last verified?

compatibilitywindow

A declared period during which old and new versions must coexist.

1. What is the current, in-scope definition of compatibilitywindow?
2. Which entities, identifiers, attributes and relationships constitute compatibilitywindow?
3. Which source or master system is authoritative for compatibilitywindow?
4. Who owns, validates and updates compatibilitywindow, and when was it last verified?

dualwriteperiod

A specific compatibility window where both old and new paths receive writes.

1. What is the current, in-scope definition of dualwriteperiod?
2. Which entities, identifiers, attributes and relationships constitute dualwriteperiod?
3. Which source or master system is authoritative for dualwriteperiod?
4. Who owns, validates and updates dualwriteperiod, and when was it last verified?

cutoverplan

The defined steps for switching from old to new version at a specific point in time.

1. What is the current, in-scope definition of cutoverplan?
2. Which entities, identifiers, attributes and relationships constitute cutoverplan?
3. Which source or master system is authoritative for cutoverplan?
4. Who owns, validates and updates cutoverplan, and when was it last verified?

refactorstream

A long-running code restructuring effort tracked as a series of work items.

1. What is the current, in-scope definition of refactorstream?
2. Which entities, identifiers, attributes and relationships constitute refactorstream?
3. Which source or master system is authoritative for refactorstream?
4. Who owns, validates and updates refactorstream, and when was it last verified?

technicaldebtburndown

A tracked reduction of identified technical debt over time.

1. What is the current, in-scope definition of technicaldebtburndown?
2. Which entities, identifiers, attributes and relationships constitute technicaldebtburndown?
3. Which source or master system is authoritative for technicaldebtburndown?
4. Who owns, validates and updates technicaldebtburndown, and when was it last verified?

migrationrisk

A risk specifically associated with a migration operation.

1. What is the current, in-scope definition of migrationrisk?
2. Which entities, identifiers, attributes and relationships constitute migrationrisk?
3. Which source or master system is authoritative for migrationrisk?
4. Who owns, validates and updates migrationrisk, and when was it last verified?

Retrospective

id, scope (initiative/cycle ref), participants/owner - assesses (work items, releases, decisions evaluated)

1. What is the current, in-scope definition of Retrospective?
2. Which entities, identifiers, attributes and relationships constitute Retrospective?
3. Which source or master system is authoritative for Retrospective?
4. Who owns, validates and updates Retrospective, and when was it last verified?

Effectiveness Assessment

id, dimensions (process, decisions, approach) - optional flow metrics, plan-vs-actual - effectiveness rating + rationale

1. What is the current, in-scope definition of Effectiveness Assessment?
2. Which entities, identifiers, attributes and relationships constitute Effectiveness Assessment?
3. Which source or master system is authoritative for Effectiveness Assessment?
4. Who owns, validates and updates Effectiveness Assessment, and when was it last verified?

Lessons

id, statement, polarity (kept|change), evidence

1. What is the current, in-scope definition of Lessons?
2. Which entities, identifiers, attributes and relationships constitute Lessons?
3. Which source or master system is authoritative for Lessons?
4. Who owns, validates and updates Lessons, and when was it last verified?

Improvement Actions

id, action, owner (b11), target date - linked work item (b8.801) or policy change (00-policies)

1. What is the current, in-scope definition of Improvement Actions?
2. Which entities, identifiers, attributes and relationships constitute Improvement Actions?
3. Which source or master system is authoritative for Improvement Actions?
4. Who owns, validates and updates Improvement Actions, and when was it last verified?

Improvement Verification

id, verifies (prior improvement ref), observed effect, status

1. What is the current, in-scope definition of Improvement Verification?
2. Which entities, identifiers, attributes and relationships constitute Improvement Verification?
3. Which source or master system is authoritative for Improvement Verification?
4. Who owns, validates and updates Improvement Verification, and when was it last verified?

Index

indexed entities - references

1. What is the current, in-scope definition of Index?
2. Which entities, identifiers, attributes and relationships constitute Index?
3. Which source or master system is authoritative for Index?
4. Who owns, validates and updates Index, and when was it last verified?

Navigation

nodes - hierarchy

1. What is the current, in-scope definition of Navigation?
2. Which entities, identifiers, attributes and relationships constitute Navigation?
3. Which source or master system is authoritative for Navigation?
4. Who owns, validates and updates Navigation, and when was it last verified?

Classification

topics - tags

1. What is the current, in-scope definition of Classification?
2. Which entities, identifiers, attributes and relationships constitute Classification?
3. Which source or master system is authoritative for Classification?
4. Who owns, validates and updates Classification, and when was it last verified?

Search

profiles - filters

1. What is the current, in-scope definition of Search?
2. Which entities, identifiers, attributes and relationships constitute Search?
3. Which source or master system is authoritative for Search?
4. Who owns, validates and updates Search, and when was it last verified?

Embeddings

vectors - linked content

1. What is the current, in-scope definition of Embeddings?
2. Which entities, identifiers, attributes and relationships constitute Embeddings?
3. Which source or master system is authoritative for Embeddings?
4. Who owns, validates and updates Embeddings, and when was it last verified?

Trace Nodes

Each trace node SHOULD include:

1. What is the current, in-scope definition of Trace Nodes?
2. Which entities, identifiers, attributes and relationships constitute Trace Nodes?
3. Which source or master system is authoritative for Trace Nodes?
4. Who owns, validates and updates Trace Nodes, and when was it last verified?

Trace Links

Each trace link SHOULD include:

1. What is the current, in-scope definition of Trace Links?
2. Which entities, identifiers, attributes and relationships constitute Trace Links?
3. Which source or master system is authoritative for Trace Links?
4. Who owns, validates and updates Trace Links, and when was it last verified?

Trace Paths

Each trace path SHOULD include:

1. What is the current, in-scope definition of Trace Paths?
2. Which entities, identifiers, attributes and relationships constitute Trace Paths?
3. Which source or master system is authoritative for Trace Paths?
4. Who owns, validates and updates Trace Paths, and when was it last verified?

Impact Paths

Each impact path SHOULD include:

1. What is the current, in-scope definition of Impact Paths?
2. Which entities, identifiers, attributes and relationships constitute Impact Paths?
3. Which source or master system is authoritative for Impact Paths?
4. Who owns, validates and updates Impact Paths, and when was it last verified?

Graph Views

Each graph view SHOULD include:

1. What is the current, in-scope definition of Graph Views?
2. Which entities, identifiers, attributes and relationships constitute Graph Views?
3. Which source or master system is authoritative for Graph Views?
4. Who owns, validates and updates Graph Views, and when was it last verified?

Source

origin - type

1. What is the current, in-scope definition of Source?
2. Which entities, identifiers, attributes and relationships constitute Source?
3. Which source or master system is authoritative for Source?
4. Who owns, validates and updates Source, and when was it last verified?

Provenance

derivation steps - transformations

1. What is the current, in-scope definition of Provenance?
2. Which entities, identifiers, attributes and relationships constitute Provenance?
3. Which source or master system is authoritative for Provenance?
4. Who owns, validates and updates Provenance, and when was it last verified?

Evidence

supporting data - references

1. What is the current, in-scope definition of Evidence?
2. Which entities, identifiers, attributes and relationships constitute Evidence?
3. Which source or master system is authoritative for Evidence?
4. Who owns, validates and updates Evidence, and when was it last verified?

Confidence

score - status

1. What is the current, in-scope definition of Confidence?
2. Which entities, identifiers, attributes and relationships constitute Confidence?
3. Which source or master system is authoritative for Confidence?
4. Who owns, validates and updates Confidence, and when was it last verified?

Coverage

entities covered - coverage percentage

1. What is the current, in-scope definition of Coverage?
2. Which entities, identifiers, attributes and relationships constitute Coverage?
3. Which source or master system is authoritative for Coverage?
4. Who owns, validates and updates Coverage, and when was it last verified?

Gaps

missing elements - affected areas

1. What is the current, in-scope definition of Gaps?
2. Which entities, identifiers, attributes and relationships constitute Gaps?
3. Which source or master system is authoritative for Gaps?
4. Who owns, validates and updates Gaps, and when was it last verified?

Inconsistencies

conflicting entities - type of conflict

1. What is the current, in-scope definition of Inconsistencies?
2. Which entities, identifiers, attributes and relationships constitute Inconsistencies?
3. Which source or master system is authoritative for Inconsistencies?
4. Who owns, validates and updates Inconsistencies, and when was it last verified?

Checks

validation rules - results

1. What is the current, in-scope definition of Checks?
2. Which entities, identifiers, attributes and relationships constitute Checks?
3. Which source or master system is authoritative for Checks?
4. Who owns, validates and updates Checks, and when was it last verified?

Retrieval Units

Each retrieval unit SHOULD include:

1. What is the current, in-scope definition of Retrieval Units?
2. Which entities, identifiers, attributes and relationships constitute Retrieval Units?
3. Which source or master system is authoritative for Retrieval Units?
4. Who owns, validates and updates Retrieval Units, and when was it last verified?

Chunking Strategies

Each strategy SHOULD include:

1. What is the current, in-scope definition of Chunking Strategies?
2. Which entities, identifiers, attributes and relationships constitute Chunking Strategies?
3. Which source or master system is authoritative for Chunking Strategies?
4. Who owns, validates and updates Chunking Strategies, and when was it last verified?

Embedding Records

Each embedding record SHOULD include:

1. What is the current, in-scope definition of Embedding Records?
2. Which entities, identifiers, attributes and relationships constitute Embedding Records?
3. Which source or master system is authoritative for Embedding Records?
4. Who owns, validates and updates Embedding Records, and when was it last verified?

Retrieval Profiles

Each profile SHOULD include:

1. What is the current, in-scope definition of Retrieval Profiles?
2. Which entities, identifiers, attributes and relationships constitute Retrieval Profiles?
3. Which source or master system is authoritative for Retrieval Profiles?
4. Who owns, validates and updates Retrieval Profiles, and when was it last verified?

Context Packages

Each context package SHOULD include:

1. What is the current, in-scope definition of Context Packages?
2. Which entities, identifiers, attributes and relationships constitute Context Packages?
3. Which source or master system is authoritative for Context Packages?
4. Who owns, validates and updates Context Packages, and when was it last verified?

ontologyterm

A named concept in the AISMM vocabulary with a stable ID and definition.

1. What is the current, in-scope definition of ontologyterm?
2. Which entities, identifiers, attributes and relationships constitute ontologyterm?
3. Which source or master system is authoritative for ontologyterm?
4. Who owns, validates and updates ontologyterm, and when was it last verified?

relationshiptype

A canonical typed relationship between AISMM entities with defined semantics.

1. What is the current, in-scope definition of relationshiptype?
2. Which entities, identifiers, attributes and relationships constitute relationshiptype?
3. Which source or master system is authoritative for relationshiptype?
4. Who owns, validates and updates relationshiptype, and when was it last verified?

edgesemantic

A declaration of what a relationship type implies (direction, transitivity, invertibility).

1. What is the current, in-scope definition of edgesemantic?
2. Which entities, identifiers, attributes and relationships constitute edgesemantic?
3. Which source or master system is authoritative for edgesemantic?
4. Who owns, validates and updates edgesemantic, and when was it last verified?

vocabularyentry

A term in the AISMM vocabulary with synonyms and deprecation status.

1. What is the current, in-scope definition of vocabularyentry?
2. Which entities, identifiers, attributes and relationships constitute vocabularyentry?
3. Which source or master system is authoritative for vocabularyentry?
4. Who owns, validates and updates vocabularyentry, and when was it last verified?

synonym

An alternative name for an ontology term or relationship type.

1. What is the current, in-scope definition of synonym?
2. Which entities, identifiers, attributes and relationships constitute synonym?
3. Which source or master system is authoritative for synonym?
4. Who owns, validates and updates synonym, and when was it last verified?

deprecatedterm

A term that has been superseded and should no longer be used.

1. What is the current, in-scope definition of deprecatedterm?
2. Which entities, identifiers, attributes and relationships constitute deprecatedterm?
3. Which source or master system is authoritative for deprecatedterm?
4. Who owns, validates and updates deprecatedterm, and when was it last verified?

Ingestion Binding

id, targetlayers - owningsystem (b2.205/b2.204 ref) - connectorreference (MCP/tool/API) - recipereference (00-policies recipe id + version) - trigger/schedule - ownerofsource (b11.1102 ref) - validationpolicy (ref into aismm-owner-validation-and-attestation.md)

1. What is the current, in-scope definition of Ingestion Binding?
2. Which entities, identifiers, attributes and relationships constitute Ingestion Binding?
3. Which source or master system is authoritative for Ingestion Binding?
4. Who owns, validates and updates Ingestion Binding, and when was it last verified?

Field Mapping

source field → record field - transform notes / normalization

1. What is the current, in-scope definition of Field Mapping?
2. Which entities, identifiers, attributes and relationships constitute Field Mapping?
3. Which source or master system is authoritative for Field Mapping?
4. Who owns, validates and updates Field Mapping, and when was it last verified?

Ingestion Run

id, binding ref, recipe version, connector, agent identity - run timestamp, source snapshot/digest - producedrecordids, updatedrecordids - resulting validationstatus

1. What is the current, in-scope definition of Ingestion Run?
2. Which entities, identifiers, attributes and relationships constitute Ingestion Run?
3. Which source or master system is authoritative for Ingestion Run?
4. Who owns, validates and updates Ingestion Run, and when was it last verified?

dataproduct

A well-defined, owned, versioned data asset published for consumption.

1. What is the current, in-scope definition of dataproduct?
2. Which entities, identifiers, attributes and relationships constitute dataproduct?
3. Which source or master system is authoritative for dataproduct?
4. Who owns, validates and updates dataproduct, and when was it last verified?

datacontract

A formal agreement defining the schema, quality, and delivery guarantees of a data product.

1. What is the current, in-scope definition of datacontract?
2. Which entities, identifiers, attributes and relationships constitute datacontract?
3. Which source or master system is authoritative for datacontract?
4. Who owns, validates and updates datacontract, and when was it last verified?

dataconsumer

A system, service, or team that depends on a data product.

1. What is the current, in-scope definition of dataconsumer?
2. Which entities, identifiers, attributes and relationships constitute dataconsumer?
3. Which source or master system is authoritative for dataconsumer?
4. Who owns, validates and updates dataconsumer, and when was it last verified?

dataowner

The team or person responsible for a data product.

1. What is the current, in-scope definition of dataowner?
2. Which entities, identifiers, attributes and relationships constitute dataowner?
3. Which source or master system is authoritative for dataowner?
4. Who owns, validates and updates dataowner, and when was it last verified?

datasla

Service-level agreement for a data product (freshness, availability, quality).

1. What is the current, in-scope definition of datasla?
2. Which entities, identifiers, attributes and relationships constitute datasla?
3. Which source or master system is authoritative for datasla?
4. Who owns, validates and updates datasla, and when was it last verified?

datalineage

A lineage record describing the provenance graph for a data asset.

1. What is the current, in-scope definition of datalineage?
2. Which entities, identifiers, attributes and relationships constitute datalineage?
3. Which source or master system is authoritative for datalineage?
4. Who owns, validates and updates datalineage, and when was it last verified?

lineageedge

A directed edge from a source asset to a target asset, representing a transformation or data flow.

1. What is the current, in-scope definition of lineageedge?
2. Which entities, identifiers, attributes and relationships constitute lineageedge?
3. Which source or master system is authoritative for lineageedge?
4. Who owns, validates and updates lineageedge, and when was it last verified?

schemaversion

A named, versioned snapshot of a data asset's schema.

1. What is the current, in-scope definition of schemaversion?
2. Which entities, identifiers, attributes and relationships constitute schemaversion?
3. Which source or master system is authoritative for schemaversion?
4. Who owns, validates and updates schemaversion, and when was it last verified?

schemachange

A recorded change between schema versions (add, remove, rename, retype, etc.).

1. What is the current, in-scope definition of schemachange?
2. Which entities, identifiers, attributes and relationships constitute schemachange?
3. Which source or master system is authoritative for schemachange?
4. Who owns, validates and updates schemachange, and when was it last verified?

backwardcompatibility

A verdict on whether a schema change preserves compatibility for existing consumers.

1. What is the current, in-scope definition of backwardcompatibility?
2. Which entities, identifiers, attributes and relationships constitute backwardcompatibility?
3. Which source or master system is authoritative for backwardcompatibility?
4. Who owns, validates and updates backwardcompatibility, and when was it last verified?

feature

A computed input signal used by one or more models.

1. What is the current, in-scope definition of feature?
2. Which entities, identifiers, attributes and relationships constitute feature?
3. Which source or master system is authoritative for feature?
4. Who owns, validates and updates feature, and when was it last verified?

featurestore

A managed store that materializes and serves features.

1. What is the current, in-scope definition of featurestore?
2. Which entities, identifiers, attributes and relationships constitute featurestore?
3. Which source or master system is authoritative for featurestore?
4. Who owns, validates and updates featurestore, and when was it last verified?

embeddingindex

A vector index built from an embedding model over a corpus.

1. What is the current, in-scope definition of embeddingindex?
2. Which entities, identifiers, attributes and relationships constitute embeddingindex?
3. Which source or master system is authoritative for embeddingindex?
4. Who owns, validates and updates embeddingindex, and when was it last verified?

embeddingmodel

The model that produces vector representations for the index.

1. What is the current, in-scope definition of embeddingmodel?
2. Which entities, identifiers, attributes and relationships constitute embeddingmodel?
3. Which source or master system is authoritative for embeddingmodel?
4. Who owns, validates and updates embeddingmodel, and when was it last verified?

indexrefreshpolicy

The cadence and trigger rules for refreshing an index or feature.

1. What is the current, in-scope definition of indexrefreshpolicy?
2. Which entities, identifiers, attributes and relationships constitute indexrefreshpolicy?
3. Which source or master system is authoritative for indexrefreshpolicy?
4. Who owns, validates and updates indexrefreshpolicy, and when was it last verified?

invalidationrule

A rule specifying when a feature or embedding becomes stale and must be recomputed.

1. What is the current, in-scope definition of invalidationrule?
2. Which entities, identifiers, attributes and relationships constitute invalidationrule?
3. Which source or master system is authoritative for invalidationrule?
4. Who owns, validates and updates invalidationrule, and when was it last verified?

model

A named model with a stable identity across versions.

1. What is the current, in-scope definition of model?
2. Which entities, identifiers, attributes and relationships constitute model?
3. Which source or master system is authoritative for model?
4. Who owns, validates and updates model, and when was it last verified?

modelversion

A specific, immutable version of a model.

1. What is the current, in-scope definition of modelversion?
2. Which entities, identifiers, attributes and relationships constitute modelversion?
3. Which source or master system is authoritative for modelversion?
4. Who owns, validates and updates modelversion, and when was it last verified?

modelcard

Documentation of a model version's intended use, limitations, and evaluation results.

1. What is the current, in-scope definition of modelcard?
2. Which entities, identifiers, attributes and relationships constitute modelcard?
3. Which source or master system is authoritative for modelcard?
4. Who owns, validates and updates modelcard, and when was it last verified?

modelartifact

The stored binary or package for a model version.

1. What is the current, in-scope definition of modelartifact?
2. Which entities, identifiers, attributes and relationships constitute modelartifact?
3. Which source or master system is authoritative for modelartifact?
4. Who owns, validates and updates modelartifact, and when was it last verified?

inferenceendpoint

A serving endpoint exposing a model version for inference.

1. What is the current, in-scope definition of inferenceendpoint?
2. Which entities, identifiers, attributes and relationships constitute inferenceendpoint?
3. Which source or master system is authoritative for inferenceendpoint?
4. Who owns, validates and updates inferenceendpoint, and when was it last verified?

trainingrun

A single execution that produces or updates a model version.

1. What is the current, in-scope definition of trainingrun?
2. Which entities, identifiers, attributes and relationships constitute trainingrun?
3. Which source or master system is authoritative for trainingrun?
4. Who owns, validates and updates trainingrun, and when was it last verified?

evaluationrun

A single execution that measures a model version against a dataset.

1. What is the current, in-scope definition of evaluationrun?
2. Which entities, identifiers, attributes and relationships constitute evaluationrun?
3. Which source or master system is authoritative for evaluationrun?
4. Who owns, validates and updates evaluationrun, and when was it last verified?

experiment

A grouping of related training and evaluation runs under a hypothesis.

1. What is the current, in-scope definition of experiment?
2. Which entities, identifiers, attributes and relationships constitute experiment?
3. Which source or master system is authoritative for experiment?
4. Who owns, validates and updates experiment, and when was it last verified?

metric

A named, valued measurement produced by a run (accuracy, F1, AUC, etc.).

1. What is the current, in-scope definition of metric?
2. Which entities, identifiers, attributes and relationships constitute metric?
3. Which source or master system is authoritative for metric?
4. Who owns, validates and updates metric, and when was it last verified?

goldendataset

A curated, stable dataset used as the evaluation reference.

1. What is the current, in-scope definition of goldendataset?
2. Which entities, identifiers, attributes and relationships constitute goldendataset?
3. Which source or master system is authoritative for goldendataset?
4. Who owns, validates and updates goldendataset, and when was it last verified?

driftsignal

An observation that input data or predictions have shifted from a baseline.

1. What is the current, in-scope definition of driftsignal?
2. Which entities, identifiers, attributes and relationships constitute driftsignal?
3. Which source or master system is authoritative for driftsignal?
4. Who owns, validates and updates driftsignal, and when was it last verified?

driftcheck

A scheduled or continuous check that evaluates drift conditions.

1. What is the current, in-scope definition of driftcheck?
2. Which entities, identifiers, attributes and relationships constitute driftcheck?
3. Which source or master system is authoritative for driftcheck?
4. Who owns, validates and updates driftcheck, and when was it last verified?

retrainingtrigger

A rule that starts a retraining cycle when conditions are met.

1. What is the current, in-scope definition of retrainingtrigger?
2. Which entities, identifiers, attributes and relationships constitute retrainingtrigger?
3. Which source or master system is authoritative for retrainingtrigger?
4. Who owns, validates and updates retrainingtrigger, and when was it last verified?

modelmonitor

A monitor observing a model version's live behavior and metrics.

1. What is the current, in-scope definition of modelmonitor?
2. Which entities, identifiers, attributes and relationships constitute modelmonitor?
3. Which source or master system is authoritative for modelmonitor?
4. Who owns, validates and updates modelmonitor, and when was it last verified?

performanceregression

A detected drop in a model version's quality against expectations.

1. What is the current, in-scope definition of performanceregression?
2. Which entities, identifiers, attributes and relationships constitute performanceregression?
3. Which source or master system is authoritative for performanceregression?
4. Who owns, validates and updates performanceregression, and when was it last verified?

labelingtask

A defined task producing labels over a set of data items.

1. What is the current, in-scope definition of labelingtask?
2. Which entities, identifiers, attributes and relationships constitute labelingtask?
3. Which source or master system is authoritative for labelingtask?
4. Who owns, validates and updates labelingtask, and when was it last verified?

annotation

A single label applied to a data item within a task.

1. What is the current, in-scope definition of annotation?
2. Which entities, identifiers, attributes and relationships constitute annotation?
3. Which source or master system is authoritative for annotation?
4. Who owns, validates and updates annotation, and when was it last verified?

annotator

The human or automated agent that produced an annotation.

1. What is the current, in-scope definition of annotator?
2. Which entities, identifiers, attributes and relationships constitute annotator?
3. Which source or master system is authoritative for annotator?
4. Who owns, validates and updates annotator, and when was it last verified?

groundtruth

A curated dataset of accepted labels used as reference.

1. What is the current, in-scope definition of groundtruth?
2. Which entities, identifiers, attributes and relationships constitute groundtruth?
3. Which source or master system is authoritative for groundtruth?
4. Who owns, validates and updates groundtruth, and when was it last verified?

labelquality

An assessment of annotation reliability (agreement, confidence).

1. What is the current, in-scope definition of labelquality?
2. Which entities, identifiers, attributes and relationships constitute labelquality?
3. Which source or master system is authoritative for labelquality?
4. Who owns, validates and updates labelquality, and when was it last verified?

dataqualityrule

A defined expectation a data asset must satisfy (e.g. non-null, range, uniqueness).

1. What is the current, in-scope definition of dataqualityrule?
2. Which entities, identifiers, attributes and relationships constitute dataqualityrule?
3. Which source or master system is authoritative for dataqualityrule?
4. Who owns, validates and updates dataqualityrule, and when was it last verified?

dataqualitymetric

A measured value of a quality dimension (completeness, accuracy, freshness).

1. What is the current, in-scope definition of dataqualitymetric?
2. Which entities, identifiers, attributes and relationships constitute dataqualitymetric?
3. Which source or master system is authoritative for dataqualitymetric?
4. Who owns, validates and updates dataqualitymetric, and when was it last verified?

dataobservabilitysignal

A monitored signal over a data asset (volume, latency, anomaly).

1. What is the current, in-scope definition of dataobservabilitysignal?
2. Which entities, identifiers, attributes and relationships constitute dataobservabilitysignal?
3. Which source or master system is authoritative for dataobservabilitysignal?
4. Who owns, validates and updates dataobservabilitysignal, and when was it last verified?

dataincident

A recorded event where data quality or availability was breached.

1. What is the current, in-scope definition of dataincident?
2. Which entities, identifiers, attributes and relationships constitute dataincident?
3. Which source or master system is authoritative for dataincident?
4. Who owns, validates and updates dataincident, and when was it last verified?

Team Topology and RACI

yaml team: id: team.<org.<name name: string type: streamaligned | platform | enabling | complicatedsubsystem | external members: [role entityid] collaborationmode: collaborationmode entityid

1. What is the current, in-scope definition of Team Topology and RACI?
2. Which entities, identifiers, attributes and relationships constitute Team Topology and RACI?
3. Which source or master system is authoritative for Team Topology and RACI?
4. Who owns, validates and updates Team Topology and RACI, and when was it last verified?

Ownership Graph

Required information about Ownership Graph in the Ownership Graph layer.

1. What is the current, in-scope definition of Ownership Graph?
2. Which entities, identifiers, attributes and relationships constitute Ownership Graph?
3. Which source or master system is authoritative for Ownership Graph?
4. Who owns, validates and updates Ownership Graph, and when was it last verified?

Decision Rights and Governance

yaml decisionright: id: decisionright.<scope.<decisiontype decisiontype: string authority: team or person entityid approvalpolicy: approvalpolicy entityid escalationpath: [team entityid]

1. What is the current, in-scope definition of Decision Rights and Governance?
2. Which entities, identifiers, attributes and relationships constitute Decision Rights and Governance?
3. Which source or master system is authoritative for Decision Rights and Governance?
4. Who owns, validates and updates Decision Rights and Governance, and when was it last verified?

Skills and Capability Matrix

yaml teamcapability: id: teamcapability.<team.<skill team: team entityid skill: skill entityid level: competencylevel entityid count: integer

1. What is the current, in-scope definition of Skills and Capability Matrix?
2. Which entities, identifiers, attributes and relationships constitute Skills and Capability Matrix?
3. Which source or master system is authoritative for Skills and Capability Matrix?
4. Who owns, validates and updates Skills and Capability Matrix, and when was it last verified?

Vendors and External Responsibilities

yaml vendor: id: vendor.<name name: string type: cloudprovider | saas | professionalservices | opensourcesteward | hardware supportcontracts: [supportcontract entityid] ownedexternalsystems: [entityid]

1. What is the current, in-scope definition of Vendors and External Responsibilities?
2. Which entities, identifiers, attributes and relationships constitute Vendors and External Responsibilities?
3. Which source or master system is authoritative for Vendors and External Responsibilities?
4. Who owns, validates and updates Vendors and External Responsibilities, and when was it last verified?

Capacity and Allocation

yaml capacity: id: capacity.<team.<period team: team entityid period: string e.g. 2026-Q2 totalcapacity: float person-weeks availablecapacity: float

1. What is the current, in-scope definition of Capacity and Allocation?
2. Which entities, identifiers, attributes and relationships constitute Capacity and Allocation?
3. Which source or master system is authoritative for Capacity and Allocation?
4. Who owns, validates and updates Capacity and Allocation, and when was it last verified?

Cost Allocation and Showback

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Cost Allocation and Showback?
2. Which entities, identifiers, attributes and relationships constitute Cost Allocation and Showback?
3. Which source or master system is authoritative for Cost Allocation and Showback?
4. Who owns, validates and updates Cost Allocation and Showback, and when was it last verified?

Capacity and Commitment Management

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Capacity and Commitment Management?
2. Which entities, identifiers, attributes and relationships constitute Capacity and Commitment Management?
3. Which source or master system is authoritative for Capacity and Commitment Management?
4. Who owns, validates and updates Capacity and Commitment Management, and when was it last verified?

Token and Inference Economics

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Token and Inference Economics?
2. Which entities, identifiers, attributes and relationships constitute Token and Inference Economics?
3. Which source or master system is authoritative for Token and Inference Economics?
4. Who owns, validates and updates Token and Inference Economics, and when was it last verified?

Cost of Quality and Incident

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Cost of Quality and Incident?
2. Which entities, identifiers, attributes and relationships constitute Cost of Quality and Incident?
3. Which source or master system is authoritative for Cost of Quality and Incident?
4. Who owns, validates and updates Cost of Quality and Incident, and when was it last verified?

Unit Economics by Service, Tenant and Request

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Unit Economics by Service, Tenant and Request?
2. Which entities, identifiers, attributes and relationships constitute Unit Economics by Service, Tenant and Request?
3. Which source or master system is authoritative for Unit Economics by Service, Tenant and Request?
4. Who owns, validates and updates Unit Economics by Service, Tenant and Request, and when was it last verified?

Carbon and Sustainability Accounting

b0.006 - product economics - b6.601 - runtime instances (cost sources) - b7.702 - financial risks - b8.804 - releases (cost attribution) - b10.1004 - model inference endpoints - b11.1102 - ownership and cost responsibility

1. What is the current, in-scope definition of Carbon and Sustainability Accounting?
2. Which entities, identifiers, attributes and relationships constitute Carbon and Sustainability Accounting?
3. Which source or master system is authoritative for Carbon and Sustainability Accounting?
4. Who owns, validates and updates Carbon and Sustainability Accounting, and when was it last verified?