Safe environment

Prove the contract before production activation

Sandbox keeps data, credentials, and webhook delivery separate from production and prevents false-success integrations.

Read guide

Activation gate

01

Minimum matrix

Valid request with valid scope.

02

Consumer contract tests

Use secret-free fixtures and verify schema and meaning rather than JSON field order. Run consumer tests whenever the producer changes.

03

Activation

Submit evidence with test results, SHA, version, environment, and rollback. Begin with a canary scope that can be disabled without a dangerous reverse migration.

Live execution is disabled to protect production data and credentials.

A path is not a production contract until it is marked verified and matches the runtime source.