The argument

When the worker is an agent.

A delivery process is a set of assumptions about who updates the tracker, who looks, and who remembers. An agent breaks the ones that depended on a person being in the loop.

Done is the author's word.

In a people-process the author moves their own ticket, and done is their say-so. An agent that grades its own work will pass it.

The loop →

One person edits, and the tracker is a place people look.

Parallel agents collide on files, not on tickets. A claim nobody frees sits there after the agent has gone.

The tracker →

The spec is a document someone remembers to read.

An agent fills a gap in intent. If anyone can mark the document approved, a quiet edit moves the target.

Specs →

The team remembers, or a wiki does.

The next agent inherits the last agent's confident note, including a wrong one. A folder of notes answers with the nearest page.

Memory →

People already know the tree.

An agent re-reads it, or trusts a map that has gone quiet. A diagram nobody updates becomes a confident lie.

Code graph →

A written rule is followed because it is written.

A rule in a document and a rule the server refuses look the same until one of them is ignored.

Rules →

A step that did not run is not a pass.

That is the line under the six. Unknown, unmeasured, stale, and never-reported are states of their own. The long version of how a green check hid a rule that had never fired is the bug that started it. The gates are on the pipeline page. The principles under the six are how it's built.

What's new

Every entry is work that merged. The full history is on GitHub.