Coming soon · Contract draft

Solution & Architecture

Planned

A project solution graph that connects systems, data intelligence, architecture decisions, mappings, and governed baseline publication.

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

Solution planning, architecture, system inventory, and data-intelligence services

Contract posture

P2 · 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 6 · Knowledge and intake

Contract dependencies

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

What this unlocks

Query solution architecture

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

Trace change impact

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

Publish reviewed baselines

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

Lifecycle and invariants

Solution & Architecture exposes a bounded lifecycle with explicit commands and named authority at every transition.

draftreviewbaselinedsuperseded

From	To	Command	Authority
draft	review	Request architecture review	Solution and architecture services
review	baselined	Publish baseline	Solution and architecture services
baselined	superseded	Publish replacement	Solution and architecture services

Lifecycle invariants

• Diagrams illustrate but do not own system truth.
• Repository evidence respects project access.

Authority boundaries

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

DigitalStack owns

• Solution and system inventory
• Architecture decisions and impact links
• Schema, flow, and mapping lifecycle

Explicitly not building

• Diagrams as authoritative system state
• Unreviewed AI architecture changes
• Repository scans bypassing project access

Surface decisions

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

add

Solution sections, systems, decisions, schemas, flows, mappings, impact, and baseline exports

Architecture consumers need a connected model rather than isolated diagrams.

keep

Reviewed baseline publication

AI and source evidence may draft changes but not redefine architecture silently.

remove

Diagram coordinates as domain truth and unrestricted repository scans

Presentation geometry and external source access are not architectural authority.

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 solution & architecture resources, commands, idempotency, and operation status.

Reads + explicit commands

GraphQL

Planned

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

Composable reads + bounded delegated mutations

MCP / Agent API

Planned

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

Read + proposal/confirmed commands only

Webhooks

Planned

Past-tense solution lifecycle facts with minimal payloads.

Past-tense durable facts only

Connected Apps

Planned

GitHub / diagram / data catalog tools 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 /solutions	solution(id: ID!): Solution	get_solution_architecture	—	Solution planning, architecture, system inventory, and data-intelligence services
Primary command	POST /solutions	draftSolutionChange(input: DraftSolutionChangeInput!): SolutionChangeProposal!	draft_solution_architecture_change	solution.created	Solution planning, architecture, system inventory, and data-intelligence services

Proposed scopes

Proposed scopes are not grantable yet.

solutions:readplanned scope

Read governed solution & architecture resources.

solutions:writeplanned scope

Create and edit bounded solution & architecture fields.

solutions:operateplanned scope

Run explicit solution & architecture 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 Solution planning, architecture, system inventory, and data-intelligence 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/solutions

List solution & architecture

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

solutions:read

POST/api/v1/solutionsconfirmation

Create Solution

Create one canonical resource with idempotency and actor attribution.

solutions:write

GET/api/v1/solutions/{id}

Retrieve Solution

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

solutions:read

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

Update Solution

Update bounded editable fields using optimistic versioning.

solutions:write

POST/api/v1/solutions/{id}/publish-baselineconfirmation

publish baseline Solution

Run one explicit domain command after validation and authorization.

solutions:operate

publish baseline a Solution

Planned request

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

Planned response

{
  "data": {
    "id": "solution_123",
    "status": "baselined",
    "version": 3,
    "operation_id": "op_01k4..."
  }
}

GraphQL

Proposed graph

Planned

Types

Solution

SolutionConnection

SolutionChangeProposal

Operation

Queries

solution(id: ID!): Solution

solutionList(filter: SolutionFilter, pagination: PaginationInput): SolutionConnection!

Mutations

draftSolutionChange(input: DraftSolutionChangeInput!): SolutionChangeProposal!

applySolutionChange(input: ApplySolutionChangeInput!): SolutionPayload!

Planned GraphQL query

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

MCP / Agent API

Proposed tools

Planned

Get Solution & Architecture

get_solution_architecture

Planned

Read the authorized solution & architecture state, provenance, and allowed actions.

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

Draft Solution & Architecture change

draft_solution_architecture_change

Planned

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

Scope: solutions: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.

Apply Solution & Architecture change

apply_solution_architecture_change

Planned

Apply a reviewed proposal through the canonical service.

Scope: solutions:operate
Input: Proposal id, expected version, idempotency key, and explicit confirmation.
Output: Updated canonical resource and audit reference.
Write boundary: Confirmation, optimistic versioning, and idempotency required.

Planned agent workflow

User: Review the proposed solution & architecture change and help me apply it.

1. Call get_solution_architecture to inspect current state, provenance, and allowed actions.
2. Call draft_solution_architecture_change to create a proposal without changing canonical state.
3. Show validation results, conflicts, and the exact command to the user.
4. After explicit confirmation, call apply_solution_architecture_change with the proposal version.

Never infer authority from access to the MCP client.

Webhooks

Proposed event catalog

Planned

Event types

solution.createdplanned event

A canonical Solution was created.

payload: solution_id, status, created_at

solution.updatedplanned event

Governed Solution fields changed.

payload: solution_id, changed_fields, version, occurred_at

solution.baselinedplanned event

The publish baseline command completed.

payload: solution_id, prior_status, status, occurred_at

Planned event example

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

Connected Apps

Proposed connection roles

Planned

Claude / ChatGPT / IDE clients

Consumer application

Read, explain, and submit bounded solution & architecture proposals through MCP.

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

GitHub / diagram / data catalog tools

Source connector

Supply repository, diagram, and catalog evidence.

Authority: Evidence informs DigitalStack solution records; publication remains governed.

Open contract decisions

Resolve before implementation approval

• Which architecture changes require a formal decision record before baseline publication?

Proof obligations

Must remain true	Failure indicator
Solution planning, architecture, system inventory, and data-intelligence 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.