Skip to content

Claims status

llms.txtlists every page for an agent

Each scenario claim (scenarios/claims/) is a promise the docs make, run against chant’s emulator. A claim runs twice: plain, where it should pass, and broken (BREAK=1), where the claim’s own check should catch the fault it plants; a claim of several parts is caught only when each part catches the fault planted in it. npm run claims runs them; see the comment at the top of scenarios/run.ts.

The record was last written at 2026-11-03 01:56 UTC, at commit 821d93b. A row run in an earlier run keeps that run’s commit and date.

A row marked “not recorded” has not been run into the record. CI does not run the forge claim, which needs a local Forgejo.

Each docs page names the claims that prove it, and npm run check fails when a page that is not a draft names one that does not pass plain and get caught broken here. The last column lists those pages.

Claim Dialect What it says Plain Broken Commit Date Pages
migrations ClickHouse yodel new writes the next migration offline, with no dev database, and it applies; on Postgres, functions, procedures and triggers too, which lint checks; yodel new –sql writes a migration a person writes; its reference rows and a column declared in src/ too are recorded from migration.sql, replay to the schema it records, apply behind the gate, and the next yodel new diffs from it; yodel lint –replay replays the migrations into a fresh database and each gives the schema it recorded; offline, yodel lint fails a migrations directory with a fork (exit 1), naming both migrations; a checkpoint replays alone to its recorded schema, and a fresh environment starts from it; yodel revert undoes the newest migration behind the gate, with a hand-written step for its data step, back to its parent’s recorded schema, and refuses a checkpoint or a migration before one; yodel test runs a project’s tests on databases replayed from the migrations, a seed meeting the backfill after it, fails a case whose assertion does not hold, and refuses an environment with a history; on Postgres, a unique index over rows with duplicates is refused before the gate by its generated pre-check (exit 1, naming the statement and the count), and yodel lint flags it as data-dependent; a project’s own column rule from chant.config.ts lint.policies fails yodel lint on the migration that breaks it, and a yodel:allow line silences it; yodel check runs a goose directory’s migrations into a throwaway schema and fails the one a pull request adds when it drops a column, on that file’s line; a yodel:allow line in the file silences it; a migration merged late, before one already applied, is refused unless –allow-out-of-order, and never skipped pass caught 821d93b 2026-11-03 01:56 UTC adoption, from-other-tools, getting-started, lint, migrations, schema, workflows
migrations Postgres yodel new writes the next migration offline, with no dev database, and it applies; on Postgres, functions, procedures and triggers too, which lint checks; yodel new –sql writes a migration a person writes; its reference rows and a column declared in src/ too are recorded from migration.sql, replay to the schema it records, apply behind the gate, and the next yodel new diffs from it; yodel lint –replay replays the migrations into a fresh database and each gives the schema it recorded; offline, yodel lint fails a migrations directory with a fork (exit 1), naming both migrations; a checkpoint replays alone to its recorded schema, and a fresh environment starts from it; yodel revert undoes the newest migration behind the gate, with a hand-written step for its data step, back to its parent’s recorded schema, and refuses a checkpoint or a migration before one; yodel test runs a project’s tests on databases replayed from the migrations, a seed meeting the backfill after it, fails a case whose assertion does not hold, and refuses an environment with a history; on Postgres, a unique index over rows with duplicates is refused before the gate by its generated pre-check (exit 1, naming the statement and the count), and yodel lint flags it as data-dependent; a project’s own column rule from chant.config.ts lint.policies fails yodel lint on the migration that breaks it, and a yodel:allow line silences it; yodel check runs a goose directory’s migrations into a throwaway schema and fails the one a pull request adds when it drops a column, on that file’s line; a yodel:allow line in the file silences it; a migration merged late, before one already applied, is refused unless –allow-out-of-order, and never skipped pass caught 821d93b 2026-11-03 01:56 UTC adoption, from-other-tools, getting-started, lint, migrations, schema, workflows
declarative ClickHouse the declarative path: yodel plan shows the change against the live server and yodel apply makes it behind the plan-bound gate, for src/ declarations (on Postgres, functions, procedures and triggers, and access control: a role, a policy and grants, with a grant made by hand revoked; on ClickHouse, a dictionary, a function, and access control: a role, a user, a row policy and grants, with a grant made by hand revoked) and for an ORM’s exported DDL; a pull request on that path gets lint over the planned changes and the plan comment with them, and a policy rule at the base commit that denies the plan refuses yodel apply before the gate; yodel drift reports a declared object changed out of band, naming the property, a column added to it by hand, and one dropped; on the versioned path it compares with the newest applied migration’s recorded schema, so a pending migration is not drift; yodel init –from adopts a live database without touching it, and yodel plan then shows no change; on Postgres its policies, row-level security and grants too, on ClickHouse its dictionaries, functions, roles, users, row policies and grants; it refuses a database holding an object of a kind it cannot declare, naming it; yodel init –baseline records the baseline, behind the gate, in a second environment that holds the same schema, and refuses one that differs pass caught 821d93b 2026-11-03 01:56 UTC access, adoption, configuration, drift, from-other-tools, getting-started, orm, schema, workflows
declarative Postgres the declarative path: yodel plan shows the change against the live server and yodel apply makes it behind the plan-bound gate, for src/ declarations (on Postgres, functions, procedures and triggers, and access control: a role, a policy and grants, with a grant made by hand revoked; on ClickHouse, a dictionary, a function, and access control: a role, a user, a row policy and grants, with a grant made by hand revoked) and for an ORM’s exported DDL; a pull request on that path gets lint over the planned changes and the plan comment with them, and a policy rule at the base commit that denies the plan refuses yodel apply before the gate; yodel drift reports a declared object changed out of band, naming the property, a column added to it by hand, and one dropped; on the versioned path it compares with the newest applied migration’s recorded schema, so a pending migration is not drift; yodel init –from adopts a live database without touching it, and yodel plan then shows no change; on Postgres its policies, row-level security and grants too, on ClickHouse its dictionaries, functions, roles, users, row policies and grants; it refuses a database holding an object of a kind it cannot declare, naming it; yodel init –baseline records the baseline, behind the gate, in a second environment that holds the same schema, and refuses one that differs pass caught 821d93b 2026-11-03 01:56 UTC access, adoption, configuration, drift, from-other-tools, getting-started, orm, schema, workflows
approval ClickHouse a pending migration applies only after chant approve of its plan digest, and the history records that digest; yodel plan –part writes the plan as a chant change-set part under that digest; a failing pre-migration check refuses it, and so does a policy rule, read at the base commit, unless an override is recorded for that digest, for a yodel revert as for an apply; the audit log derived from the history and the ledger accounts for every approval and apply, and names one removed; a reader and a writer that are one user are refused, and the reader, its password a minted token, cannot write; the pull request comment lists the pending migrations with each statement’s class, and the digest the gate asks for pass caught 821d93b 2026-11-03 01:56 UTC approval, audit, configuration, getting-started, kubernetes, migrations, terraform, workflows
approval Postgres a pending migration applies only after chant approve of its plan digest, and the history records that digest; yodel plan –part writes the plan as a chant change-set part under that digest; a failing pre-migration check refuses it, and so does a policy rule, read at the base commit, unless an override is recorded for that digest, for a yodel revert as for an apply; the audit log derived from the history and the ledger accounts for every approval and apply, and names one removed; a reader and a writer that are one user are refused, and the reader, its password a minted token, cannot write; the pull request comment lists the pending migrations with each statement’s class, and the digest the gate asks for pass caught 821d93b 2026-11-03 01:56 UTC approval, audit, configuration, getting-started, kubernetes, migrations, terraform, workflows
resume ClickHouse an interrupted apply resumes where it stopped: a backfill step written as yodel’s form (table, key, batch size, SQL) from its receipts, running each batch once, and a failed statement at that statement, never resending one that ran; Postgres: a column rename runs as a PostgresMigrationOp step (expand, backfill, switch, contract) and keeps every value; a step that fails part way keeps its work and resumes from its receipts; Postgres: a statement blocked behind another session’s lock times out at lock_timeout and is retried until it succeeds; Postgres and ClickHouse with Keeper: two applies at once never send a statement twice, the second waits naming the holder, and –stand-down steps aside for a newer commit pass caught 821d93b 2026-11-03 01:56 UTC from-other-tools, migrations, steps
resume Postgres an interrupted apply resumes where it stopped: a backfill step written as yodel’s form (table, key, batch size, SQL) from its receipts, running each batch once, and a failed statement at that statement, never resending one that ran; Postgres: a column rename runs as a PostgresMigrationOp step (expand, backfill, switch, contract) and keeps every value; a step that fails part way keeps its work and resumes from its receipts; Postgres: a statement blocked behind another session’s lock times out at lock_timeout and is retried until it succeeds; Postgres and ClickHouse with Keeper: two applies at once never send a statement twice, the second waits naming the holder, and –stand-down steps aside for a newer commit pass caught 821d93b 2026-11-03 01:56 UTC from-other-tools, migrations, steps
clickhouse ClickHouse ClickHouse: a sort-key change is a ClickHouseRebuildOp step inside the migration, never an ALTER or a drop; approved, it runs and keeps every row; yodel cleanup drops the old table it kept only after its retention date, behind an approval on a gate of its own; ClickHouse: one migrations directory applies to a single node and to a Replicated database, and one to a sharded cluster with drift read there, each rendered for its topology pass caught 821d93b 2026-11-03 01:56 UTC configuration, steps, topology
waves ClickHouse the apply pipeline runs one wave per environment, each behind its gate policy, approved with yodel approve; a wave applies only what the wave before applied, yodel report finds each wave’s approvals, a tenant set’s migrations reach every tenant behind one gate, and the steps around apply run once under the lock and are recorded pass caught 821d93b 2026-11-03 01:56 UTC approval, workflows
waves Postgres the apply pipeline runs one wave per environment, each behind its gate policy, approved with yodel approve; a wave applies only what the wave before applied, yodel report finds each wave’s approvals, a tenant set’s migrations reach every tenant behind one gate, and the steps around apply run once under the lock and are recorded pass caught 821d93b 2026-11-03 01:56 UTC approval, workflows
forge ClickHouse a project from the starter template, on Forgejo: apply only after approval, lint with replay and the plan comment on a pull request, and the approved change applied on merge; a sealed wave applies only on an approval sealed by a signer listed at the base, and a pr-review wave on the review of a writer other than the author; a pull request job cannot write, a forked migration fails lint and is annotated, a stale or hand-edited pipeline fails yodel ci –check, a project with ci.apply: false and no apply pipeline passes it and gets the plan comment, the CI image pinned by digest runs a pull request’s jobs, a command token source mints the reader’s password, and the drift watch keeps one tracking issue pass caught 868ff97 2026-10-10 21:57 UTC chant-ci, forges, lint-and-plan

