Actions kept with a person
These are the actions the stack keeps with the maintainer. Each row lists every mechanism that holds some part of the action, hardest to get past first, and says which part.
The holds whose instances this table lists: Deny rules and dry runs (An unattended session does something irreversible); A push tool that cannot (An unattended session does something irreversible)
A written rule and nothing else holds 3 of the 9.
- Tool refuses The tool an agent uses will not do it.
- Permission rule The agent harness denies the command, matched by its prefix.
- Dry run by default The command changes nothing until it is given an explicit flag.
- Written rule An instruction the agent is expected to follow.
| Action | Held by | How | Source |
|---|---|---|---|
| Force-push or rewrite the main branch | Tool refuses Permission rule | The push tool only fast-forwards, and raw pushes are denied | push gateway |
| Push a tag, which starts a release in CI for tsv and gro | Tool refuses Permission rule Dry run by default | The push tool never sends a tag, and raw pushes are denied. The release script of tsv pushes its own tag, and changes nothing without an explicit flag | push gateway |
| Create a remote branch | Tool refuses Permission rule | The push tool refuses to create one from an agent's shell, and raw pushes are denied | new branches |
| Publish a package | Permission rule Dry run by default Written rule | The harness denies the publish commands, in settings that are not public. The release scripts of tsv, pglet and blake3 change nothing without an explicit flag, which a session could pass. The publish task of gro and the release task of fuz_forge have no such default | release task |
| Deploy a site or a server | Permission rule Dry run by default Written rule | The harness denies the site deploy command, in settings that are not public, and the deploy task of gro has no dry default. A server deploy through zap changes nothing without an explicit flag and runs only a plan it has already previewed, which a session can do itself, so there the written rule is what holds | reviewed plans |
| Delete files or data | Dry run by default | No public rule keeps deletion with the maintainer. In the stack's own Rust tools a new command that is hard to undo is a dry run until it is given an explicit flag | Rust rules |
| Change a version or a changelog | Written rule | Only a written rule: no gate detects the change | shared rules |
| Add or upgrade a dependency | Written rule | Only a written rule, with an allowlist to choose from. fuz_schema alone has a test that fails on a runtime dependency | shared rules |
| Create a package or a crate | Written rule | Only a written rule: the release audit checks the crate graph, not new members, and tsv asks only that a new crate declare whether it publishes | shared rules |