Schema Format

Desired schemas and inspected snapshots share a versioned representation of one managed PostgreSQL schema. Tables declare supported columns, primary keys and ordinary indexes. Type aliases and nonsemantic ordering normalize; ordered key and index columns remain significant.

Rename intent belongs in a separate explicit mapping file. Reviewed plans contain the canonical source and target descriptions, fingerprints, explained operations and quoted SQL. Their strict JSON loader rejects malformed and inconsistent artifacts.

Verification compares the complete supported managed schema. Extra tables, columns or indexes are drift, rather than being ignored as unrelated. A structure outside the inspector’s supported representation produces an error instead of a partial report. A match concerns structural metadata, not application data or migration history.

Read the schema contract, inspection scope, planning format, execution guide and verification guide for exact boundaries.

The six-session prototype is complete. See the reproducible walkthrough and capability matrix for demonstrated behavior and limits.