What a team knows, written where the work is — and, deliberately, where the
agents read.
Why it is not a wiki in another tab
An agent about to touch this repository reads these. How we name branches,
Writing migrations, Working with the provider are not documentation about
the product; they are the instructions a member is expected to have.
Kept here rather than in a separate tool for the same reason the diff is:
something a person has to go somewhere else to find is something that gets out
of date, and an agent cannot go anywhere else at all.
Links between pages
[[decline-taxonomy]] in the body is a link. Pages point at each other, and a
page knows what points at it — so a convention that three runbooks depend on
says so on itself.
A link to a page that does not exist yet is not an error. It is a page
somebody has decided is worth writing, and the ones nobody wrote are listed as
such.
The graph
The same pages drawn as what they point at, with the count above them:
Three kinds of dot, and the two that matter are the ones that are not just a
page. Carried by a card or an agent is a page something is actually
reading — How we name branches, Working with the provider, Checkout
principles. Linked, not written is the dashed outline: Retry policy is
referred to by a page somebody wrote and does not exist yet.
4 joined to nothing is the honest half of the picture. A page nobody links
to and nothing carries is a page that is not part of how this team works,
whatever it says inside.
Ended pages
Deleting a page ends it rather than removing it, and ended pages sit at the
bottom of the tree with Restore beside them.
The same rule as everywhere else here: a decision somebody made and later
reversed is part of how the team got where it is, and a wiki that forgets it
is a wiki that will have the same argument again.
Pages can be written from the API too, which is the case worth automating: a
convention that already lives in a linter or a generator should not be
transcribed by hand into the place the agents look.
