Test, automate, and operate

Operational Ptah work should leave an observable result: a test report, an exit code, a sealed artifact, a recorded revision, or a diagnostic tied to a stable error fragment. Choose the task that owns that result.

Common tasks

Test migrations and schemasRun cases against throwaway databases and verify expected success or failure.

Build a CI gateGate drift, migration integrity, unsafe SQL, generated output, and test cases.

Load controlled dataReconcile versioned lookup rows separately from ordinary schema changes.

Publish an OCI artifactPackage, verify, and distribute migration or schema artifacts through a registry.

Troubleshoot a failureStart from the exact error or symptom and verify the repair.

Choose the safety boundary

Use a throwaway database for tests, a dev or shadow database for replay and planning, and a reviewed target URL for a real apply. These roles are not interchangeable; database URLs and dev databases defines each one.

Commands that mutate a database keep their warning and verification step on the task page where the operation runs.

Reference

Use exit codes for automation contracts and test-case reference for the exact case format.