sql/ | The logical schema (tables, columns, keys and indexes made from governance by a projection, with the report of the flow and the types of rows), the physical schema (a logical schema bound to a dialect and a case style, as statements) and the dialects of PostgreSQL, SQLite and DuckDB, which are extensions; the extensions are in sql/extensions/: documentation (comments, documentation tables, governance tables), views, access (row-level security and grants from governance), routines and partitions; names that carry a schema are in sql/physical/; protected access (tables in a schema, views over them, rights and a guard) is in sql/extensions/protected-access/; the safety features (quarantine instead of drop, lock discipline, verification) are in sql/extensions/safety/; the plan report (what a plan does in the words of governance, and who must approve it) is in sql/extensions/plan-report/; the rewrite (a table made again where the engine cannot change it, a type cast) is in sql/extensions/rewrite/; the history strategy (a plan frozen into files, replayed, or delivered as a release package or a procedure in the database) is in sql/extensions/history/; the convergence strategy (the plan from the state a database is in, reviewed or autonomous) is in sql/extensions/convergence/; parallel versions (two versions of an application on one database through schemas of views, an expand that destroys nothing, and the retirement of the older) are in sql/extensions/rollout/; integrations (rows, CSV text, an attached database or an adapter landed, checked and loaded by append, upsert, replace or snapshot in one transaction, with a ledger and lineage) are in sql/extensions/integrations/; transforms (models whose SQL asks for names by their words, built in order, each in one transaction with its tests, so that a model whose tests find wrong rows is not published) are in sql/extensions/transforms/; queries (a catalog of read-only queries over the names of a schema, with typed parameters that enter only as literals, verified against a database and compared between versions of a schema) are in sql/extensions/queries/; the ephemeral target (a database that is a build product: one SQL file from governance and typed rows, the same bytes every time, committed and diffed in Git, made into a database in one transaction and checked for staleness) is in sql/extensions/target/; kinds (reference data kept as CSV, read into typed rows, checked against a table and written as a TypeScript module) are in sql/extensions/kinds/; osquery ATC (the auto_table_construction configuration that makes osquery tables from a SQLite database, made from a logical schema) is in sql/extensions/osquery-atc/; operations (the business operations of a model: contracts in governance, run by sql/extensions/operations in one transaction, held to what they declare, with the audit trail written with them) are in sql/extensions/operations/, with the identity decision engine (one decide() for every kind of principal: roles, groups, inheritance, relationships and policies, refusal wins, unknown never allows, delegation never adds), the audit chain and the operations of delegation and agents (delegate, revoke, tool calls with budgets and single-use approvals, the kill switch) in sql/extensions/operations/identity/; the presets (team-managed, dba-managed, reviewed-convergence and autonomous-convergence: each a strategy with the features it needs and the settings it calls for) are in sql/presets/; the generators (diagrams in Mermaid and D2, the data dictionary in Markdown and HTML, row types in Rust and Zod, the register of personal data and security) are in sql/extensions/generators/ | governance/, engine/, by package name |
sql/lifecycle/ | What changes a database from one physical schema to the next: the hashed state of a database, the changes between two states, the plan of classified steps, the hash-chained ledger and the run on a driver. Strategies and features of migration (idempotency first) are extensions of it. | sql/physical/, sql/logical/, governance/, engine/, by package name |
acceptance/ | The acceptance kits (acceptance/README.md): testing by people or agents, for the experience beyond the code, with their own specifications (acceptance/spec-kit), made-up data and checks, and run apart from the library's tests by bun run acceptance. The first is arcactl-pg, a UAT of arcactl and row-level security on PostgreSQL. Not packed. | governance/, sql/, models/, by package name |