Type: Hybrid / Reified Normative Relation
Placement note: Obligation belongs in Division V because it supplies the normative relation presupposed by Commitment, Waiver, and Breach. It is broader than an institutional Commitment. Obligations may arise from a Rule, Role, Judgment, recognized Norm, relationship, moral basis, or another disclosed ground without all sharing one origin or enforcement mechanism.
Working Definition: An obligation is a normative requirement attributable to a bearer under a stated basis and within a stated scope. When its conditions apply, it requires the bearer to perform, refrain from, provide, preserve, or answer for something. A well-formed Obligation identifies the bearer, required content, basis, conditions, and scope.
Function in the Grammar: Obligation connects normative sources to attributable requirements. Rules and Norms can state general expectations. Roles can specify what occupants must do. Commitments and Judgments can create particular requirements. Obligation identifies the resulting relation between a bearer and required content without treating every source, expectation, or institutional preference as already binding.
Reifying the relation preserves provenance and difference. Two Obligations may require identical conduct while arising under different bases. Performing that conduct may satisfy both, but a Waiver, Exception, Amendment, or challenge affecting one basis does not silently eliminate the other. This lets the grammar ask not only whether conduct occurred, but which Obligation it satisfied, under what basis, and whether any coextensive Obligation remains.
Obligation also keeps independent properties independent. Existence, applicability, due conditions, satisfaction, discharge, breach, recognition, recording, and enforceability do not form a mandatory lifecycle. An Obligation may apply before it is due, remain in force after Breach, be satisfied for one interval without being discharged, or be normatively discharged before an institution records that effect.
Formal Grammar Representation
<obligation> ::= Obligation(
id: <obligation-id>,
bearer: Agent(<agent-id>),
content: <normative-content>,
basis: <governing-basis>,
scope: <scope>,
conditions: <conditions>
)
<normative-content> ::= Perform(<action-type>)
| RefrainFrom(<action-type>)
| Provide(<object-or-service>)
| Preserve(<state-or-object>)
| Maintain(<state-condition>)
| AnswerFor(<matter>)
| <other-disclosed-content>
<governing-basis> ::= a disclosed Rule, Role, Commitment, Judgment, Norm,
relationship, moral ground, or other warranted basis
<conditions> ::= applicability, activation, due, duration, completion,
and other conditions relevant to the content
Obligation(o) is well-formed when:
bearer(o) = Agent(a), where a is the identified bearer
content(o) = phi, where phi states what is required or prohibited
basis(o) = g, where g states what warrants the claimed binding
scope(o) = S, where S states the domain and limits of the requirement
conditions(o) = C, where C states when and how the requirement applies
If two independently sufficient bases g1 and g2 warrant the same content:
Obligation(o1, bearer: a, content: phi, basis: g1, scope: S1, conditions: C1)
Obligation(o2, bearer: a, content: phi, basis: g2, scope: S2, conditions: C2)
o1 != o2
Semantic Constraints
The expression Obligation(o, a, phi, g, S, C) is well-formed when its bearer, content, basis, scope, and conditions can be stated. The syntax does not establish that the basis exists, that it applies to the bearer, that it warrants the full content claimed, or that the Obligation is valid, recognized, enforceable, or morally justified. Those questions may require evidence, interpretation, Judgment, or institutional Recognition. A claim that an Obligation exists is not made true merely by using the predicate.
The governing basis is not necessarily an Authority. An institutional Rule or Judgment may carry formal authority, while a relationship, moral ground, or informal Norm may warrant an Obligation without authorizing institutional enforcement. The grammar records the asserted basis without resolving one general theory of why obligations bind.
Beneficiary direction is optional. Some Obligations are owed to an identified person or institution. Others protect a public, a community, an office, or a good without creating one beneficiary who may claim or waive performance. OWED_TO must therefore be stated when warranted rather than inferred from Obligation.
Applicability and due conditions differ. An Obligation may govern a case while performance is not yet due, or require continuing conduct without one deadline. Capacity is not a condition of syntactic well-formedness. Incapacity may affect excuse, culpability, remedy, or a Breach finding without automatically deciding whether the Obligation existed.
Satisfaction is polymorphic. Depending on the content, an Action, recognized Act, omission, maintained condition, authorized third-party performance, or Event may satisfy an Obligation. The variable x in SATISFIES(x, o) does not introduce a new Performance primitive. Its admissible type must be disclosed by the Obligation's content and basis.
Independent bases remain independently contestable. The same x may satisfy several Obligations, but discharge, Waiver, Exception, or invalidation under one basis does not transfer automatically to another. Recognition and recording also remain separate from normative effect unless a governing Rule makes either constitutive in the relevant case.
Formal Pattern
Obligation(o, bearer: Agent(a), content: phi, basis: g, scope: S, conditions: C)
BINDS(Obligation(o), Agent(a), to: phi, under: g, within: S)
ARISES_FROM(Obligation(o), GoverningBasis(g))
OWED_TO(Obligation(o), Beneficiary(B)) # optional
APPLIES_TO(Obligation(o), Case(i), at: t)
DUE_AT(Obligation(o), t)
SATISFIES(x, Obligation(o), extent: q)
DISCHARGES(y, Obligation(o), at: t)
PREVENTS_APPLICABILITY(Exception(e), Obligation(o), in: Case(i))
WAIVES(Waiver(w), Obligation(o), within: Case(i))
SUSPENDS(Act(s), Obligation(o), aspect: z, during: T)
Breach(beta, obligation: Obligation(o), bearer: Agent(a))
ENFORCEABLE_IN(Obligation(o), Forum(f), at: t)
RECOGNIZES(Institution(I), Obligation(o), within: S)
REPRESENTS(Record(r), Obligation(o), within: S)
ENTERS(Act(e), Record(r), Ledger(L))
These relations are composable, not sequential. APPLIES_TO does not imply that performance is presently due. SATISFIES does not imply discharge. Breach does not imply that the Obligation has ended. RECOGNIZES and RECORDS do not create normative effect unless the relevant governing basis makes them constitutive.
Core Relations
| Relation | Notes |
|---|---|
| Agent bears | An Obligation must be attributable to a bearer. Collective or institutional bearers remain subject to the Agent entry's attribution constraints. |
| Rule and Norm may ground | A Rule or prescriptive Norm may warrant Obligations when its scope and applicability conditions reach a particular bearer and case. Its existence alone does not individualize every possible Obligation. |
| Role specifies | A Role may specify Obligations before it is occupied. Occupation is what ordinarily binds an identified Agent to the role-based requirement for the relevant interval. |
| Commitment specializes | A Commitment is a particular, durable Obligation created through a recognized Act and tied to its parties and conditions. Obligation supplies the broader normative genus. |
| Judgment may ground | An authorized Judgment may find, specify, create, modify, or discharge an Obligation when its governing basis gives it that effect. |
| Claim asserts | An Agent may claim that an Obligation exists, applies, or has been satisfied. The Claim makes the proposition contestable but does not itself establish binding force. |
| Action and Act may satisfy | Conduct may satisfy an Obligation when it matches the content and conditions. Some Obligations are instead satisfied by omission, maintained conditions, or other admissible occurrences. |
| Exception limits applicability | An Exception may prevent a rule-grounded Obligation from applying in a particular case. It does not necessarily discharge other Obligations with the same content. |
| Waiver may release | A Waiver releases an otherwise applicable Obligation only when performed by a party with standing to release that Obligation within the stated scope. |
| Breach may be found | Breach concerns failure relative to a specific applicable Obligation under its conditions. Non-performance alone does not establish Breach. |
| Recognition confers institutional treatment | Recognition may give an Obligation institutional standing or acknowledge its satisfaction, discharge, or Breach. Recognition is distinct from the underlying normative claim. |
| Record and Ledger preserve | A Record may represent an Obligation or one of its changing properties, and a governed Act may enter that Record into a Ledger. Neither the artifact nor its entry creates normative effect unless the governing basis makes recording constitutive. Absence from a Ledger weakens institutional traceability but does not prove that no moral, social, or unrecorded Obligation exists. |
Typical Questions
- Who is claimed to bear this Obligation?
- What conduct, omission, condition, provision, preservation, or answer does it require?
- What basis warrants the claimed binding?
- Does that basis apply to this bearer, case, scope, and time?
- Is the Obligation applicable now, and is performance presently due?
- What would count as full or partial satisfaction?
- Is the Obligation owed to an identified beneficiary, and who has standing to waive it?
- Does another Obligation require the same content under a different basis?
- Has the Obligation been satisfied, discharged, waived, excepted, suspended, breached, recognized, recorded, or made enforceable, and which of those claims remain contested?
Examples
| Domain | Obligation | Basis | What must remain distinct |
|---|---|---|---|
| Ordinary life | A parent must provide care to a child | Relationship, moral ground, and sometimes law | A family agreement may add a Commitment without exhausting the underlying care Obligation |
| Law | A witness must appear on the stated date | Valid subpoena and applicable procedural rules | The Obligation applies to this witness and date, not to everyone who knows about the case |
| Science | A researcher must disclose a financial conflict | Professional Norm, journal Rule, or contractual term | One disclosure may satisfy several independently grounded Obligations |
| Publishing | A peer reviewer must preserve manuscript confidentiality | Occupied reviewer Role and accepted review terms | Leaving the Role may end future access without erasing responsibility for prior disclosure |
| Markets | A supplier must deliver specified goods | Contractual Commitment | A Waiver of one delivery deadline does not amend every future delivery term |
| Digital systems | A human author must review content before publication | Editorial Role and publication Rule | The Rule does not make a model output human-reviewed or make the model the bearer of the human Obligation |
| Community life | A member should answer for harm they caused | Relational and community Norms | The Obligation may be real without one beneficiary possessing authority to waive every consequence |
Distinctions
Obligation ≠ Commitment. A Commitment is a specific, durable Obligation created through a recognized Act and tied to particular parties and conditions. A caregiver may be obligated by relationship or law without having made a Commitment. Conversely, a Commitment may add a distinct Obligation whose content overlaps an existing duty.
Obligation ≠ Rule. A Rule is a general specification for a class of cases. An Obligation is an attributable requirement under a basis. A Rule requiring licensed operators to file a report does not bind every person who reads it; an Obligation arises for an Agent only when the Rule's bearer, scope, and conditions apply.
Obligation ≠ Norm. A Norm is a shared expectation that guides evaluation within a community. Some prescriptive Norms may ground Obligations, but not every expectation binds every member in every case. A courtesy Norm may guide conduct without creating a determinate Obligation owed by one Agent.
Obligation ≠ Requirement. A requirement may state a condition for validity, eligibility, or classification without binding an Agent to bring that condition about. Identification may be required for admission while no applicant is obligated to apply. An Obligation requires an attributable bearer.
Obligation ≠ Claim. A Claim asserts that something is owed, required, satisfied, or breached. Obligation is the normative relation asserted. Recording the Claim preserves who said what; it does not establish that the asserted Obligation exists or applies.
Obligation ≠ Enforceability. An Obligation may lack an authorized Forum or practical mechanism of enforcement. Conversely, an institution may attempt to enforce a purported Obligation whose basis or applicability is invalid. Enforcement capacity and normative binding must be assessed separately.
Obligation ≠ Permission or prohibition. Permission identifies what an Agent may do; it does not require the permitted conduct. A prohibition may ground a negative Obligation to refrain from an act, but the Rule and the attributable Obligation remain distinct.
Common Failure Modes
| Mode | Description |
|---|---|
| Fabricated basis | An Obligation is asserted under a Rule, Role, Commitment, Judgment, Norm, or relationship that does not exist or does not carry the claimed force. Where to look: the cited basis and the provenance of the act, assignment, or rule said to establish it. |
| Ambiguous bearer | The required content is stated but no accountable Agent is identified, or the record names a department, system, or process without resolving who bears the requirement. Where to look: passive formulations such as "review must occur" with no role or bearer attached. |
| Content overreach | The claimed content exceeds what the disclosed basis warrants. Where to look: narrow confidentiality, care, reporting, or compliance provisions used to demand unrelated conduct. |
| Rule-to-obligation collapse | A general Rule is treated as immediately binding every Agent without checking bearer, scope, conditions, effective time, or valid Exception. Where to look: enforcement that cites rule text but contains no applicability analysis. |
| Basis conflation | Coextensive Obligations are treated as one because they require the same conduct. Waiver or invalidation of one is then assumed to eliminate the others. Where to look: cases where contractual, role-based, legal, and relational grounds overlap. |
| Property collapse | Applicability, due status, satisfaction, discharge, Breach, recognition, recording, and enforceability are treated as one status. Where to look: systems that mark an Obligation simply "closed" without saying what occurred or what effect followed. |
| Non-enforcement as release | Delay or inaction is treated as proof that an Obligation was waived, suspended, or extinguished without an attributable act or applicable rule producing that effect. Where to look: old Obligations absent from recent enforcement activity but lacking a Waiver, Exception, Amendment, expiry condition, or discharge record. |
Minimum Viable Test Case
o1 = Obligation(
bearer: human_author,
content: Review(entry_x),
basis: editorial_role,
scope: publication_of(entry_x),
conditions: before status becomes published
)
o2 = Obligation(
bearer: human_author,
content: Review(entry_x),
basis: publication_rule,
scope: publication_of(entry_x),
conditions: before status becomes published
)
a1 = Action(human_author reviews entry_x)
SATISFIES(a1, o1, extent: full)
SATISFIES(a1, o2, extent: full)
Result:
o1 != o2 because their bases differ.
One Action may satisfy both Obligations.
Satisfaction does not by itself establish that either Obligation has been
institutionally discharged or recorded.
Failure case:
A minor-edit Exception under the publication_rule may
PREVENTS_APPLICABILITY(Exception(e1), o2, in: this_publication).
It does not automatically remove o1 if the editorial Role independently
requires review. The remaining basis must be assessed separately.
Cross-References
Required
- Agent: the bearer to whom required content is attributed
- Rule: a general specification that may ground an Obligation when applicable
- Norm: a shared expectation that may warrant an Obligation without formal enactment
- Role: an institutional position that may specify Obligations for its occupants
- Commitment: a particular, act-generated, durable Obligation
Consequential
- Action: conduct that may satisfy an Obligation
- Act: recognized conduct that may satisfy, discharge, waive, suspend, or otherwise affect an institutional Obligation
- Judgment: may find or alter an Obligation where authorized
- Breach: a finding of failure relative to a specific applicable Obligation
- Waiver: authorized release of an otherwise applicable Obligation
- Exception: may prevent an Obligation from applying in a specific case
- Amendment: may change a basis prospectively without silently resolving prior Obligations
Evidential
- Claim: makes an Obligation assertion attributable and contestable
- Recognition: may confer institutional treatment without proving independent validity
- Status: may qualify distinct properties without turning them into one lifecycle
- Record: may represent an Obligation or one of its properties without constituting it
- Ledger: preserves institutional Obligations and their traceable changes