EM-LEG-01 · Subject model · W1
Contract, obligation and service level agreement
Agreement of the parties, versions, terms, obligations, confirmation of performance and SLA/OLA. Operational SLO and metrics are moved to their own models.
Partially published; research continues
Claude: complete-frozen-study-and-audit; Grok: complete-browser-study.
Published results
Research note, in Russian: Canonical promotion remains held by the limits published with the profile.
Subject boundary and candidate types
- Contract
- ContractAmendment
- Obligation
- FulfilmentEvidence
- ServiceLevelAgreement
Deep research questions
- When does a change require a new party or a new contract?
- How does a contractual SLA differ from an internal SLO?
- How to record a dispute over performance?
Verifiable invariants
- A party is identified as of the signing date
- An amendment does not overwrite the signed text
- An obligation has a debtor, a subject and a criterion of performance
End-to-end acceptance scenario
A contract with two amendments, partial performance and a disputed SLA preserves its legal and operational history.
Negative case
An internal SLO is declared a contractual guarantee without an agreement.
Approaches to compare
- OASIS UBL/FIBO: agreements, parties and obligations
- ODRL: permission, prohibition, duty and constraint
- Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
Candidates in the live catalogue
- WM-ECO-006 · Commercial Contract · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-XCT-029 · Obligation / Commitment · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
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.