Oko database schema

Oko’s hosted database schema is owned by the dedicated `wisent-supabase-oko` repository. The deployed Supabase project reference is alvaewvbyxpgwdpugnxy.

Source of truth

The ordered migrations in wisent-supabase-oko are the canonical definition of the database. They own the tables, functions, policies, grants, indexes, and other schema objects consumed by Oko products.

Application repositories may depend on this contract, but they must not redefine or privately own the schema. Client code, including Oko’s desktop, web, and iOS surfaces, must treat the database as an external versioned dependency.

Change workflow

Every schema change starts as a migration in wisent-supabase-oko and is reviewed through a pull request. Pull-request CI applies the complete migration history to a fresh database and runs Splinter so that failures are caught against the full schema rather than an already-mutated developer project.

A pull request proves that the migration chain can create the expected database; it does not deploy the hosted project.

Deployment

After review, merging to main deploys the canonical migrations to Supabase project alvaewvbyxpgwdpugnxy. Application repositories do not deploy schema changes and must not contain a competing migration history.

This boundary keeps review, fresh-stack verification, and production deployment attached to one auditable source.