Skip to content
beholdDocsDemo

behold on a SQL Yodeler project

llms.txtlists every page for an agent
Optional: hand this page to your coding agentThe steps work by hand too.
Show the whole prompt
Read https://intentius.io/behold/for/sql-yodeler/.
Serve this SQL Yodeler project with `npx @intentius/behold serve .` and tell me the URL.
List the environments the Releases tab shows.
For each gate that waits, show me the `yodel approve` line to run myself.
Never deploy with the Deploy button, `POST /api/apply` or `POST /api/ci/dispatch`. Gate approvals stay mine as well (`/api/ops/:name/signal/:gate`, `/api/workspace/gates/approve`, `/api/operator/approve/:op/:gate`). Op runs (`/api/ops/:name/run`) and rollbacks (`/api/rollback`) are mine too. Leave `--auto-sync` off, and keep a `behold preview` or `--public` serve read-only.

Draw the schema a SQL Yodeler project declares. What each environment holds comes from the files yodel wrote and the chant/lifecycle branch.

Works

  • Tables and indexes as cards named by kind, joined by each REFERENCES
  • The Pipeline tab: each wave's gate and the plan digest it is bound to
  • Who approved each gate, and how
  • The Releases tab: each environment's newest release per component
  • Drift files as dated corner tags on the cards they name

Needs

  • The project's checkout, with chant/lifecycle on its origin
  • Report and drift JSON from yodel for the SQL Yodeler tab

First step

Terminal window
yodel report --json > out/report.json
yodel drift prod --json > out/drift-prod.json
npx @intentius/behold serve . --yodel-report out/

Look at a SQL Yodeler project

Proof

The example projects and end-to-end scripts in the behold repository for this room. The build checks that each one is there.

PathWhere
sql-yodeler-fke2e/fixtures/sql-yodeler-fk

Then read

Tasks
Look at a SQL Yodeler projectReport and drift
Background
The pipelineReleases
Reference
Policy denialsSQL Yodeler docs

behold