Capabilities

Context Engine

Read governed delivery knowledge two ways: query the deterministic, evidence-backed Context Engine for a synthesized project, engagement, or portfolio briefing (findings, risks, blockers, coverage, freshness, provenance), or search the Engagement Knowledge Corpus for exact evidence passages — ranked full-text retrieval of ingested Context Sources with source, page/paragraph, and provenance-quality attribution. Search returns evidence, never a synthesized answer; neither surface exposes package-authoring authority or a competing source of truth.

Interfaces

RESTAvailable

REST exposes synthesized portfolio/project/engagement queries, deterministic Engagement Knowledge Corpus evidence search (ranked full-text with keyset pagination and page-level provenance), and package, overview, evidence, and provider reads with project/engagement filters.

MCPAvailable

MCP exposes synthesized query_context and evidence-corpus search_context (exact passages with provenance; engagement queries fan out to caller-visible child projects), plus governed package inspection with project/engagement filters.

GraphQLAvailable

GraphQL exposes a typed subjectRef for synthesized queries plus project/engagement filters on overview, package search, package lists, and providers.

WebhooksAvailable

Context Engine emits durable contribution-persisted, merge-decided, and entry-superseded facts from the canonical evolution commit path.

Required scopes

agent:readAPI key scoperequired

Read agent-optimized project delivery, sprint, and risk read models via the Agent API (/api/agent/v1). Directional signals only — no rates, invoice data, or personal metadata.

context-engine:readAPI key scoperequired

Search and inspect governed context packages, evidence references, provenance, freshness, coverage, and contributing providers.

Examples

Query context — view in REST API reference

POST /api/v1/context/query

curl -X POST "https://www.digitalstack360.com/api/v1/context/query" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"question":"Why is this project at risk?","project_id":"24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2"}'

Search context evidence — view in REST API reference

POST /api/v1/context/search

curl -X POST "https://www.digitalstack360.com/api/v1/context/search" \
  -H "Authorization: Bearer $DS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"subject_ref":{"type":"project","id":"24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2"},"query":"Shopify Tax"}'

Context Engine overview — view in REST API reference

GET /api/v1/context-engine

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine?project_id=24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2" \
  -H "Authorization: Bearer $DS_API_KEY"

Retrieve context package — view in REST API reference

GET /api/v1/context-engine/:id

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine/9c9f22ac-8b6a-4a72-8145-9d1714f8af52" \
  -H "Authorization: Bearer $DS_API_KEY"

Search structured context — view in REST API reference

GET /api/v1/context-engine/search

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine/search?query=rollout terminology&project_id=24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2" \
  -H "Authorization: Bearer $DS_API_KEY"

List context packages — view in REST API reference

GET /api/v1/context-engine/packages

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine/packages?project_id=24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2" \
  -H "Authorization: Bearer $DS_API_KEY"

Get context package evidence — view in REST API reference

GET /api/v1/context-engine/packages/:id/evidence

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine/packages/9c9f22ac-8b6a-4a72-8145-9d1714f8af52/evidence" \
  -H "Authorization: Bearer $DS_API_KEY"

List context providers — view in REST API reference

GET /api/v1/context-engine/providers

curl -X GET "https://www.digitalstack360.com/api/v1/context-engine/providers?project_id=24ea6df2-7f4c-4c32-9fc1-6c8a0cb5b4b2" \
  -H "Authorization: Bearer $DS_API_KEY"

“Which of my projects are currently at risk, and why?”

“Search this project’s context for “Shopify Tax”.”

“Show me the current Context Engine coverage and freshness posture.”

“List the newest ready context packages.”

“Explain context package {package_id} and its provenance.”

“Search governed context for rollout terminology.”

“Show the evidence references behind context package {package_id}.”

“Which providers contribute to Context Engine and what authority do they have?”

GraphQL examples

Query contextAvailablecontext-engine:read

Run the same deterministic evidence-backed Context Engine used by REST and MCP.

GraphQL

query QueryContext($question: String!, $subjectRef: ContextEngineSubjectInput) {
  contextQuery(question: $question, subjectRef: $subjectRef)
}

Search context packagesAvailablecontext-engine:read

Search governed persisted context and inspect provenance and freshness.

GraphQL

