ce:compound

Trevin Chow's 31 March 2026 notes on Compound Engineering v2.60.0 record the change that defines ce:compound today: the skill adopted a schema per track, bug versus knowledge, and gained a discoverability check. The split rests on a claim stated bluntly in Kieran Klaassen's Thinkroom agent guide, that a system remembering only bugs forgets the essential. The bug-track holds what broke; the knowledge-track holds what was decided or discovered.

ce:compound sits at the capture end of the Compounding Knowledge Lifecycle, invoked as /ce-compound. Its output unit is the Learning: one markdown file, one solved problem, filed under docs/solutions/<category>/, whose frontmatter (title, tags, module, problem_type, applies_when, severity, date) exists for retrieval rather than for reading.

Its discipline is timing. Klaassen locates the real bottleneck in recovery, not writing: postmortems rot in wikis. So ce:compound documents while the context is still fresh, fanning out subagents (a context analyzer, a solution extractor, a related-docs finder that guards against duplicates) while the orchestrator alone writes a single document.

The scale involved is modest. Klaassen's guide counts 35 Learnings, with skill-design in the lead. The canonical illustration is incident #714, which became a fix, a Learning, a test, and a doctrine at once. By that measure, compounding means retiring classes of failure. Whether a growing file count ever stops being the proxy for it is left open.