Landscape of contracts and obligations
A map of parties, agreements, obligations, deadlines and fulfillment dependencies.
Bundle → Layer → Finding → Questions Filled
2 bundles · 2 layers · 4 findings · 8 questions
Agreements and parties Which agreements exist, between whom and over which period.
Agreement map
Agreements with their parties as they were at each time.
Historical parties
Parties kept as they were when the agreement applied.
- Which parties were bound by this agreement, and over which period?
- Has a party changed through assignment, merger or renaming?
Conflicts
Agreements whose terms contradict each other.
- Which agreements impose conflicting terms on the same subject?
- Which agreement prevails, and on what basis?
Obligations Individual obligations with their own terms and dependencies.
Obligation terms
Each obligation with its own start, end and state.
Surviving obligations
Obligations that continue after the agreement ends.
- Which obligations survive termination or expiry of the agreement?
- What evidence supports the state of each surviving obligation?
Dependencies and disputes
Conditions that depend on another party, and disputes.
- Which obligations depend on performance by someone else?
- Is a late item in dispute or simply overdue?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-09W2landscapeContractLandscapeObligationNetwork
What it is Filled
A map of parties, agreements, obligations, deadlines and fulfillment dependencies.
Why it exists Filled
A map of parties, agreements, obligations, deadlines and fulfillment dependencies.
Distinguishing features Filled
- The term of an agreement and the term of each obligation are recorded separately.
- Parties are kept as they stood at the time, not overwritten by later changes.
- A dispute is a separate state from a delinquency.
- Distinct from a single contract record; this view maps many agreements and their interplay.
What robots and AI may and may not do Filled
Must not
- Delete a confidentiality or other surviving obligation because the agreement expired.
- Replace historical parties with their current names or successors.
- Mark a disputed item as delinquent without recording the dispute.
- Interpret contract terms as legal advice to any party.
Only with a human decision
- Deciding which agreement prevails when terms conflict.
- Closing or waiving an obligation.
- Classifying an item as disputed or in breach.
May
- List obligations that remain active after an agreement expires.
- Flag agreements with conflicting terms on the same subject.
- Show which obligations wait on performance by another party.
Moral aspects Filled
- Lost surviving obligations can expose confidential information or personal data of third parties.
- Mislabelling a dispute as a default can damage a counterparty's standing unfairly.
Who is affected
- Contract parties and their staff
- People whose data the contracts protect
- Legal and procurement teams
Owners Filled
Steward
A contract and obligation steward is accountable for agreement coverage, obligation traceability and authoritative source references.
Master systems
- Contract lifecycle management system.
- Counterparty master data and legal succession registry.
- Obligation tracking and fulfillment evidence register.
- Legal dispute and decision register.
Links to other meta-models Filled
references
- WM-ECO-006 - conceptual-candidate
- WM-XCT-029 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a landscape identifier and version, with agreements and obligations referenced by their own identifiers.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A network of agreements, obligations, deadlines and dependencies between parties.
- Often confused with a contract repository or a list of renewal dates.
Capabilities and actions required Filled
- Post-contractual obligations can be traced to their evidence.
- Chains of dependent obligations can be followed across agreements.
Hazards and failure modes required Filled
- Silent loss of surviving obligations at contract expiry.
- Wrong prevalence decisions when conflicts are resolved automatically.
Standards and interfaces required Filled
- OASIS LegalRuleML for representing legal norms and obligations.
- W3C ODRL Information Model for permissions, prohibitions and duties.
- ISO 8601 for dates and periods of obligations.
Context of use required Filled
- Used in contract renewal, termination and supplier exit planning.
- Relevant wherever confidentiality, data protection or warranty duties outlive contracts.
Sources Filled
- 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
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
- United Nations Convention on Contracts for the International Sale of Goods (Vienna, 1980) (CISG) - Carried over from the published world model wm-eco-006-commercial-contract; checked live (HTTP 200) on 2026-10-09.
- UNIDROIT Principles of International Commercial Contracts 2016 - Carried over from the published world model wm-eco-006-commercial-contract; checked live (HTTP 200) on 2026-10-09.
- LegalRuleML Core Specification Version 1.0 (OASIS Standard) - Carried over from the published world model wm-eco-006-commercial-contract; checked live (HTTP 200) on 2026-10-09.
Open questions
- Which obligations survive contract termination?
- Where does a condition depend on someone else's performance?
- Which agreements conflict?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-09/brief.json, ver-cy/world-models/card-supplements/em-lnd-09.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.