Coming soon · Contract draft

Commitments & Acceptance

Planned

A commitment graph beneath projects and contracts with explicit acceptance authority and durable evidence.

Reviewable specification — not callable

Documentation-first contract draft. The proposed additions on this page are not callable or available yet. Paths, payloads, scopes, names, and examples are intentionally concrete so customers can review the intended contract before and during implementation.

Canonical owner

Commitment and acceptance domain services

Contract posture

P1 · Documentation first · implementation follows approval

Contract metadata

Draft version

0.2 review draft

Review owner

Delivery/Execute + Developer Platform

Last reviewed

July 14, 2026

Target wave

Wave 2 · Project and Execute core

Contract dependencies

• Canonical domain service adapter
• Optimistic concurrency and idempotency policy
• Transactional event outbox

What this unlocks

Track delivery promises

Read a stable domain model for commitments & acceptance without depending on GUI routes or database shapes.

Collect acceptance evidence

Create a reviewable proposal and apply only the bounded commands the canonical owner permits.

React to commitment breach

React to durable lifecycle facts and connect external systems with explicit direction and provenance.

Lifecycle and invariants

Commitments & Acceptance exposes a bounded lifecycle with explicit commands and named authority at every transition.

draftcommittedat_riskfulfilledacceptedbreached

From	To	Command	Authority
draft	committed	Commit outcome	Commitment and acceptance services
committed	fulfilled	Mark fulfilled	Commitment and acceptance services
fulfilled	accepted	Accept commitment	Commitment and acceptance services
committed	breached	Record breach	Commitment and acceptance services

Lifecycle invariants

• Acceptance names an authorized human.
• Contract terms remain outside commitment write scopes.

Authority boundaries

The interfaces expose canonical capabilities; they do not become a second owner of domain rules or state.

DigitalStack owns

• Commitment identity and lifecycle
• Acceptance criteria and evidence linkage
• Authorized acceptance decisions

Explicitly not building

• Agents accepting on a customer’s behalf
• Contract text mutation through commitment scopes
• Acceptance inferred from activity alone

Surface decisions

Deliberate additions, retained boundaries, and removals from the proposed external contract.

add

Commitment detail, evidence, acceptance request, decision, and breach history

The API must represent both delivery facts and the authority to accept them.

keep

Human acceptance as a distinct command

Evidence may support acceptance but cannot make the decision.

remove

Agent acceptance and contract-text mutation through commitment scopes

Neither belongs to an execution-assistance interface.

add

Project/engagement-scoped filtering on every read and command

A workspace API key is not a licence to read every project. Access composes workspace membership with per-project visibility, so integrators receive exactly the engagements they are entitled to.

Interface plan

REST API

Planned

Versioned commitments & acceptance resources, commands, idempotency, and operation status.

Reads + explicit commands

GraphQL

Planned

Composable Commitment reads with mutations delegated to the same canonical domain service.

Composable reads + bounded delegated mutations

MCP / Agent API

Planned

Bounded read, draft, and human-request tools with evidence and audit attribution.

Read + proposal/confirmed commands only

Webhooks

Planned

Past-tense commitment lifecycle facts with minimal payloads.

Past-tense durable facts only

Connected Apps

Planned

Customer portal / DocuSign plus consumer clients, with declared direction and authority.

Declared direction and field authority required

Cross-interface parity

Each surface delegates to the named canonical owner; a blank surface is an intentional denial of authority, not missing documentation.

Capability	REST	GraphQL	MCP	Webhook	Canonical owner
Primary read	GET /commitments	commitment(id: ID!): Commitment	get_commitments_acceptance	—	Commitment and acceptance domain services
Primary command	POST /commitments	draftCommitmentChange(input: DraftCommitmentChangeInput!): CommitmentChangeProposal!	draft_commitments_acceptance_change	commitment.created	Commitment and acceptance domain services

Proposed scopes

Proposed scopes are not grantable yet.

commitments:readplanned scope

Read governed commitments & acceptance resources.

commitments:writeplanned scope

Create and edit bounded commitments & acceptance fields.

commitments:operateplanned scope

Run explicit commitments & acceptance lifecycle commands.

Behavioral contract

Cross-cutting rules every implementation and interface must satisfy.

Project / engagement-scoped access

A project and its engagement are the same object here. Resources are scoped to the projects the principal can access: workspace membership plus project-level visibility — owners and admins see every project, other principals see only the projects they created, were role-assigned, or were added to as members. List endpoints return only visible projects’ resources; detail endpoints enforce that visibility before returning or changing anything.

Canonical delegation

Every interface delegates to Commitment and acceptance domain services; no resolver, gateway, worker, or connector reimplements domain rules.

Least-privilege principals

Scopes are evaluated with tenant, role, field-visibility, and principal-type constraints before data is read or changed.

Safe writes

Mutations use explicit confirmation where required, optimistic concurrency, idempotency, and durable actor attribution.

Transactional facts

Webhook facts are emitted from the canonical commit path, versioned, minimal, and safe to redeliver.

Declared provider authority

Every Connected App declares direction, field authority, provenance, and conflict behavior before activation.

REST API

Proposed endpoints

Planned

GET/api/v1/commitments

