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.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
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 Derived, awaiting review
- 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
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: An internal SLO is declared a contractual guarantee without an agreement.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Юридическая функция / владелец договора
Master systems
- CLM
- подписанные документы
- нормативные источники
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 Incomplete
Identity and identifiers required Derived, awaiting review
- Contract
- ContractAmendment
- Obligation
- FulfilmentEvidence
- ServiceLevelAgreement
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- 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
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
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.