-
Notifications
You must be signed in to change notification settings - Fork 4
Corrections
Everything this repository has published and had to fix, with the date and the cause.
Being wrong in public is a cost of publishing. Hiding it is a larger one.
A page that quietly changes a number teaches its readers nothing. A page that says what it used to claim, why that was wrong, and how it was caught teaches them how to read everything else here.
Nothing on this page was found by a reader. All of it was found by checking, which is the argument for checking.
Was: the wiki's spine listed nine frameworks. Five of them, Agent Patterns, the Seven-Layer Stack, the Agent Factory Maturity Model, the Seniority Ladder and the Three Drifts, were named and defined nowhere. A reader was expected to already know them.
Now: every name on the spine resolves to a definition, either on that page or on its own.
Cause: the spine was written as an index of work in progress and never revisited once the work stopped progressing.
Was: the front page of the wiki listed five tools. The repository README and the Published Tools page both listed seven. The site contradicted itself on the first page a reader meets.
Now: seven, and Published Tools states what "seven" counts, because the
repository holds five files in tools/ and seven in cheatsheets/ and
nothing said which were being counted.
Cause: two tools were added and only one of the three places that count them was updated.
Was: the README described Grounding as Layer 2 of the seven-layer stack. In the stack's own ordering Grounding is fifth of seven.
Now: the number is gone. "Grounding is the developed layer" is true, checkable, and does not depend on a numbering nobody had ratified.
Cause: the claim was written before the stack was written down.
Was: tools/agent-card.md shipped seven pattern values. Three patterns
with the highest governance weight, Supervisor, Workflow and Guardian,
were absent from a governance artifact. Three of the seven values it did
ship, classification, reasoning and research, are capabilities an agent
has rather than shapes an agent is.
Now: the card ships the eight defined agent patterns,
and the three capability values moved to a separate Capabilities field.
This is a breaking change to a published tool. Anyone holding the earlier card will find their pattern list differs.
Was: resources/community-repos.md contained a worked example reading
git clone https://github.com/YOUR-USERNAME/deepeval. It had been
published, unfilled.
Now: the real path. Six other links in resources/ had rotted at the
same time: two repositories had moved owner, one demo repository was gone,
two video channels no longer resolved, and one vendor documentation deep
link had moved.
Cause: nobody had ever run a link check. All 122 links in resources/
were checked on 2026-08-24; seven did not resolve. See the reading
list.
Was: the README's spine table named Four Modes after that framework had been split into two, because it had been two frameworks sharing one name.
Now: Application Modes, which is what the wiki had already been saying. The repository and its own wiki disagreed in the one place a reader compares them.
Was: working material behind this repository stated the three proofs as Technology, Credibility and Value, and a second variant used Concept, Value and Scale.
Now: Technology, Value and Competence, which is the definition in use and the one attested across every other source. The difference is substantive: credibility asks whether experts trust it, competence asks whether this organisation can operate and remediate it at 2am.
Cause: a framework restated in each place it is used, with no place that is authoritative, drifts in every copy. See the glossary, which now carries the single definition.
Six of the seven are the same failure. A fact was written down in more than one place, one copy changed, and nothing checked the others.
The fix that generalises: link to a definition rather than restating it. A quotation is a copy, and copies drift. Where a restatement is unavoidable, the page that owns the definition is named so the copy can be found later.
The fix that does not generalise but works: check the checkable things on a cadence. Link rot, counts, and cross-references between a repository and its wiki are all machine-checkable, and none of them were being checked.
Reviewed 2026-08. How the evidence here is judged · What is not verified · Back to Home
The thinking
Operating model
Frameworks
Governance
Playbooks
Value and people
Reference
In the repository
The courses
Reviewed 2026-08.