Rule
Keep two ledgers with different jobs. Beads records the work, acceptance, decisions, and evidence. A reviewed LLM wiki records the smaller set of explanations and patterns worth reusing. Link them so every durable claim has a trail back to the work that tested it.
The model does not learn because a session ended. An LLM can draft a wiki page, propose links, and flag stale material. Review decides what the page may claim. A later task links the page when it is relevant.
The Two Ledgers
| Surface | What it records | Question it answers |
|---|---|---|
| Beads | Intent, acceptance, dependencies, status, decisions, and evidence | What are we doing, and what happened? |
| Reviewed LLM wiki | Source-linked explanations, patterns, decisions, and maintenance notes | What should a future session know, and where did it come from? |
An issue tracker alone scatters reusable knowledge across closed work. A wiki alone can become a polished story detached from the evidence. The link between them makes the record inspectable.
Put It to Work
- Start with a bead or another durable intent source that names the work and acceptance.
- Run the implementation and record the result next to the original intent.
- Promote a lesson only when it generalizes beyond that task.
- Make the wiki page cite the bead, commit, verdict, or other source that supports it.
- Link the relevant page from a later bead before implementation starts.
- Open repair work when the page proves stale or wrong.
Most sessions should not create a wiki page. Good candidates prevent a repeated mistake, preserve an architectural decision, or document a procedure another operator must run. Transcript dumps, status updates, and unsupported hunches stay out.
Where AgentOps Fits
AgentOps runs the binding work loop: Plan fixes the intent, Implement builds one bounded candidate, and a fresh Validate context judges the same acceptance and evidence. It writes a durable verdict and stops.
The wiki is optional later work. It may inform a future plan, but it cannot change the verdict for the current candidate. This boundary keeps reusable knowledge useful without turning it into a second source of truth.
Failure Signal
- A wiki page has no source or review date.
- Every session creates another page, including one-off status notes.
- Closed beads contain repeated lessons that nobody can find.
- A future task loads the whole wiki instead of linking the small relevant slice.
- A stale page remains authoritative because there is no repair path.
Done Looks Like
A later bead links one reviewed page, that page cites the work that supports it, and a named repair path exists if the guidance stops being true.