Coming soon · Contract draft

Contracts, vSOW & Amendments

Planned

A commercial engagement graph for contracts, virtual SOWs, amendments, terms, signatures, and portal decisions.

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

Commercial engagement, contract, vSOW, amendment, and signature services

Contract posture

P1 · Documentation first · implementation follows approval

Contract metadata

Draft version

0.2 review draft

Review owner

Commercial/Knowledge + Developer Platform

Last reviewed

July 14, 2026

Target wave

Wave 4 · Commercial lifecycle

Contract dependencies

• Canonical identity and provider mapping policy
• Field-level visibility rules
• Transactional event outbox

What this unlocks

Build contract workflows

Read a stable domain model for contracts, vsow & amendments without depending on GUI routes or database shapes.

Draft governed amendments

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

Coordinate signatures

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

Lifecycle and invariants

Contracts, vSOW & Amendments exposes a bounded lifecycle with explicit commands and named authority at every transition.

draftpublishedsignature_pendingsignedamendedsuperseded

From	To	Command	Authority
draft	published	Publish package	Commercial contract and signature services
published	signature_pending	Request signature	Commercial contract and signature services
signature_pending	signed	Complete signature	Commercial contract and signature services
signed	amended	Approve amendment	Commercial contract and signature services

Lifecycle invariants

• Only named humans sign or approve amendments.
• Sensitive terms remain separately scoped.

Authority boundaries

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

DigitalStack owns

• Contract/package/version identity
• Amendment and supersession lifecycle
• Signature-request and completion evidence

Explicitly not building

• Agents signing for people
• Sensitive terms under broad project scopes
• Provider signature state overriding contract state silently

Surface decisions

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

add

Packages, versions, amendments, signature requests, decisions, and supersession history

A contract API needs versioned legal/commercial lifecycle, not document CRUD alone.

keep

Human signature and amendment approval boundaries

Connected signature providers transport decisions but do not own them.

remove

Agent signatures and broad project scopes for sensitive terms

These exceed both legal authority and least privilege.

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 contracts, vsow & amendments resources, commands, idempotency, and operation status.

Reads + explicit commands

GraphQL

Planned

Composable CommercialContract 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 commercial contract lifecycle facts with minimal payloads.

Past-tense durable facts only

Connected Apps

Planned

DocuSign / Adobe Sign / CRM / ERP 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 /commercial/contracts	commercialContract(id: ID!): CommercialContract	get_commercial_contracts	—	Commercial engagement, contract, vSOW, amendment, and signature services
Primary command	POST /commercial/contracts	draftCommercialContractChange(input: DraftCommercialContractChangeInput!): CommercialContractChangeProposal!	draft_commercial_contracts_change	commercial_contract.created	Commercial engagement, contract, vSOW, amendment, and signature services

Proposed scopes

Proposed scopes are not grantable yet.

commercial-contracts:readplanned scope

Read governed contracts, vsow & amendments resources.

commercial-contracts:writeplanned scope

Create and edit bounded contracts, vsow & amendments fields.

commercial-contracts:operateplanned scope

Run explicit contracts, vsow & amendments 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 Commercial engagement, contract, vSOW, amendment, and signature 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/commercial/contracts

List contracts, vsow & amendments

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

commercial-contracts:read

POST/api/v1/commercial/contractsconfirmation

Create CommercialContract

Create one canonical resource with idempotency and actor attribution.

commercial-contracts:write

GET/api/v1/commercial/contracts/{id}

Retrieve CommercialContract

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

commercial-contracts:read

PATCH/api/v1/commercial/contracts/{id}confirmation

Update CommercialContract

Update bounded editable fields using optimistic versioning.

commercial-contracts:write

POST/api/v1/commercial/contracts/{id}/publishconfirmation

publish CommercialContract

Run one explicit domain command after validation and authorization.

commercial-contracts:operate

publish a CommercialContract

Planned request

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

Planned response

{
  "data": {
    "id": "commercial_contract_123",
    "status": "published",
    "version": 3,
    "operation_id": "op_01k4..."
  }
}

GraphQL

Proposed graph

Planned

Types

CommercialContract

CommercialContractConnection

CommercialContractChangeProposal

Operation

Queries

commercialContract(id: ID!): CommercialContract

commercialContractList(filter: CommercialContractFilter, pagination: PaginationInput): CommercialContractConnection!

Mutations

draftCommercialContractChange(input: DraftCommercialContractChangeInput!): CommercialContractChangeProposal!

Planned GraphQL query

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

MCP / Agent API

Proposed tools

Planned

Get Contracts, vSOW & Amendments

get_commercial_contracts

Planned

Read the authorized contracts, vsow & amendments state, provenance, and allowed actions.

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

Draft Contracts, vSOW & Amendments change

draft_commercial_contracts_change

Planned

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

Scope: commercial-contracts: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 Contracts, vSOW & Amendments action

request_commercial_contracts_action

Planned

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

Scope: commercial-contracts: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 contracts, vsow & amendments change and help me apply it.

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

Never infer authority from access to the MCP client.

Webhooks

Proposed event catalog

Planned

Event types

commercial_contract.createdplanned event

A canonical CommercialContract was created.

payload: commercial_contract_id, status, created_at

commercial_contract.updatedplanned event

Governed CommercialContract fields changed.

payload: commercial_contract_id, changed_fields, version, occurred_at

commercial_contract.publishedplanned event

The publish command completed.

payload: commercial_contract_id, prior_status, status, occurred_at

Planned event example

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

Connected Apps

Proposed connection roles

Planned

Claude / ChatGPT / IDE clients

Consumer application

Read, explain, and submit bounded contracts, vsow & amendments proposals through MCP.

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

DocuSign / Adobe Sign / CRM / ERP

Synchronization provider

Exchange signature and commercial lifecycle facts.

Authority: Signing authority remains with the named human; provider state is reconciled with provenance.

Open contract decisions

Resolve before implementation approval

• Should signature-complete events include signer identity or only an authorized reference?

Proof obligations

Must remain true	Failure indicator
Commercial engagement, contract, vSOW, amendment, and signature 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.