Decision owner
Service owner or change advisory approver
The named role remains accountable for the consequential decision.
Technology & Software
Designed for Software engineer and AI platform engineer
Give software and AI platform engineers one grounded surface that diagnoses service incidents and platform constraints together: correlate deployment manifests, quota and token telemetry, runbooks and prior tickets so a latency spike or a model capacity wall is explained and remediated with an approved, cited change.
Contract TEC-01 · primary aggregate ServiceOperationalContext · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Service owner or change advisory approver
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
A retrieval API's p99 latency triples in West Europe while error rate stays flat.
Give software and AI platform engineers one grounded surface that diagnoses service incidents and platform constraints together: correlate deployment manifests, quota and token telemetry, runbooks and prior tickets so a latency spike or a model capacity wall is explained and remediated with an approved, cited change.
executedChange gives Service owner or change advisory approver the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Service owner or change advisory approver verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Developer support copilot performs symptom and telemetry correlation using PlatformTelemetry and produces correlatedSymptomSet. The transition is deterministic and does not require autonomous model approval.
Why it matters: correlatedSymptomSet gives Change correlation service the evidence needed to begin Deployment bisection, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/symptom-and-telemetry-correlation
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Change correlation service performs deployment bisection using DeploymentManifest and produces suspectChangeSet. The transition is deterministic and does not require autonomous model approval.
Why it matters: suspectChangeSet gives Retrieval orchestrator the evidence needed to begin Prior-art and runbook retrieval, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/deployment-bisection
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieval orchestrator performs prior-art and runbook retrieval using suspectChangeSet and produces RunbookChunk. The transition is deterministic and does not require autonomous model approval.
Why it matters: RunbookChunk gives Developer support copilot the evidence needed to begin Remediation proposal with blast radius, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/prior-art-and-runbook-retrieval
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Developer support copilot performs remediation proposal with blast radius using RunbookChunk and produces RemediationProposal. The transition is deterministic and does not require autonomous model approval.
Why it matters: RemediationProposal gives Service owner or change advisory approver the evidence needed to begin Change approval and production execution, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/remediation-proposal-with-blast-radius
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Service owner or change advisory approver performs change approval and production execution using RemediationProposal and produces executedChange. A named human approver must review the evidence before the transition completes.
Why it matters: executedChange gives Service owner or change advisory approver the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/change-approval-and-production-execution
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved ServiceOperationalContext evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
serviceOperationalContexts/tenantId + /serviceIdA retrieval API's p99 latency triples in West Europe while error rate stays flat. The copilot correlates the window to a deployment 40 minutes earlier that changed the embedding model deployment from a provisioned to a standard SKU, shows tokens-per-minute utilization pinned at 100 percent with 4,900 throttled requests, and finds two prior tickets with the same symptom resolved by restoring provisioned throughput. It cites the capacity runbook, which classifies SKU changes on tier-1 services as change-advisory-required, and proposes a rollback of the SKU change plus a provisioned-throughput increase, assessing blast radius as single-region. The service owner approves at the required level and the change executes.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
serviceOperationalContexts |
Primary | /tenantId + /serviceId |
Service, DeploymentManifest, PlatformTelemetry, IncidentTicket, RemediationProposal |
serviceRunbookLibrary |
Reference | /tenantId + /procedureCategory |
RunbookChunk |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
Service |
serviceOperationalContexts |
/tenantId + /serviceId |
service::{serviceId} |
None |
DeploymentManifest |
serviceOperationalContexts |
/tenantId + /serviceId |
service::{serviceId}::deployment::{deployedAtUtc}::{releaseVersion} |
None |
PlatformTelemetry |
serviceOperationalContexts |
/tenantId + /serviceId |
service::{serviceId}::telemetry::{metricTimestampUtc}::{metricName} |
None |
RunbookChunk |
serviceRunbookLibrary |
/tenantId + /procedureCategory |
procedure::{procedureCategory}::runbook::{runbookDocId}::{chunkOrdinal} |
chunkVector |
IncidentTicket |
serviceOperationalContexts |
/tenantId + /serviceId |
service::{serviceId}::ticket::{ticketNumber} |
symptomVector |
RemediationProposal |
serviceOperationalContexts |
/tenantId + /serviceId |
service::{serviceId}::remediation::{proposalId} |
rationaleVector |
Show which model deployments are approaching their token or provisioned-throughput ceiling in a region.
serviceOperationalContexts
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.serviceId = @serviceId AND c.type = 'PlatformTelemetry' AND c.metricName IN ('tokensPerMinute','provisionedThroughputUtilization') AND c.metricTimestampUtc >= @windowStartUtc AND c.utilizationPct >= @headroomThreshold ORDER BY c.metricTimestampUtc DESC
List deployments that landed inside the regression window for bisection.
serviceOperationalContexts
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.serviceId = @serviceId AND c.type = 'DeploymentManifest' AND c.deployedAtUtc BETWEEN @lastKnownGoodUtc AND @firstFailureUtc ORDER BY c.deployedAtUtc ASC
Find prior tickets with a semantically similar symptom to reuse a proven resolution.
serviceOperationalContexts
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.serviceId = @serviceId AND c.type = 'IncidentTicket' AND c.ticketState = 'resolved' ORDER BY RANK RRF(VectorDistance(c.symptomVector, @currentSymptomVector), FullTextScore(c.symptomSummary, @queryTerms))
Retrieve the remediation procedure valid for this service tier along with its change-control level.
serviceRunbookLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.procedureCategory = @procedureCategory AND c.type = 'RunbookChunk' AND c.appliesToTier = @serviceTier ORDER BY RANK RRF(VectorDistance(c.chunkVector, @queryVector), FullTextScore(c.chunkText, @queryTerms))