query SearchContext($query: String!, $projectId: ID) {
  contextEngineSearch(query: $query, projectId: $projectId, first: 25) {
    totalCount
    truncated
    nodes {
      score
      package {
        id status term summary contributionType
        scope { projectId engagementId adoptionWorkspaceId }
        freshness { status asOf ageDays }
        provenance { source promoterIdentity generatedAt }
        coverage { evidenceCount providerCount missing }
      }
    }
  }
}

Inspect package evidence and providersAvailablecontext-engine:read

Read policy-safe evidence references and provider authority boundaries.

GraphQL

query InspectContext($packageId: ID!, $engagementId: ID) {
  contextEnginePackageEvidence(packageId: $packageId) {
    id provider capability asOf
    freshness { status asOf ageDays }
    reference { kind id class }
    provenance { source promoterIdentity generatedAt }
  }
  contextEngineProviders(engagementId: $engagementId) {
    id name classification capabilities contributionCount
    coverageStatus freshnessStatus authority
  }
}

Webhook emits

context_engine.contribution_persistedAvailable

A governed provider contribution was persisted into the Context Engine.

Resource: context_engine_evolution

subject_idrelated_entry_idevolution_kindoccurred_at

context_engine.merge_decidedAvailable

A governed Context Engine overlap/merge decision was committed.

Resource: context_engine_evolution

subject_idrelated_entry_idevolution_kindoccurred_at

context_engine.entry_supersededAvailable

A Context Engine entry was superseded by a governed successor.

Resource: context_engine_evolution

subject_idrelated_entry_idevolution_kindoccurred_at

All webhook events use the shared v1 envelope, signed delivery, and minimal payload rule. Fetch by resource id for expanded data.

Operating contract

These boundaries remain part of the customer-facing contract after capability promotion.

Must remain true

• Every synthesized claim preserves evidence references, coverage, freshness, and package provenance.
• Corpus search returns exact stored passages with source and page/paragraph provenance and performs no synthesis, semantic, or vector search; only active source-content and segmenter versions are eligible to surface.
• Corpus retrieval enforces the context:read permission for the resolved principal plus project visibility; engagement queries fan out only to caller-visible child projects, never to unbound sources.
• Generated context is advisory read output and never becomes canonical domain truth without the source domain’s governed commit path.
• Provider contributions add evidence with provenance; providers do not own final Context Engine composition or canonical source truth.
• Package, evidence, provider, corpus-search, GraphQL, and MCP reads all delegate to the same Context Engine services and account boundary.
• Financial and staffing context remain separately scoped even when the caller can query Context Engine.
• Project and engagement targeting derives from canonical project and commercial-engagement links; Context Engine never owns a competing subject mapping.

Explicitly not exposed

• Customer-authored context-package create, update, publish, or delete operations
• Semantic or vector similarity search — corpus retrieval is PostgreSQL full-text only
• Synthesized answers from the evidence-search primitive; search_context returns ranked passages, not conclusions
• Arbitrary model execution or a generic prompt-completion gateway
• Raw source bodies or unrestricted evidence excerpts through package evidence endpoints
• Webhook events emitted merely because a customer performed a read
• A second project, delivery, risk, or work-item source of truth inside Context Engine

System boundaries

Systems commonly integrated with this capability. Each row states the boundary and its native status; it does not transfer canonical authority to the connected system.

DigitalStack owns

• Context package composition and deterministic query planning
• Evidence references, provenance, coverage, freshness, and provider disclosure
• Engagement Knowledge Corpus: source registration, deterministic segmentation, versioned evidence spans, and authorized full-text retrieval with page-level provenance
• Read-only projection of governed persisted contributions

Source systems own

• Canonical project, delivery, risk, work-item, and imported knowledge facts that packages cite
• The original documents and Context Sources that ingested evidence spans are extracted from

Typical integration patterns

Your existing systems of record

Contribute canonical-domain evidence through DigitalStack provider and adoption contractsDigitalStack has a native connection and ingestion foundation for this system already — public developer-platform exposure for this capability is still limited or planned.

Related guides

Context Engine

Interfaces

Required scopes

Examples

GraphQL examples

Webhook emits

Operating contract

System boundaries

Related guides

REST API reference

GraphQL overview

MCP overview

Authentication & scopes

Webhooks overview

Context Platform (unified)