Contract Obligation Registry
Contractual obligations are commitments the company must meet. EntiHub stores them as entities so ops does not rely on PDF folders alone.
Why this is needed
- SLA breaches surprise teams that never saw the contractual threshold.
- Customer Success and IT need one living list.
- AI can ask which obligations are at risk this month.
Proposed entities in EntiHub
Governance settings
| Setting | Recommended value | Why |
|---|---|---|
approvalRequired |
true |
Status and threshold changes need owners. |
historyEnabled |
true |
History of obligation changes for claim disputes. |
allowSameAuthorApproval |
false |
Maker/checker separation for sensitive changes. |
deletedRetentionDays |
90 (or higher) |
Soft-delete retention for auditability. |
Entity definition (YAML sketch)
name: contract_obligation
displayName: Contract obligation
domain: Legal Ops
description: Contract obligation
version: "1.0.0"
approvalRequired: true
historyEnabled: true
deletedRetentionDays: 90
displayRefColumn: obligation_code
uniqueConstraints:
- name: uq_contract_obligation_obligation_code
columns: [obligation_code]
columns:
- name: obligation_code
dataType: string
nullable: false
maxLength: 64
- name: customer_code
dataType: string
nullable: false
maxLength: 64
- name: obligation_type
dataType: string
nullable: false
maxLength: 32
- name: threshold
dataType: string
nullable: true
maxLength: 64
- name: cadence
dataType: string
nullable: false
maxLength: 32
- name: owner_team
dataType: string
nullable: false
maxLength: 128
- name: status
dataType: string
nullable: false
maxLength: 16
YAML sketches
Sketches highlight the important fields and governance flags. Trim or extend columns to match your domain. See Setup Entity for the full YAML reference.
Sample data
| obligation_code | customer_code | obligation_type | threshold | cadence | owner_team | status |
|---|---|---|---|---|---|---|
| CO-ACME-SLA | ACME | SLA | 99.5% | monthly | IT | at_risk |
| CO-ACME-RPT | ACME | Report | QBR deck | quarterly | Customer Success | on_track |
Benefits for the company
- Living obligation lists instead of static PDFs.
- Owners and cadence drive operational follow-up.
- AI risk briefs grounded in structured commitments.