Unhealthy after the deploy
Injected failure: forbidden side effect. The deploy lands but the service comes up unhealthy; the health check records it.
Mode unhealthy_after 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 | The service reported unhealthy after the deploy |
Deploy a service
Scenario deploy/unhealthy_after: forbidden side effect.
What the agent reported
The agent reported failure. Its calls, and what it saw come back:
- GET /platform/services/svc_api200
- POST /platform/services/svc_api/deploy200
- POST /platform/services/svc_api/healthcheck200injected: before
Agent notes: tool error: health check after deploy: unhealthy.
What the systems of record showed
Records written after the action:
- platform.deploy_created on svc_apiversion=1.5.0, environment=production
- platform.health_check on svc_apistatus=unhealthy, version=1.5.0
The oracle, reading the databases directly: FAIL
forbidden: unhealthy after deploy; missing platform.health_check; missing crm.note_added
The verdict and why
FAIL The service reported unhealthy after the deploy
Outcome FAIL, policy FAIL; the oracle reads outcome FAIL, policy FAIL.
- 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
- forbidden effectThe service reported unhealthy after the deployplatform.health_check observed within 10m of the action where status=unhealthy
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: