Record fleet-diff as shipped and correct its contract in the process brainstorm #44

Open

allod-agent wants to merge 1 commit from agent/fleet-diff-shipped into master

allod-agent commented

2026-09-04 01:05:05 +01:00

Member

Corrects one paragraph in a brainstorm that the shipped tool has overtaken.

No machine changes and no agent behaviour changes — this repo is Markdown only. What changes is that a reader of the development-process brainstorm is no longer told to build a tool that exists, with a contract it does not have. What stays identical: the proposal itself, which is still unadopted, and every other section of the document. What proves it: one paragraph diff, no other file touched. If it is wrong, revert the commit; nothing depends on it.

Why this and not an archive

README.md says a plan moves to archive/ once implemented or superseded. That is the wrong move here. The document is a project-direction proposal for a land-inert and gate-activation development process, and that process is not adopted — memory's git-workflow.md has no such section. Only the tools paragraph is overtaken, so only the tools paragraph changes.

What was wrong

The paragraph specified "non-zero exit when anything changes so it composes with expectations". The tool that shipped in allod/tools#136 deliberately does the opposite: an expectation is declared with --expect or --expect-none, a mismatch fails in both directions, and a run with no expectation is report-only and exits 0, because a run that asserts nothing should not gate anything. That reasoning is recorded on the tool's own issue, which supersedes this line on purpose.

Two smaller staleness items in the same paragraph: overrides now take a revision rather than a URL, since the checkout's lock already records which repository each input came from; and the sizing estimate ("roughly the size of flake-status, one PR, R2, one review pass") described work that has since happened, so it is dropped rather than left reading as outstanding.

The paragraph now says plainly that the section is a record of what was proposed rather than work outstanding, and points at flake/README.md in allod/tools as the reference.

Risk

R0. Documentation in a planning repo, one paragraph, no consumer.

Validation

git diff --stat shows one file and five inserted lines against one deleted. No other file in the repo mentions fleet-diff — checked with a repo-wide grep before editing, which is also how this paragraph was found.

Deliberately not recorded here: the limit that a fleet diff cannot distinguish a real change from a store-path move for an input whose path is embedded in a machine's configuration. That finding belongs with its cause, which is allod/archetypes#21 and the allod-tools interpolation beside it, not with the document that observes it.

Corrects one paragraph in a brainstorm that the shipped tool has overtaken. No machine changes and no agent behaviour changes — this repo is Markdown only. What changes is that a reader of the development-process brainstorm is no longer told to build a tool that exists, with a contract it does not have. What stays identical: the proposal itself, which is still unadopted, and every other section of the document. What proves it: one paragraph diff, no other file touched. If it is wrong, revert the commit; nothing depends on it. ## Why this and not an archive `README.md` says a plan moves to `archive/` once implemented or superseded. That is the wrong move here. The document is a project-direction proposal for a land-inert and gate-activation development process, and that process is not adopted — `memory`'s `git-workflow.md` has no such section. Only the tools paragraph is overtaken, so only the tools paragraph changes. ## What was wrong The paragraph specified "non-zero exit when anything changes so it composes with expectations". The tool that shipped in allod/tools#136 deliberately does the opposite: an expectation is declared with `--expect` or `--expect-none`, a mismatch fails in both directions, and a run with no expectation is report-only and exits 0, because a run that asserts nothing should not gate anything. That reasoning is recorded on the tool's own issue, which supersedes this line on purpose. Two smaller staleness items in the same paragraph: overrides now take a revision rather than a URL, since the checkout's lock already records which repository each input came from; and the sizing estimate ("roughly the size of `flake-status`, one PR, R2, one review pass") described work that has since happened, so it is dropped rather than left reading as outstanding. The paragraph now says plainly that the section is a record of what was proposed rather than work outstanding, and points at `flake/README.md` in `allod/tools` as the reference. ## Risk R0. Documentation in a planning repo, one paragraph, no consumer. ## Validation `git diff --stat` shows one file and five inserted lines against one deleted. No other file in the repo mentions `fleet-diff` — checked with a repo-wide grep before editing, which is also how this paragraph was found. Deliberately not recorded here: the limit that a fleet diff cannot distinguish a real change from a store-path move for an input whose path is embedded in a machine's configuration. That finding belongs with its cause, which is allod/archetypes#21 and the `allod-tools` interpolation beside it, not with the document that observes it.

allod-agent added 1 commit

2026-09-04 01:05:05 +01:00

Record fleet-diff as shipped and correct its contract a5423c15d5

The tools section proposed a non-zero exit whenever any machine changed.
The tool that shipped asserts against a declared expectation instead, and
a run with no expectation is report-only and exits 0. Left uncorrected the
paragraph reads as outstanding work with a contract the tool does not have.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin agent/fleet-diff-shipped:agent/fleet-diff-shipped

git switch agent/fleet-diff-shipped

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master

git merge --no-ff agent/fleet-diff-shipped

git switch agent/fleet-diff-shipped

git rebase master

git switch master

git merge --ff-only agent/fleet-diff-shipped

git switch agent/fleet-diff-shipped

git rebase master

git switch master

git merge --no-ff agent/fleet-diff-shipped

git switch master

git merge --squash agent/fleet-diff-shipped