A claim can also cite one row of a product’s scenario on the shared e2e harness (scenarios/product-proofs.json). A row names the repo, the scenario, the claim, the product commit, the date and the yodel version it ran, and counts only when that version is the one the claims are about, 0.12.1 here. A row at another version is listed and marked not counted. A cited row never replaces the claim’s own run above.

No product scenario row is cited yet.

These harness scenarios have no recorded row yet. Each is listed here as pending until its row is recorded and cited above.

Claim Repo Scenario To record
approval INTENTIUS/sql-yodeler sy-approval-clickhouse the digest-bound gate, the gate read at the base, an override for a denied drop, and the audit, in CI (ClickHouse template)
approval INTENTIUS/sql-yodeler sy-approval-postgres the digest-bound gate, the gate read at the base, an override for a denied drop, and the audit, in CI (Postgres template)
waves INTENTIUS/sql-yodeler sy-waves-clickhouse dev and prod applied as two waves on a Forgejo runner, each behind its own gate, each approved with yodel approve (ClickHouse template)
waves INTENTIUS/sql-yodeler sy-waves-postgres dev and prod applied as two waves on a Forgejo runner, each behind its own gate, each approved with yodel approve (Postgres template)
forge INTENTIUS/sql-yodeler sy-forge-clickhouse lint with the replay, the plan comment and the approved apply on Forgejo, and lint failing a forked migration (ClickHouse template)
forge INTENTIUS/sql-yodeler sy-forge-postgres lint with the replay, the plan comment and the approved apply on Forgejo, and lint failing a forked migration (Postgres template)
forge INTENTIUS/sql-yodeler sy-new-clickhouse /yodel new pushes the migration to the pull request on Forgejo, and a change outside migrations/ is refused (ClickHouse template)
forge INTENTIUS/sql-yodeler sy-new-postgres /yodel new pushes the migration to the pull request on Forgejo, and a change outside migrations/ is refused (Postgres template)
forge INTENTIUS/sql-yodeler sy-rebase-clickhouse /yodel rebase on a fork two merged branches make, refused on Forgejo when main moves while it runs (ClickHouse template)
forge INTENTIUS/sql-yodeler sy-rebase-postgres /yodel rebase on a fork two merged branches make, refused on Forgejo when main moves while it runs (Postgres template)

SQL Yodeler