EM-LND-11 · Landscape · W3
Operations and supply chain landscape
Flows of sourcing, transformations, inventory and deliveries with item-level traceability.
Partially published; research continues
Claude: complete-frozen-study; Grok: prompt-ready-awaiting-action-time-confirmation.
Published results
Research note, in Russian: Canonical/runtime promotion remains governed by the package allocation, identity and dependency holds.
Subject boundary and candidate types
- OperationsLandscape
- SupplyNetwork
Deep research questions
- How to find affected items by a component batch?
- Where does an unknown supplier break traceability?
- How to link the process to actual movement?
Verifiable invariants
- Genealogy references events
- A plan is not a movement
- Unknown origin is flagged
End-to-end acceptance scenario
A recalled batch identifies only provably affected units and, separately, potentially affected ones.
Negative case
A BOM automatically proves the actual composition of every batch.
Approaches to compare
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
Candidates in the live catalogue
The boundary and the reuse / extension / new model route are not chosen yet.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.