Estate views
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/terragucci/guides/estate-views/.
Using the estate over MCP (`terragucci mcp`, its `waiting`, `estate` and `report` tools), tell me what is waiting for an approval now and what drifted this week, with the project and roots of each.
Read only. Never apply, approve (a pull request review or `terragucci approve`), override a policy denial (`terragucci override`), use `--mode apply`, or merge; never touch `.chant/allowed_signers` or `chant/lifecycle`.Result
Section titled “Result”The view that answers your question. Each is built from files in your own reports bucket: static pages, dashboards in your own observability stack, or queries, with nothing to host or sign in to.
Questions and views
Section titled “Questions and views”| Question | Look at |
|---|---|
| What is applying now, and how far is it? | with choudoufu, each resource done, in flight or waiting in the run view’s column and the estate page’s applying row (Watch a choudoufu wave apply); for any binary, each wave’s state in the run view |
| What is waiting for me? | the estate page’s waiting waves, the waiting tool of terragucci mcp, or terragucci approve --dry-run in the repo; the Rollouts and waves dashboard and the TerragucciWaveWaiting alert for how long |
| Why did this wave refuse? | its column in the run view and its wave report, which names the roots whose plans moved or the rule that denied one; the TerragucciWaveRefused alert |
| What changed on this resource, and who approved it? | the estate page’s Resources section and its change history, and with choudoufu each record’s past versions; terragucci query over the history table |
| Was a state written outside the pipeline? | the unrecorded-write entries of the audit trail, with the writer when a CloudTrail log names one, the estate page’s state versions for each root, which mark them, and terragucci notify unrecorded for a chat message |
| Which roots read this state? | the estate page’s dependency graph, between projects too, and its Cross-state edges, each stale or current; the edges table in terragucci query |
| How often do we deploy, and how often does it fail? | the estate page’s Delivery section and dora.json, and the Estate dashboard |
| Is drift checked? | the estate page’s latest drift check per project, the Drift dashboard, and the TerragucciDriftOld and TerragucciDriftStopped alerts |
| Which roots are slow, and where does a run spend its time? | the Runs and Rollouts and waves dashboards with each run’s trace, and the run view’s timeline |
| What will this pull request change, down to each resource? | the plan note and its report |
| Which resources in one repo drifted or will change, as a graph? | behold, on your machine or published beside the estate page |
The estate page comes from a scheduled job in your control repo; the run view and the reports from the pipeline’s own jobs; the dashboards from dashboards. The reports bucket lists where each file lives.
terragucciHelp setting it up: Intentius
These docs count page views and clicks with PostHog. They set no cookies, store nothing in your browser, and send nothing when your browser asks not to be tracked.