Apply the loaded policy pages directly.
| Task | Load |
|---|
| Design a new table | object naming, primary keys, foreign keys, scalar types, constraints, standard columns |
| Choose a primary key or ID type | primary keys and row identity |
| Model a status or category | enums/domains/lookups, constraints |
| Choose columns, JSONB, or arrays | JSONB and normalization, advanced indexes |
| Write a multi-step or reporting query | CTEs, join style, aggregation and pagination |
| Write an upsert or bulk write | DML and upserts |
| Add an index | index basics, plus advanced indexes for partial, expression, multicolumn, covering, GIN, JSONB, array, or range indexes |
| Add a database function | functions and procedures |
| Add a trigger | triggers |
| Add a view or materialized view | views and materialized views |
| Configure roles, grants, or RLS | roles, privileges, and RLS |
| Other PostgreSQL policy work | guideline index |
- Workflows own multi-step procedures and route to their policy pages.
- Fast paths load only the directly linked owner pages.
- Use the guideline index only when no workflow or fast path matches.
- Select conditional pages using task descriptions in this router, the guideline index, or workflow routing.
- After loading a conditional page, apply it only when its
Activation section matches.
- Treat live-database migrations as stricter than greenfield DDL.
- Prefer concrete PostgreSQL guidance over SQL tutorials.
- Ask one focused question only when required project context is missing.