Introducing ForgeSchema

A schema change is easy to describe casually and surprisingly difficult to execute reliably. A renamed column can look like a deletion followed by an addition. A new requirement can conflict with existing rows. A migration prepared yesterday can be wrong for a database changed this morning. ForgeSchema is being built to make those differences explicit before a change is applied.

The engine inspects PostgreSQL, compares current structure with a desired YAML schema, generates an explained migration artifact, applies supported changes transactionally and verifies the target independently. Explicit renames preserve intent; unsupported changes block the entire plan.

All six prototype sessions are complete. The customer walkthrough runs the compiled Go CLI against an isolated synthetic fixture, preserves two original rows across six operations and demonstrates stale-plan rejection and drift detection. It passed from fresh CI checkouts on PostgreSQL 16.10 and 17.6.

The strict schema contract rejects features it cannot honor. This remains an unreleased prototype with a narrow operation set. External DDL must be paused during apply, and a structural match does not establish application correctness or continued future state. Read the roadmap for the handoff and remaining scope.