Degraded service
Injected failure: precondition violated. The service is degraded (svc_batch); the agent reads that and stops.
Mode degraded_service of the failure matrix, on one of its eight workflows. Each run below is the sandbox's scripted agent acting on the sandbox's fake systems of record under the injected failure, an oracle reading those systems' databases, and the verdict of engine 1.0.0 from the systems of record alone.
Last changed Markdown versionllms.txt
| Workflow | Agent reported | Oracle | CommitLayer | Why |
|---|---|---|---|---|
| Deploy a service | failure | FAIL | FAIL | Service was not healthy before the deploy |
Deploy a service
Scenario deploy/degraded_service: precondition violated.
What the agent reported
The agent reported failure. Its calls, and what it saw come back:
- GET /platform/services/svc_batch200
Agent notes: tool error: service not healthy (degraded).
What the systems of record showed
No record was written after the action.
The oracle, reading the databases directly: FAIL
precondition: service not healthy; missing platform.deploy_created; missing platform.health_check; missing crm.note_added
The verdict and why
FAIL Service was not healthy before the deploy
Outcome FAIL, policy FAIL; the oracle reads outcome FAIL, policy FAIL.
- preconditionService was not healthy before the deploylatest platform.service_health before the action had status=healthy
- expected effectThe platform shows no deployplatform.deploy_created observed within 10m of the action
- expected effectNo healthy check after the deployplatform.health_check observed within 10m of the action where status=healthy
- expected effectNo change note was addedcrm.note_added observed within 10m of the action
Run it in the Failure Lab
The Failure Lab replays each run above: the agent's calls, the records the systems held and the verdict. No account is needed. The verdict comes from the production engine while you watch.
The sandbox in the app runs the exact scenario in your own workspace, as a verified action: