feat: add obligation definitions to protocol#89
Conversation
Implements Issue accordproject#57 by adding standard Obligation types (Payment, Ownership, Escrow, Access) to protocol.cto and regenerating OpenAPI spec and docs. Signed-off-by: Aadityavardhan Singh <singhrashmi018@gmail.com>
|
This PR is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
Be gone, bot.
…On Sat, 14 Feb 2026, 07:50 github-actions[bot], ***@***.***> wrote:
*github-actions[bot]* left a comment (accordproject/apap#89)
<#89 (comment)>
This PR is stale because it has been open 15 days with no activity. Remove
stale label or comment or this will be closed in 10 days.
—
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYXRV6YLBNVUHNPLZHAWYUL4L2BAXAVCNFSM6AAAAACTK47EJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMBQGQ3TIMZTG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
dselman
left a comment
dselman
left a comment
There was a problem hiding this comment.
This requires more discussion with the legal folks in the WG and taking into account the existing Obligations defined in https://models.accordproject.org/cicero/runtime@0.2.0.html
Before we move into implementation lets create a separate CTO file with the proposed obligations and present/validate with the WG.
|
This PR is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
I have started a document as a basis for discussion at https://docs.google.com/document/d/15vtcLDK4ymJ17q4w4Rd3N1hCJdSZ6mlH/edit?usp=share_link&ouid=112259737190306437667&rtpof=true&sd=true |
|
This PR is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
Be gone, bot.
…On Fri, 17 Apr 2026, 07:52 github-actions[bot], ***@***.***> wrote:
*github-actions[bot]* left a comment (accordproject/apap#89)
<#89 (comment)>
This PR is stale because it has been open 15 days with no activity. Remove
stale label or comment or this will be closed in 10 days.
—
Reply to this email directly, view it on GitHub
<#89 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AYXRV64BATPTMR4LEK74ODD4WGIOPAVCNFSM6AAAAACTK47EJGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DENRUHAZDQNRUGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
This PR is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 10 days. |
|
This PR is stale because it has been open with no activity. Remove the stale label or comment to keep it active. Only items with maintainer engagement are auto-closed. |
4 participants
Description
Addresses Issue #57 "Create Obligation Definitions for triggering responses".
This PR extends the
protocol.ctomodel to include standardized definitions for legal obligations. This standardizes the output of contract triggers, allowing external systems (like Banking APIs or Distributed Ledgers) to programmatically understand required actions (payments, transfers, etc.).Changes
model/protocol.cto: AddedObligationStatusenum and concepts:BaseObligationPaymentObligationOwnershipTransferObligationEscrowReleaseObligationAccessControlObligationTriggerResponse: Now includes an optionalobligationsarray to emit these events.npm run buildto updateopenapi.jsonandclient/typescript/apap.ts.Verification
npm run buildsuccessfully.openapi.jsoncontains the new schema definitions (e.g.,PaymentObligation).