95. Continuity, compatibility, and knowledge

Permissions describe available actions; obligations constrain continuations. The debt created by an urgency exchange is not satisfied merely because the creditor remains authorized to ask for service. It requires a particular future event. A finite obligation record can be written as \[o=(\mathsf{id},i,j,\varphi,d,\mathsf{authority},\mathsf{status}),\] where \(i\) and \(j\) are the debtor and beneficiary offices, \(\varphi\) specifies a fulfillment event, and \(d\) is a deadline under an agreed clock. Status distinguishes pending, fulfilled, breached, and validly discharged obligations. Cancellation must itself satisfy the declared authorization rule; deleting a record is not fulfillment.