Persistence
PostgreSQL & MySQL
Versioned service images, reproducible migrations and synthetic data. State observations are part of the profile.
Docs / Profiles
Your stack. A precise execution contract.
Runtime, dependencies, services and observable behavior. A profile brings them together so the same rule can be tested reproducibly.
01 / Execution tracks
Different stacks.
One standard of evidence.
Seven verification areas share the engine contract. Each runtime and service combination carries its own acceptance record.
Node / TypeScriptPythonJava / JVMGoC# / .NET
Scenario services
Redis, where it matters.
Explicit retry, deduplication and side-effect scenarios define how Redis is provisioned, observed and reset.
A language name alone does not guarantee a compatible runtime, framework or service combination.
02 / Profile contract
Nothing important left implicit.
Every admitted profile specifies the inputs, observations and controls needed to reproduce its verdict.
01
Runtime and framework
Exact runtime version, supported build system and application layout.
02
Dependency installation
Committed dependency resolution, approved registries and installation permissions.
03
Application startup
Build and start commands, readiness route, timeout and test environment variables.
04
Persistence
Pinned service image, schema migration, synthetic seed and reset procedure.
05
Observation
Business outputs and durable state that establish the approved rule.
06
Fault controls
Named retry, concurrency, timeout and partial-failure schedules with supported injection points.
07
Repair acceptance
Protected files, customer checks, held-out scenarios and patched commit identity.
03 / Lifecycle
Prepare. Pin.
Verify again.
The installation is reviewable, and every update has a way back.
Prepare
A reproducible fixture.
Keep build and startup commands, readiness, seed/reset steps and expected observations in your repository. Use synthetic data, never production secrets.
Install
Pin the exact release.
Follow the pinned-release workflow. Node.js example commands must not be reused for another runtime.
Read the quickstart →Update
Review before replacing.
Verify the replacement release, change the pin in a reviewed PR and check the digest on a fresh run. Keep the old pin for rollback.
Remove
End access explicitly.
Delete the workflow and revoke integration permissions. A pull request with no check is not a PASS.
Recorded evidence / 3 October 2026
A precise boundary.
An honest result.
The recorded GitHub rehearsal covers a synthetic Express application, Node.js 24 and GitHub-hosted Ubuntu 24.04, with refund-cap and authentication-route checks. It does not certify the other language or database tracks.
The tracks above describe the final-product contract. Accepted profiles require exact versions, clean installation, correct, violated and unsupported cases, fault controls and separate Fix records. Incompatible environments return UNKNOWN.
Inspect recorded results ↗Prepare your first rule ↗