Skip to content
beholdDocsDemo

Security review

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/security/.
Run `npx @intentius/behold doctor . --json` in this project and summarise it.
List the Ops this project commits so I can review which ones behold would offer.
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.

Review what behold reads and where each of its writes runs.

Works

  • Every view is a read and needs read roles only
  • Each write starts a committed Op or chant's local executor, on the credentials behold was started with
  • A terragucci or SQL Yodeler repo refuses every write behold could start
  • One delegated write runs at a time, and auto-sync leaves every gate for a person
  • An export cuts each absolute path down to its directory name

Needs

  • The credentials of the shell that starts behold, which set what Deploy can change

First step

Terminal window
npx @intentius/behold doctor . --json

Read-only core, delegated writes

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
AGENTS.mdAGENTS.md
ci-executor-github-e2e.she2e/ci-executor-github-e2e.sh

Then read

Tasks
Acting on itExport a snapshot
Background
Read-only core, delegated writesGates
Reference
The act loopbehold doctor

behold