Every hold that is in places says what it leaves out. Gathered here by failure, those lines are what each hold does not reach. Where the gap is in a check or a structure, whatever sits on the rungs above it is what holds, where anything does. A rung with nothing aimed at the failure, a rung that cannot hold it, and what is wanted and not built are listed with them. Review after landing and the gate apply to every row, so a blank rung means only that nothing more specific is aimed at the failure.
Tool: Lints for the mechanical rulesleaves out: Nothing checks the naming forms, the styling ladder or whether a feature belongs. Only their mechanical edges are checked, such as the case lints of Rust and the class diagnostics of fuz_css.
Shapeis out of reach: Whether a feature belongs is a judgment about the whole design, and no structure makes that call.
Shape: No quiet path to takeleaves out: The first two hold only where code follows the rule that asks for them, and code outside all three can still catch an error and carry on.
Nothing at the Person and Session
rungs is aimed at it.
Person: Review after landingleaves out: One person reads what many sessions push, and nothing yet lists the commits pushed across the repos in one place.
Wanted: A view of the commits pushed across every repo, so the review has one place to happen.
Session: Writer and reviewer loopleaves out: The loop is for long-running work and not for every change, and its reviewer is another agent.
Tool: Suppressions that expireleaves out: Where no outside reference exists, an expected file regenerated from wrong output passes, and so does a suppression with a plausible reason. The record of twin differences is checked only when the cross-backend suites run, which for the Rust side is on demand.
Nothing at the Person and Shape
rungs is aimed at it.
Tool: Suites that fail on a skipleaves out: Elsewhere a skip may only warn, as when the install suite of fuz finds a program it needs missing.
Shape: One gate definitionleaves out: Most other Rust workspaces list their steps again in CI, and nothing structural stops a commit whose local gate was red.
Nothing at the Person and Session
rungs is aimed at it.
Tool: CI reruns the gateleaves out: A few repos have no CI, or one that runs less than the local gate; the list under the gates table names them.
Shape: Fast toolsleaves out: Rust compile loops stay slow, and the heaviest gates, such as the corpus and conformance runs of tsv, run before a release and not on each push.
Nothing at the Person and Session
rungs is aimed at it.
Tool: Link and drift checksleaves out: Outside tsv, no gate checks the links in a repo's own Markdown files, such as its README and docs. Only Markdown that a site renders is crawled, by that site's build.
Tool: Committed size limitsleaves out: Size is the only axis a gate limits on each change. Speed is graded against a base on demand: tsv fails a row that moves past a committed percentage, and gro asks for a written reason.
Shapeis out of reach: Whether a change is faster is known only by measuring it, so no structure can rule a slow one out.
Tool: The gateleaves out: A few repos have no CI, or one that runs less than the local gate; the list under the gates table names them. A mistake reaches the gate only once someone has given it a mechanical form.
Tool: Busy detection and rebase on pushleaves out: It holds syncs and pushes, not edits: two sessions can still write the same files. It cannot see a session that writes no session file, and it works on Linux alone.
Tool: Deny rules and dry runsleaves out: No gate detects a version change, and a new dependency or package passes nearly every gate: fuz_schema has a test that allows it no runtime dependency, and tsv makes a new crate declare whether it publishes. The deny rules match a command by its prefix, so one spelled another way gets past them. gro's publish and deploy tasks, which the TypeScript libraries release with, run for real unless told otherwise, and so do the release task of fuz_forge, the publish command of fuz and the addon publish script of tsv.
Shape: A push tool that cannotleaves out: Only pushing goes through such a tool. Publishing and deploying have none, and git itself is still on the machine, behind a deny rule.
Nothing at the Session
rung is aimed at it.
Actions nothing refuses
Of the actions kept with a person, these are the ones where no part is refused by a tool or denied by a permission rule. An action left off this list may still have a part that nothing refuses, which its row says.
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.
Change a version or a changelog(written rule): Only a written rule: no gate detects the change.
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.
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.