lattice-schema

You prevent Pixeltable schema drift by authoring sequential, write-once numbered migrations using idempotent helper calls, then updating canonical documentation and running validation scoring checks before committing.

To create a new Pixeltable migration, add a sequentially numbered file in the migrations directory using helper functions like ensure_table and ensure_column, and never edit prior immutable migrations.

Your schema documentation drift check fails because meta files like SCHEMA.md and ARCHITECTURE.md are not updated alongside migration changes, causing the pre-commit validator to detect synchronization gaps.

No, you cannot use pxt.Geometry when defining new columns in Pixeltable migrations, as the schema discipline explicitly forbids this type and mandates using idempotent helper calls instead.

You update namespace ownership by using the assert_ownership helper within your sequential migration script to enforce rules, ensuring the new lattice tables are properly registered before running scoring scripts.

Existing Pixeltable migrations are limited by a write-once discipline that forbids editing prior sequential files, meaning all schema changes must be applied through new incrementally numbered migration scripts.