Inventory answers what exists. A world model answers what it means.
A list of resources cannot explain whether two services form one customer path, whether a database replacement violates an objective, or whether an apparently idle component is part of a recovery plan.
A world model adds stable identity, typed relationships, provider-specific semantics, customer objectives, constraints, known gaps, and temporal context.
Temporal context changes the recommendation
The same utilization level can mean normal seasonality, a release regression, an emerging growth pattern, or a measurement gap. Historical topology and retained outcomes help separate those cases.
- Current and previous resource relationships.
- Observation freshness and known coverage gaps.
- Prior plans, assumptions, actions, rollbacks, and verified outcomes.
- Provider-native constraints that cannot be flattened into false equivalence.
The model informs decisions; it does not authorize them
Semantic understanding can establish context and generate candidate plans. Independent policy and action evaluation still determine whether an exact mutation has current authority.
Common questions
Is a world model a graph database?
Not necessarily. It is a semantic and temporal contract. It can be represented with relational projections, graph views, or both; the storage engine is an implementation choice rather than the product definition.