Skip to content
All failure modes
Failure mode

Wrong environment

Injected failure: parameter not allowed. Agent deploys to an environment the policy does not allow (sandbox-prod).

Mode wrong_environment 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.

Synthetic demo data.

Last changed Markdown versionllms.txt

WorkflowAgent reportedOracleCommitLayerWhy
Deploy a servicesuccessFAILFAILlimit exceeded: environment not one of staging, production (was sandbox-prod)

Deploy a service

Scenario deploy/wrong_environment: parameter not allowed.

What the agent reported

The agent reported success. Its calls, and what it saw come back:

  • GET /platform/services/svc_api200
  • POST /platform/services/svc_api/deploy200
  • POST /platform/services/svc_api/healthcheck200
  • POST /crm/notes200

What the systems of record showed

Records written after the action:

  • platform.deploy_created on svc_api
    version=1.5.0, environment=sandbox-prod
  • platform.health_check on svc_api
    status=healthy, version=1.5.0
  • crm.note_added on svc_api
    author=lab-agent, text=Deployed 1.5.0 to sandbox-prod

The oracle, reading the databases directly: FAIL

limit: environment not allowed

The verdict and why

FAIL limit exceeded: environment not one of staging, production (was sandbox-prod)

Outcome PASS, policy FAIL; the oracle reads outcome PASS, policy FAIL.

  • limit
    environment not one of staging, production

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: