Skip to content
terragucciDocs

One note for fifteen plans

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/tutorial/one-note/.
In the terragucci clone with the example booted, run the `just example` commands on the page. Summarize what the plan note says about the twelve roots, the outlier and any destroy.
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`.

Every queue in every service should wait 60 seconds before retrying a job. That is one line in modules/service, and twelve roots call the module.

$ just example change module-bump
[example] pushed change/module-bump at ea6d7680
[example] run 6 for ea6d7680 (pull_request): success (http://localhost:3300/terragucci-admin/example/actions/runs/6/jobs/1/attempt/1)
[example] run 7 for ea6d7680 (push): success (http://localhost:3300/terragucci-admin/example/actions/runs/7/jobs/0/attempt/1)

  Pull request  http://localhost:3300/terragucci-admin/example/pulls/3 (the plan note is in its conversation)
  Plan          http://localhost:3300/terragucci-admin/example/actions/runs/6/jobs/1/attempt/1 (success)
  Check         http://localhost:3300/terragucci-admin/example/actions/runs/7/jobs/0/attempt/1 (success)

Open the pull request link it printed, on Forgejo at localhost:3300; the plan note is the comment in the conversation.

terragucci plans only the twelve service roots the change reaches and posts one note. Eleven roots take the identical change and appear as one group. Prod payments sits apart, because its dead-letter queue changes too.

The plan note on the module change's pull request: 12 roots in 2 groups, the waves table, eleven roots in one group with one diff, and prod payments on its own with its dead-letter queueThe plan note on the module change's pull request: 12 roots in 2 groups, the waves table, eleven roots in one group with one diff, and prod payments on its own with its dead-letter queue

GitHub and GitLab get the same single comment, here for a change to one root:

The plan note on a GitHub pull request for a change to one root: one group, its waves table with the set digest, and the change to the jobs queueThe plan note on a GitHub pull request for a change to one root: one group, its waves table with the set digest, and the change to the jobs queue

The note links to the full report. Its links start with http://forgejo:3000, which your browser cannot reach; open them at http://localhost:3300 instead. The report opens on what differs and folds the eleven identical plans into one.

Next, try just example change replace and just example change destroy. Each is named on its own, never folded into a group.

Tutorial step 3 of 11.

terragucci

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.