Coming soon · Contract draft

Resource Planning

Planned

A resource-planning contract for people, roles, availability, project demand, allocation proposals, confirmed assignments, and capacity-impact reporting.

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

Resource planning, capacity, staffing, role, and allocation services

Contract posture

P1 · Documentation first · implementation follows approval

Contract metadata

Draft version

0.2 review draft

Review owner

Work/Finance + Developer Platform

Last reviewed

July 14, 2026

Target wave

Wave 2 · People and capacity planning

Contract dependencies

• Financial/privacy scope matrix
• Generic Operation resource
• Transactional audit and event contracts

What this unlocks

Compare capacity and demand

Read a stable domain model for resource planning without depending on GUI routes or database shapes.

Draft allocation proposals

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

Confirm resource plans safely

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

Lifecycle and invariants

Resource Planning exposes a bounded lifecycle with explicit commands and named authority at every transition.

draftreviewapprovedpublishedsuperseded

From	To	Command	Authority
draft	review	Review Resource Planning	Resource planning, capacity, staffing, role, and allocation services
review	approved	Approve Resource Planning	Resource planning, capacity, staffing, role, and allocation services
approved	published	Publish Resource Planning	Resource planning, capacity, staffing, role, and allocation services
published	superseded	Supersede Resource Planning	Resource planning, capacity, staffing, role, and allocation services

Lifecycle invariants

• Recommendations do not become assignments automatically.
• Capacity, financial visibility, and allocation authority remain separately scoped.

Authority boundaries

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

DigitalStack owns

• Capacity and demand model
• Allocation proposal lifecycle
• Confirmed assignment and conflict history

Explicitly not building

• Recommendations becoming assignments automatically
• External planners owning DigitalStack allocation truth
• Rate or margin access through broad planning scopes

Surface decisions

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

add

Resource Planning REST, GraphQL, MCP, webhook, and connected-app surfaces

The capability should return to the live Capabilities section only when every advertised interface has a backed runtime contract.

keep

Resource Planning as documentation-first until runtime parity exists

Partial runtime slices should not appear as a fully available customer capability.

remove

Claims that Resource Planning is available before REST, GraphQL, MCP, and webhooks are implemented

The developer docs must not make customers infer support that does not exist yet.

Interface plan

REST API

Planned

Versioned resource planning resources, commands, idempotency, and operation status.

Reads + explicit commands

GraphQL

Planned

Composable ResourcePlan 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 resource plan lifecycle facts with minimal payloads.

Past-tense durable facts only

Connected Apps

Planned

Runn / HRIS / PSA 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 /resource-planning	resourcePlan(id: ID!): ResourcePlan	get_resource_planning	—	Resource planning, capacity, staffing, role, and allocation services
Primary command	POST /resource-planning	draftResourcePlanChange(input: DraftResourcePlanChangeInput!): ResourcePlanChangeProposal!	draft_resource_planning_change	resource_plan.created	Resource planning, capacity, staffing, role, and allocation services

Proposed scopes

Proposed scopes are not grantable yet.

resource-planning:readplanned scope

Read governed resource planning resources.

resource-planning:writeplanned scope

Create and edit bounded resource planning fields.

resource-planning:operateplanned scope

Run explicit resource planning lifecycle commands.

Behavioral contract

Cross-cutting rules every implementation and interface must satisfy.

Canonical delegation

Every interface delegates to Resource planning, capacity, staffing, role, and allocation 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/resource-planning

List resource planning

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

resource-planning:read

POST/api/v1/resource-planningconfirmation

Create ResourcePlan

Create one canonical resource with idempotency and actor attribution.

resource-planning:write

GET/api/v1/resource-planning/{id}

Retrieve ResourcePlan

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

resource-planning:read

PATCH/api/v1/resource-planning/{id}confirmation

Update ResourcePlan

Update bounded editable fields using optimistic versioning.

resource-planning:write

POST/api/v1/resource-planning/{id}/confirm-allocationconfirmation

confirm allocation ResourcePlan

Run one explicit domain command after validation and authorization.

resource-planning:operate

confirm allocation a ResourcePlan

Planned request

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

Planned response

{
  "data": {
    "id": "resource_plan_123",
    "status": "allocation_confirmed",
    "version": 3,
    "operation_id": "op_01k4..."
  }
}

GraphQL

Proposed graph

Planned

Types

ResourcePlan

ResourcePlanConnection

ResourcePlanChangeProposal

Operation

Queries

resourcePlan(id: ID!): ResourcePlan

resourcePlanList(filter: ResourcePlanFilter, pagination: PaginationInput): ResourcePlanConnection!

Mutations

draftResourcePlanChange(input: DraftResourcePlanChangeInput!): ResourcePlanChangeProposal!

Planned GraphQL query

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

MCP / Agent API

Proposed tools

Planned

Get Resource Planning

get_resource_planning

Planned

Read the authorized resource planning state, provenance, and allowed actions.

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

Draft Resource Planning change

draft_resource_planning_change

Planned

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

Scope: resource-planning: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 Resource Planning action

request_resource_planning_action

Planned

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

Scope: resource-planning: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 resource planning change and help me apply it.

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

Never infer authority from access to the MCP client.

Webhooks

Proposed event catalog

Planned

Event types

resource_plan.createdplanned event

A canonical ResourcePlan was created.

payload: resource_plan_id, status, created_at

resource_plan.updatedplanned event

Governed ResourcePlan fields changed.

payload: resource_plan_id, changed_fields, version, occurred_at

resource_plan.allocation_confirmedplanned event

The confirm allocation command completed.

payload: resource_plan_id, prior_status, status, occurred_at

Planned event example

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

Connected Apps

Proposed connection roles

Planned

Claude / ChatGPT / IDE clients

Consumer application

Read, explain, and submit bounded resource planning proposals through MCP.

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

Runn / HRIS / PSA

Synchronization provider

Exchange people, availability, demand, and approved allocations.

Authority: Direction, conflict policy, and financial visibility are explicit per provider.

Open contract decisions

Resolve before implementation approval

• Which write operations require manager approval versus project-lead approval?

Proof obligations

Must remain true	Failure indicator
Resource planning, capacity, staffing, role, and allocation 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.