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.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Agreement and versions The contract, its parties and its signed text over time.
Contract and amendments
The signed agreement and each amendment as a separate version.
Contract
The agreement with parties identified as of the signing date.
- Who were the parties and their legal identities on the signing date?
- Which signed text is the original, and where is it kept?
Amendment
A change that adds a version without overwriting the signed text.
- Which amendments apply, and from which dates?
- Does a change of party require a new contract or an assignment?
Obligations Who owes what to whom, and how performance is shown.
Obligation and fulfilment
Obligations with debtor, subject and criterion, and evidence of performance.
Obligation
A duty with a debtor, a subject and a criterion of performance.
- Who is the debtor and what exactly is owed?
- By which criterion is performance judged?
Fulfilment evidence
Evidence of full or partial performance and any dispute.
- What evidence shows full or partial performance?
- Is performance disputed, and by whom?
Service levels Contractual service levels kept apart from internal objectives.
SLA terms
Agreed service levels, measurement and remedies.
Service level agreement
Contractual levels with measurement method and remedies.
- Which service levels are contractually agreed, and how are they measured?
- Is a target an internal objective or a contractual commitment?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseLEG
- Industry
- Cross-industry
- Tags
- EM-LEG-01W1subjectContractContractAmendmentObligationFulfilmentEvidenceServiceLevelAgreement
What it is Filled
Agreement of the parties, versions, terms, obligations, confirmation of performance and SLA/OLA. Operational SLO and metrics are moved to their own models.
Why it exists Filled
Agreement of the parties, versions, terms, obligations, confirmation of performance and SLA/OLA. Operational SLO and metrics are moved to their own models.
Distinguishing features Filled
- A signed contract text is never overwritten; amendments are added as dated versions.
- Each obligation names a debtor, a subject and how performance is judged.
- A contractual service level is a commitment to a party; an internal objective is not.
- Distinct from the external norms contour, which records law rather than agreements between parties.
What robots and AI may and may not do Filled
Must not
- Declare an internal service objective a contractual guarantee without an agreement.
- Edit the signed text of a contract instead of recording an amendment.
- Mark an obligation as fulfilled without evidence.
- Sign, accept or terminate a contract on behalf of a party.
Only with a human decision
- Signing, amending or terminating a contract.
- Deciding a dispute over performance or service levels.
- Claiming penalties or service credits.
May
- Extract obligations, dates and service levels from a signed contract for review.
- Track deadlines and report missing evidence of performance.
- Compare an amendment with the text it changes.
Moral aspects Filled
- Misread obligations can cause financial harm to either party.
- Weaker parties depend on accurate records of what was promised.
- Contracts often contain personal and commercially confidential data.
Who is affected
- Contracting parties
- Staff who perform the obligations
- Customers relying on service levels
Owners Filled
Steward
The legal function or contract owner who answers for legal records and their interpretation.
Master systems
- Contract lifecycle management system
- Signed document repository
- Legal sources register
Links to other meta-models Filled
neighbor
- EM-FIN-03
- EM-KNW-01
- EM-KNW-02
- EM-ORG-02
- EM-PEO-01
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 the contract number with its parties and signing date; amendments by sequence number and effective date.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- Marked by parties, a signing date, signatures and terms of performance.
- Often confused with an order, an invoice or an internal service objective.
Capabilities and actions required Filled
- Contract history can be reconstructed as of any date.
- Obligations can be tracked to evidence of performance.
Hazards and failure modes required Filled
- Lost original text after edits in place.
- Party identity changes not reflected in obligations.
- Service levels measured differently from the agreed method.
Standards and interfaces required Filled
- OASIS Universal Business Language (UBL) for contract-related business documents.
- W3C ODRL Information Model for permissions, prohibitions and duties.
- Financial Industry Business Ontology (FIBO) by the EDM Council for agreements and parties.
- ISO/IEC 19086-1 for cloud service level agreement concepts.
Context of use required Filled
- Used for customer, supplier, licence and service contracts.
- Legal effect depends on the governing law, which must be checked against primary sources.
Sources Filled
- OASIS UBL: business documents for agreements and orders
- FIBO (EDM Council, OMG): financial agreements, parties and obligations
- ODRL: permission, prohibition, duty and constraint
- Primary legal sources of selected jurisdictions; subject-matter verification of applicability is mandatory
- OASIS Universal Business Language (UBL) 2.3 - Checked live (HTTP 200) on 2026-10-07.
- W3C ODRL Information Model 2.2 - Checked live (HTTP 200) on 2026-10-07.
- OASIS Universal Business Language Technical Committee - Checked live (HTTP 200) on 2026-10-07.
Open 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?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-leg-01/brief.json, ver-cy/world-models/card-supplements/em-leg-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.