Running behold for a platform team
llms.txtlists every page for an agent
Show the whole prompt
Read https://intentius.io/behold/for/platform/.
Serve this estate with `npx @intentius/behold serve . --env <env> --poll 30` and tell me the URL.
List the nodes it reports as unobserved.
Name the Ops it offers so I can decide on them.
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.Give a platform team one graph per estate across substrates. Deploys go through the Ops and forges the team already runs.
Works
- Each substrate in the graph keeps its own meaning of deployed
- An environment designated to a forge deploys through that forge's workflow and your
gh - Auto-sync routes drift to the Op that owns its substrate
behold exportwrites a static snapshot any host serves
Needs
- Read roles for every substrate the estate spans
- Write roles only where Deploy runs from behold
First step
npx @intentius/behold serve . --env prod --poll 30Proof
The example projects and end-to-end scripts in the behold repository for this room. The build checks that each one is there.
| Path | Where |
|---|---|
example-flux-estate | example-flux-estate |
example-argo-estate | example-argo-estate |
ci-executor-github-e2e.sh | e2e/ci-executor-github-e2e.sh |