// readme

                             

Ptah manages database change across schemas and persistent inference state. For schemas, it compares a desired schema with a live database and either writes versioned migrations or applies an approved plan directly. For inference state, it builds a candidate generation beside the active one, calls an external embedding endpoint, verifies the result, and switches consumers with a rollback path.

The command-line interface runs without a Go toolchain, and the same planning components are available as Go packages.

Schema changes

Both workflows use the same comparison and planning model. The difference is whether SQL becomes a reviewed artifact in version control before it runs.

Persistent inference state

Ptah orchestrates the migration; it does not run inference. It reads source rows, calls the external endpoint, and writes the candidate generation itself, leaving the active generation untouched until verification and cutover.

The inference migrations guide covers the…