Coming soon · Contract draft

Sprint Intelligence

Planned

A sprint-intelligence contract for sprint analytics, trend snapshots, carryover explanations, retrospective signals, and advisory forecasts.

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

Sprint intelligence, report, retrospective, and forecast services

Contract posture

P2 · 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 · Sprint intelligence

Contract dependencies

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

What this unlocks

Explain sprint performance

Read a stable domain model for sprint intelligence without depending on GUI routes or database shapes.

Compare forecast and actuals

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

Subscribe to sprint thresholds

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

Lifecycle and invariants

Sprint Intelligence exposes a bounded lifecycle with explicit commands and named authority at every transition.

draftreviewapprovedpublishedsuperseded

From	To	Command	Authority
draft	review	Review Sprint Intelligence	Sprint intelligence, report, retrospective, and forecast services
review	approved	Approve Sprint Intelligence	Sprint intelligence, report, retrospective, and forecast services
approved	published	Publish Sprint Intelligence	Sprint intelligence, report, retrospective, and forecast services
published	superseded	Supersede Sprint Intelligence	Sprint intelligence, report, retrospective, and forecast services

Lifecycle invariants

• Sprint intelligence is advisory and cannot move work or mutate sprint scope.
• Provider metrics are evidence, not canonical DigitalStack sprint intelligence.

Authority boundaries

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

DigitalStack owns

• Sprint metric definitions
• Carryover and completion explanations
• Retrospective and forecast snapshots

Explicitly not building

• Intelligence mutating sprint scope
• Provider board metrics as canonical truth
• Webhook noise for every transient metric tick

Surface decisions

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

add

Sprint Intelligence 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

Sprint Intelligence as documentation-first until runtime parity exists

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

remove

Claims that Sprint Intelligence is available before REST, GraphQL, MCP, and webhooks are implemented

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

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 sprint intelligence resources, commands, idempotency, and operation status.

Read only

GraphQL

Planned

Composable, read-only sprint intelligence discovery through the canonical service.

Read only · no customer mutations

MCP / Agent API

Planned

Bounded read, draft, and confirmed apply tools with evidence and audit attribution.

Read only

Webhooks

Planned

Past-tense sprint intelligence lifecycle facts with minimal payloads.

Past-tense durable facts only

Connected Apps

Planned

Jira / Azure DevOps / Linear 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 /sprint-intelligence	sprintIntelligence(id: ID!): SprintIntelligence	get_sprint_intelligence	—	Sprint intelligence, report, retrospective, and forecast services
Primary command	Not exposed	Not exposed	Not exposed	sprint_intelligence.created	Sprint intelligence, report, retrospective, and forecast services

Proposed scopes

Proposed scopes are not grantable yet.

sprint-intelligence:readplanned scope

Read governed sprint health, capacity, carryover, completion, and forecast metrics. This is an advisory read surface — it exposes no write or operate scope.

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 Sprint intelligence, report, retrospective, and forecast 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.

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/sprint-intelligence

List sprint intelligence

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

sprint-intelligence:read

GET/api/v1/sprint-intelligence/{id}

Retrieve SprintIntelligence

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

sprint-intelligence:read

GET/api/v1/projects/{id}/sprint-intelligence

Get sprint intelligence

Return sprint health, capacity, carryover, and forecast metrics for a visible project’s active sprint.

sprint-intelligence:read

Execution: Synchronous

List sprint intelligence

Planned request

curl --request GET \
  --url "https://www.digitalstack360.com/api/v1/sprint-intelligence" \
  --header "Authorization: Bearer $DSTACK_API_KEY"

Planned response

{
  "data": [
    {
      "id": "sprint-intelligence_123",
      "status": "available",
      "version": 1
    }
  ]
}

GraphQL

Proposed graph

Planned

Types

SprintIntelligence

SprintIntelligenceConnection

SprintIntelligenceChangeProposal

Operation

Queries

sprintIntelligence(id: ID!): SprintIntelligence

sprintIntelligenceList(filter: SprintIntelligenceFilter, pagination: PaginationInput): SprintIntelligenceConnection!

No GraphQL mutations planned

Read only. Customer callers cannot create, edit, publish, or administer these DigitalStack-owned resources.

Planned GraphQL query

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

MCP / Agent API

Proposed tools

Planned

Get Sprint Intelligence

get_sprint_intelligence

Planned

Read the authorized sprint intelligence state, provenance, and allowed actions.

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

Planned agent workflow

User: Explain the current sprint intelligence for a project I can access.

1. Call get_sprint_intelligence to read the authorized state, contributing evidence, and provenance.
2. Summarize the facts and their evidence for the user.

This is a read-only surface: there is no draft, apply, or command tool to call.

Webhooks

Proposed event catalog

Planned

Event types

sprint_intelligence.createdplanned event

A canonical SprintIntelligence was created.

payload: sprint_intelligence_id, status, created_at

sprint_intelligence.updatedplanned event

Governed SprintIntelligence fields changed.

payload: sprint_intelligence_id, changed_fields, version, occurred_at

sprint_intelligence.refreshedplanned event

The refresh command completed.

payload: sprint_intelligence_id, prior_status, status, occurred_at

Planned event example

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

Connected Apps

Proposed connection roles

Planned

Claude / ChatGPT / IDE clients

Consumer application

Read, explain, and submit bounded sprint intelligence proposals through MCP.

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

Jira / Azure DevOps / Linear

Synchronization provider

Supply sprint activity and completion evidence.

Authority: Provider metrics are evidence; DigitalStack owns published sprint intelligence.

Open contract decisions

Resolve before implementation approval

• Which sprint metrics should emit threshold webhooks versus remain report-only?

Proof obligations

Must remain true	Failure indicator
Sprint intelligence, report, retrospective, and forecast 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.