suite/qualified.test.ts: where the dialect has none the schema's words come before each table's name with the case style, the length is checked after they are added, and no schema is made
suite/qualified.test.ts: a statement source is given the reference to a table, to a table of an extension, and the name an extension's table is written by
suite/qualified.test.ts: the comments, the documentation tables, the governance tables and the views are made in the schema on every engine, and the tables are in none other; suite/qualified.test.ts: policies, routines and partitions refer to the tables in the schema on PostgreSQL
suite/qualified.test.ts: a state records the schema where the dialect has schemas, and a plan writes its statements and the probes of its guards qualified by it
suite/qualified.test.ts: the steps from empty and from each version to the next leave the database that bind makes in the same schema, on three engines
suite/qualified.test.ts: the comments, the documentation tables, the governance tables and the views are made in the schema on every engine, and the tables are in none other; suite/qualified.test.ts: policies, routines and partitions refer to the tables in the schema on PostgreSQL
suite/protected-access.test.ts: the tables are in their schema and a view of each is in the other, read through on every engine, with the comment, and no view for a table of an extension
suite/protected-access.test.ts: the tables are in their schema and a view of each is in the other, read through on every engine, with the comment, and no view for a table of an extension
suite/protected-access.test.ts: a row is inserted, updated and deleted through the view on PostgreSQL and SQLite, and DuckDB's views are read-only and say so
suite/protected-access.test.ts: on PostgreSQL a role that owns nothing sees through the view only the rows of its scope and cannot read the table, a writer writes only in its scope, and the guard refuses a change of a table outside a migration
suite/protected-access.test.ts: on PostgreSQL a role that owns nothing sees through the view only the rows of its scope and cannot read the table, a writer writes only in its scope, and the guard refuses a change of a table outside a migration
suite/protected-access.test.ts: enforcement asked for where the dialect cannot is an error value, and convention makes the schemas and views and nothing else
suite/protected-access.test.ts: a renamed attribute stays in its view under its old name for as long as governance says so, and leaves it when the annotation is taken out
suite/protected-access.test.ts: a step that changes a table drops its views before and makes them again after, in the same transaction, so a view never blocks the change; the lifecycle gives the transform the states and runs the setting first
suite/protected-access.test.ts: a step that changes a table drops its views before and makes them again after, in the same transaction, so a view never blocks the change; the lifecycle gives the transform the states and runs the setting first
suite/protected-access.test.ts: what governance says must be hidden is hidden in the view, a role the settings name sees it as it is, and a mask the dialect cannot write is an error value
suite/protected-access.test.ts: on PostgreSQL a role that owns nothing sees through the view only the rows of its scope and cannot read the table, a writer writes only in its scope, and the guard refuses a change of a table outside a migration; suite/protected-access.test.ts: with a secret that seals the flag, a session that sets the flag to on is not a migration, and one that holds the secret is
suite/protected-access.test.ts: the tables are in their schema and a view of each is in the other, read through on every engine, with the comment, and no view for a table of an extension; suite/protected-access.test.ts: the plans of a domain's versions run with the layer leave the tables in their schema, a view of each with the last version's columns, the reference rows, and every step safe to run twice
suite/safety.test.ts: a step's verification is run in its transaction, a check that fails rolls the step back and records nothing, and the verification is part of the step's identifier
suite/safety.test.ts: a step is tried again when its error is of the kind the project names, a number of times with a pause, and the last error is returned where it still fails
suite/quarantine-reuse.test.ts: a column dropped a second time does not lose its new values to the quarantine of the first drop: the step fails its verification, is rolled back, and says what to do; suite/safety.test.ts: dropping a column keeps its values in a quarantine table, does not copy again, is data-dependent and quarantine-reversible, and undoing the step restores the values
suite/safety.test.ts: dropping a table renames it to its quarantined name with its rows, undoing brings it back, and a purge drops a quarantine table and nothing else
suite/safety.test.ts: dropping a table renames it to its quarantined name with its rows, undoing brings it back, and a purge drops a quarantine table and nothing else
suite/safety.test.ts: a step that changes a table asks for its locks with a timeout where the dialect has them, and gives the run a retry for a lock timeout
suite/safety.test.ts: a foreign key or a check is added without checking the rows and then checked, and the step's verification says the constraint is valid
suite/safety.test.ts: each step says what must be true after it, and a step that changes the structure and not the data finds the same number of rows, on three engines
suite/safety.test.ts: dropping a column keeps its values in a quarantine table, does not copy again, is data-dependent and quarantine-reversible, and undoing the step restores the values; suite/safety.test.ts: dropping a table renames it to its quarantined name with its rows, undoing brings it back, and a purge drops a quarantine table and nothing else; suite/safety.test.ts: with the protection layer and idempotency, dropping a column on three engines leaves the values in quarantine, the view without the column, and the step safe to run twice
suite/plan-report.test.ts: the report gives the dialect, the states, the counts by class, reversibility and idempotency, and for each step its class, reversibility, idempotency and an estimate of the lock
suite/plan-report.test.ts: the report gives the dialect, the states, the counts by class, reversibility and idempotency, and for each step its class, reversibility, idempotency and an estimate of the lock
suite/plan-report.test.ts: for what a step removes the report says what governance said of it, and who has to approve: the steward, the role for personal data, for a restricted element and for a destructive or hand-written step, each with the reason
suite/plan-report.test.ts: the report says what governance itself changes between the schemas, and where the schema before is not given says it does not know
suite/plan-report.test.ts: for what a step removes the report says what governance said of it, and who has to approve: the steward, the role for personal data, for a restricted element and for a destructive or hand-written step, each with the reason
suite/plan-report.test.ts: the report says what governance itself changes between the schemas, and where the schema before is not given says it does not know
suite/rewrite.test.ts: a change the core cannot make is offered to the fallback before it is an error, the step goes through the transforms, and a person's step takes its place
suite/rewrite.test.ts: on SQLite a key is added by making the table again, the rows and what refers to the table are kept, the new definition is enforced, and the step says what it is; suite/rewrite.test.ts: a column made required is made by making the table again where the engine cannot, a row that does not meet it rolls the step back whole, and it succeeds once the row does; suite/rewrite.test.ts: the statements are written from the states: the indexes are made after, the primary key is kept, and a column the tables have in common is copied
suite/rewrite.test.ts: on SQLite a key is added by making the table again, the rows and what refers to the table are kept, the new definition is enforced, and the step says what it is; suite/rewrite.test.ts: the protection layer's views are dropped before and made again after a table is made again, and a step that makes a table again relies on the ledger alone
suite/rewrite.test.ts: what cannot be made safely is left to a person with the reason: a required column with no default, a table that others refer to where the engine stops it, and a type that is not allowed to be cast
suite/rewrite.test.ts: on SQLite a key is added by making the table again, the rows and what refers to the table are kept, the new definition is enforced, and the step says what it is; suite/rewrite.test.ts: the statements are written from the states: the indexes are made after, the primary key is kept, and a column the tables have in common is copied
suite/rewrite.test.ts: a type is cast in place where the engine can alter a column and by making the table again where it cannot, when casts are allowed, and says that values may change
suite/rewrite.test.ts: on SQLite a key is added by making the table again, the rows and what refers to the table are kept, the new definition is enforced, and the step says what it is; suite/rewrite.test.ts: a column made required is made by making the table again where the engine cannot, a row that does not meet it rolls the step back whole, and it succeeds once the row does; suite/rewrite.test.ts: the protection layer's views are dropped before and made again after a table is made again, and a step that makes a table again relies on the ledger alone
suite/rewrite.test.ts: a table that has triggers is not made again without them: the step fails its verification, is rolled back whole, and the trigger and the rows are as they were
suite/history.test.ts: a step is a file with a numbered slug name, a JSON header, its statements with their guards, its undo and what must be true after, the same every time, and parsing it gives the step back
suite/history.test.ts: the manifest chains the files, and a file changed, taken out, put in or moved is found, as is one whose manifest entry was edited to match
suite/history.test.ts: freeze gives only files that are new, never rewrites one, refuses a plan that does not start where the history ends, and freezes the repeatable objects and the state beside the steps
suite/history.test.ts: freeze gives only files that are new, never rewrites one, refuses a plan that does not start where the history ends, and freezes the repeatable objects and the state beside the steps
suite/history.test.ts: the files are checked and then replayed through the lifecycle's run on three engines to the same state, the ledger holds the same steps, a second replay does nothing, and a history that does not check runs nothing
suite/history.test.ts: the files are checked and then replayed through the lifecycle's run on three engines to the same state, the ledger holds the same steps, a second replay does nothing, and a history that does not check runs nothing
suite/history.test.ts: freeze gives only files that are new, never rewrites one, refuses a plan that does not start where the history ends, and freezes the repeatable objects and the state beside the steps
suite/history.test.ts: a release package is plain SQL a DBA runs: a preflight that returns a row only on the right state, an installer in one transaction with the guards inside, a verification, a back-out and a runbook; and it is an error where a guard cannot be written
suite/history.test.ts: a procedure inside PostgreSQL applies the history, chains its ledger, refuses a ledger that was changed and a state no step starts from, is run again to do nothing, and applies only what is missing when the history grows
suite/convergence.test.ts: the state of a database made from a schema has the hash of the desired state, with types read under another name found the same, and the words of a table found with the schema's taken off
suite/convergence.test.ts: drift made by hand is a difference: a column added is a column to drop, a table missing is a table to make, a table made by hand is a table to drop, and what is not compared is not
suite/convergence.test.ts: a proposal is the plan from the state read, pinned to it and to the state it ends in, empty between equal states, and refused as stale when the database moved
suite/convergence.test.ts: a proposal is the plan from the state read, pinned to it and to the state it ends in, empty between equal states, and refused as stale when the database moved
suite/convergence.test.ts: a reviewed proposal is text a person approves by its hash, the same every time; it is applied only if the text is the approved one, leaves the database as bind makes it, and a second apply finds nothing to do
suite/convergence.test.ts: autonomous convergence applies what only adds, holds a plan that renames or drops and changes nothing, holds everything when the policy is off, and says which steps it did not allow; suite/convergence.test.ts: a step that fails leaves the database at the step before and the next access resumes, a lock is taken where the dialect has one, and a rehearsal that says no holds the plan
suite/convergence.test.ts: autonomous convergence applies what only adds, holds a plan that renames or drops and changes nothing, holds everything when the policy is off, and says which steps it did not allow
suite/convergence.test.ts: a step that fails leaves the database at the step before and the next access resumes, a lock is taken where the dialect has one, and a rehearsal that says no holds the plan
suite/convergence.test.ts: autonomous convergence applies what only adds, holds a plan that renames or drops and changes nothing, holds everything when the policy is off, and says which steps it did not allow
suite/convergence.test.ts: drift made by hand is a difference: a column added is a column to drop, a table missing is a table to make, a table made by hand is a table to drop, and what is not compared is not; suite/convergence.test.ts: a reviewed proposal is text a person approves by its hash, the same every time; it is applied only if the text is the approved one, leaves the database as bind makes it, and a second apply finds nothing to do
suite/convergence.test.ts: a default changed by hand is drift on the engines that can change one, and the defaults the model made are not drift on any engine; suite/convergence.test.ts: what a person made outside the model is held, not dropped, where the project says to hold it: a table, a column and an index are left alone and named, and the plan has no step for them
suite/rollout.test.ts: the expanded schema is the latest with what older versions still use kept as optional and what only the latest has made optional, a renamed column being the same column
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used; suite/rollout.test.ts: the schema's pattern and the primary version are settings, DuckDB's views read, and SQLite's views carry the version's label in their names
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used
suite/rollout.test.ts: the schema's pattern and the primary version are settings, DuckDB's views read, and SQLite's views carry the version's label in their names
suite/rollout.test.ts: on PostgreSQL two versions use one database at once under their own names, the expand destroys nothing, retiring the older drops its schema, and the contract quarantines what only it used; suite/rollout.test.ts: the schema's pattern and the primary version are settings, DuckDB's views read, and SQLite's views carry the version's label in their names
suite/presets.test.ts: each of the four presets is a strategy with its features and settings, a name that is not one of them is refused, and every preset has the safety features and idempotency on
suite/presets.test.ts: each of the four presets is a strategy with its features and settings, a name that is not one of them is refused, and every preset has the safety features and idempotency on
suite/presets.test.ts: each of the four presets is a strategy with its features and settings, a name that is not one of them is refused, and every preset has the safety features and idempotency on
suite/presets.test.ts: a project's changes are taken over the preset's setting by setting, and settings for a strategy the preset does not use are refused
suite/presets.test.ts: on three engines autonomous-convergence applies what adds on first access, holds what does not and finds the next access current, and reviewed-convergence applies only the approved text, once
suite/integrations.test.ts: an integration is resolved by the words of its names, and a table or column that is not there, a required column left out and a missing key are errors as values
suite/integrations.test.ts: CSV text is parsed with quotes and read into the target's types, an empty field is null, and a header the contract does not name is refused; suite/integrations.test.ts: a table of another database file is attached for the load and detached, on the engines that can attach, and refused as a value on the one that cannot; an adapter gives rows, fails, or gives a column the contract does not
suite/integrations.test.ts: on three engines each strategy loads as it says, an upsert run twice leaves the rows as after once, a failure rolls back, and the landing is gone
suite/integrations.test.ts: on three engines each strategy loads as it says, an upsert run twice leaves the rows as after once, a failure rolls back, and the landing is gone
suite/integrations.test.ts: duplicate keys, a missing required value, an empty snapshot and a snapshot that would delete most of the target are refused and change nothing
suite/integrations.test.ts: duplicate keys, a missing required value, an empty snapshot and a snapshot that would delete most of the target are refused and change nothing
suite/integrations.test.ts: every load is a row of the ledger with its counts and the hash of what it landed, and an append of rows that have not changed does nothing
suite/integrations.test.ts: on three engines each strategy loads as it says, an upsert run twice leaves the rows as after once, a failure rolls back, and the landing is gone; suite/integrations.test.ts: every load is a row of the ledger with its counts and the hash of what it landed, and an append of rows that have not changed does nothing
suite/integrations.test.ts: lineage is the edges from the source to the landing and the landing to the target, and what reaches a node is found nearest first
suite/integrations.test.ts: every load is a row of the ledger with its counts and the hash of what it landed, and an append of rows that have not changed does nothing
suite/transforms.test.ts: a project is made in the order of what each model reads, with lineage, and a name that is not there, a cycle, a duplicate, a missing key and a test of an ephemeral model are errors as values
suite/transforms.test.ts: a project is made in the order of what each model reads, with lineage, and a name that is not there, a cycle, a duplicate, a missing key and a test of an ephemeral model are errors as values
suite/transforms.test.ts: a project is made in the order of what each model reads, with lineage, and a name that is not there, a cycle, a duplicate, a missing key and a test of an ephemeral model are errors as values
suite/transforms.test.ts: on three engines a view, a table, an ephemeral and an incremental model are made as they say, a table is made again under the views that read it, and each build is in the ledger
suite/transforms.test.ts: a model whose test of severity error finds a row is rolled back, what was published stays, what reads it is blocked, and a warning is reported and does not stop the build; suite/transforms.test.ts: a relationship, a not-null and a test of one's own find the rows that are wrong, by the names of the schema
suite/transforms.test.ts: a model whose test of severity error finds a row is rolled back, what was published stays, what reads it is blocked, and a warning is reported and does not stop the build
suite/transforms.test.ts: on three engines a view, a table, an ephemeral and an incremental model are made as they say, a table is made again under the views that read it, and each build is in the ledger
suite/queries.test.ts: a catalog is made from names by their words, and an unknown name, a duplicate, an undeclared parameter and anything that is not one read-only statement are errors as values
suite/queries.test.ts: a value enters a query only as a literal of its type: another type, a missing value, a null and an undeclared parameter are refused, and what looks like SQL is text
suite/queries.test.ts: a catalog is made from names by their words, and an unknown name, a duplicate, an undeclared parameter and anything that is not one read-only statement are errors as values
suite/target.test.ts: the file is a header, the structure, then rows with tables after the tables they refer to, rows in the order of their key, a fixed number to an INSERT, and the same bytes every time whatever the order the rows were given in; suite/target.test.ts: rows are checked when the file is made: an unknown table or column, a missing required column, a key twice, a column twice and a cycle among tables are errors as values
suite/target.test.ts: the file is a header, the structure, then rows with tables after the tables they refer to, rows in the order of their key, a fixed number to an INSERT, and the same bytes every time whatever the order the rows were given in
suite/target.test.ts: the file is a header, the structure, then rows with tables after the tables they refer to, rows in the order of their key, a fixed number to an INSERT, and the same bytes every time whatever the order the rows were given in
suite/target.test.ts: on three engines a database is made from the build in one transaction, with the rows as the source gives them, and a failure rolls everything back
suite/kinds.test.ts: CSV is read into typed rows in the order of the file, and a bad header, a ragged row, a value of the wrong type and a key twice are errors as values with their lines
suite/kinds.test.ts: the rows are checked against a table by the words of the names: an unknown table or column, a required column the file lacks and an empty required value are errors as values
suite/kinds.test.ts: the module is the same text every time, marked not to be edited, imports as the rows that were read, and the rows go into an ephemeral target as they are
suite/kinds.test.ts: the module is the same text every time, marked not to be edited, imports as the rows that were read, and the rows go into an ephemeral target as they are
suite/osquery-atc.test.ts: the configuration has an entry for each table in the order of their names, whose query selects its columns, written by the dialect, from its table, and it is the same bytes every time; suite/osquery-atc.test.ts: what osquery refuses is an error as a value: another dialect, an unknown table or column, a name, a duplicate, a column called path, no columns, a platform and a path that does not fit its platform
suite/osquery-atc.test.ts: the configuration has an entry for each table in the order of their names, whose query selects its columns, written by the dialect, from its table, and it is the same bytes every time
suite/osquery-atc.test.ts: what osquery refuses is an error as a value: another dialect, an unknown table or column, a name, a duplicate, a column called path, no columns, a platform and a path that does not fit its platform; suite/osquery-atc.test.ts: a column that is written as path, in any case, is refused because osquery adds a path column of its own
suite/osquery-atc.test.ts: what osquery refuses is an error as a value: another dialect, an unknown table or column, a name, a duplicate, a column called path, no columns, a platform and a path that does not fit its platform
suite/modules.test.ts: a project composes the modules it lists into one domain, and a module that is not listed has no table; suite/modules.test.ts: a required module that is not listed, a cycle, two modules with one name, a concept twice, a reference sideways and the errors of the domain are errors as values
suite/modules.test.ts: a required module that is not listed, a cycle, two modules with one name, a concept twice, a reference sideways and the errors of the domain are errors as values
suite/modules.test.ts: withRequired gives the modules wanted and everything they require, in the order of the requirements, and a name no module has is an error as a value
suite/modules.test.ts: every module of the library applies to a subject, one of the six, and a described model carries it; a module that names its own subject keeps it
suite/identity.test.ts: each module names what it requires, a project composes only what it needs and gets no table of the others, and a module whose requirement is not listed is an error as a value
suite/identity.test.ts: each module names what it requires, a project composes only what it needs and gets no table of the others, and a module whose requirement is not listed is an error as a value
suite/identity.test.ts: the whole composition binds for each dialect and loads into each real engine, and on every engine a principal of any of the five kinds has a status and an owner that is not itself, and a tenant has a unique slug and is not its own parent
suite/identity.test.ts: each module names what it requires, a project composes only what it needs and gets no table of the others, and a module whose requirement is not listed is an error as a value
suite/identity.test.ts: the whole composition binds for each dialect and loads into each real engine, and on every engine a principal of any of the five kinds has a status and an owner that is not itself, and a tenant has a unique slug and is not its own parent; suite/identity.test.ts: the identity model's uniques are in the database: one login in a tenant, one name for a group in a tenant, one passkey credential id, one hash for a refresh token, one verified domain, one membership of a user in a tenant
suite/identity.test.ts: no concept of any module holds a secret, a prompt or raw arguments in the clear, every concept that holds a secret is restricted, and an agent's provenance and its calls are kept as pinned versions and hashes; suite/identity.test.ts: the identity model's uniques are in the database: one login in a tenant, one name for a group in a tenant, one passkey credential id, one hash for a refresh token, one verified domain, one membership of a user in a tenant
suite/identity.test.ts: no concept of any module holds a secret, a prompt or raw arguments in the clear, every concept that holds a secret is restricted, and an agent's provenance and its calls are kept as pinned versions and hashes; suite/identity.test.ts: the identity model's uniques are in the database: one login in a tenant, one name for a group in a tenant, one passkey credential id, one hash for a refresh token, one verified domain, one membership of a user in a tenant
suite/identity.test.ts: no concept of any module holds a secret, a prompt or raw arguments in the clear, every concept that holds a secret is restricted, and an agent's provenance and its calls are kept as pinned versions and hashes
suite/identity.test.ts: on three engines invitations grant roles once, domains and policies and the audit chain keep what the model says, and a hash in the chain is unique
suite/identity.test.ts: on three engines invitations grant roles once, domains and policies and the audit chain keep what the model says, and a hash in the chain is unique
suite/identity.test.ts: on three engines invitations grant roles once, domains and policies and the audit chain keep what the model says, and a hash in the chain is unique
suite/identity.test.ts: every concept carries a classification and the requirement it cites, what is personal carries its category, and short-lived data says how long it is kept