List commitments & acceptance

Return an authorized, paginated collection with stable filters and provenance.

commitments:read

POST/api/v1/commitmentsconfirmation

Create Commitment

Create one canonical resource with idempotency and actor attribution.

commitments:write

GET/api/v1/commitments/{id}

Retrieve Commitment

Return canonical detail, lifecycle state, permissions, and allowed actions.

commitments:read

PATCH/api/v1/commitments/{id}confirmation

Update Commitment

Update bounded editable fields using optimistic versioning.

commitments:write

POST/api/v1/commitments/{id}/acceptconfirmation

accept Commitment

Run one explicit domain command after validation and authorization.

commitments:operate

accept a Commitment

Planned request

curl --request POST \
+  --url https://www.digitalstack360.com/api/v1/commitments/commitment_123/accept \
+  --header "Authorization: Bearer $DSTACK_API_KEY" \
+  --header "Content-Type: application/json" \
+  --header "Idempotency-Key: commitments-acceptance-accept-v2" \
+  --data '{
    "expected_version": 2,
    "reason": "Confirmed through the reviewed integration workflow"
  }'

Planned response

{
  "data": {
    "id": "commitment_123",
    "status": "accepted",
    "version": 3,
    "operation_id": "op_01k4..."
  }
}

GraphQL

Proposed graph

Planned

Types

Commitment

CommitmentConnection

CommitmentChangeProposal

Operation

Queries

commitment(id: ID!): Commitment

commitmentList(filter: CommitmentFilter, pagination: PaginationInput): CommitmentConnection!

Mutations

draftCommitmentChange(input: DraftCommitmentChangeInput!): CommitmentChangeProposal!

Planned GraphQL query

query CommitmentDetail($id: ID!) {
  commitment(id: $id) {
    id
    status
    version
    updatedAt
    allowedActions { id label requiresConfirmation }
    source { kind externalId }
  }
}

MCP / Agent API

Proposed tools

Planned

Get Commitments & Acceptance

get_commitments_acceptance

Planned

Read the authorized commitments & acceptance state, provenance, and allowed actions.

Scope: commitments:read
Input: Resource id or a bounded filter.
Output: Canonical detail with source provenance and allowed actions.
Write boundary: Read only.

Draft Commitments & Acceptance change

draft_commitments_acceptance_change

Planned

Build a reviewable proposal from explicit user intent and DigitalStack evidence.

Scope: commitments:write
Input: Target, requested outcome, expected version, and optional evidence references.
Output: A persisted proposal, validation results, and conflicts.
Write boundary: Creates a proposal; it does not mutate canonical state.

Request Commitments & Acceptance action

request_commitments_acceptance_action

Planned

Prepare an authorized human action request without executing the high-risk command.

Scope: commitments:operate
Input: Proposal id, expected version, named decision maker, and reason.
Output: A pending human-action request and audit reference.
Write boundary: The agent cannot execute the final command.

Planned agent workflow

User: Review the proposed commitments & acceptance change and help me apply it.

1. Call get_commitments_acceptance to inspect current state, provenance, and allowed actions.
2. Call draft_commitments_acceptance_change to create a proposal without changing canonical state.
3. Show validation results, conflicts, and the exact command to the user.
4. Call request_commitments_acceptance_action so an authorized human can decide.

Never infer authority from access to the MCP client.

Webhooks

Proposed event catalog

Planned

Event types

commitment.createdplanned event

A canonical Commitment was created.

payload: commitment_id, status, created_at

commitment.updatedplanned event

Governed Commitment fields changed.

payload: commitment_id, changed_fields, version, occurred_at

commitment.acceptedplanned event

The accept command completed.

payload: commitment_id, prior_status, status, occurred_at

Planned event example

{
  "event_id": "evt_01k4...",
  "type": "commitment.accepted",
  "event_version": 1,
  "occurred_at": "2026-07-16T14:22:04Z",
  "workspace_id": "ws_abc123",
  "resource": {
    "type": "commitment",
    "id": "commitment_123"
  },
  "actor": {
    "id": "user_123"
  },
  "payload": {
    "commitment_id": "commitment_123",
    "prior_status": "draft",
    "status": "accepted"
  },
  "source": null
}

Connected Apps

Proposed connection roles

Planned

Claude / ChatGPT / IDE clients

Consumer application

Read, explain, and submit bounded commitments & acceptance proposals through MCP.

Authority: Client access never implies domain approval or unrestricted mutation authority.

Customer portal / DocuSign

Action sink

Present acceptance requests and return named decisions.

Authority: Only an authorized participant can accept; delivery evidence remains separate.

Open contract decisions

Resolve before implementation approval

• Can acceptance be partial, and if so does it create a new commitment version?

Proof obligations

Must remain true	Failure indicator
Commitment and acceptance domain services remains the singular canonical owner.	An interface or connector persists a second authoritative lifecycle state.
Draft and apply remain separate actions.	An agent or integration silently converts inferred intent into a canonical mutation.
Every write is attributable, versioned, and idempotent.	A retry duplicates work or stale state overwrites a newer human decision.
Connected App direction and field authority are explicit.	Provider data silently becomes canonical or conflicts are resolved without policy.