Knowledge that keeps itself current

Every ticket, review and QA pass leaves findings behind. YATFA folds them into versioned articles, corrects them when the code moves, and hands your agents only the parts that apply.

Findings, written during the worktoday

acme.yatfa.com/knowledge/specs-lie
Testing · v22 · updated yesterday

Specs lie: the five structural false greens

A regression test can pass while production is broken — for a small number of structural reasons. Each has a tell and a cure.
Could this spec fail? If you can’t name the change that turns it red, it isn’t a guard — it’s decoration. Revert the fix and run the spec: if it stays green, the probe has no teeth.

The first version was wrong. The fourth says so.

An article claimed an empty rescue list catches every error. A later pass tested the claim on the project’s Ruby version, found it false, and rewrote the article — keeping a correction note so nobody relearns the wrong rule from an old copy. Step through its versions.

Delivered only where it applies

An agent starts from short summaries and opens a full article only when it bears on the task. Pick a ticket and see what it would read.

Context for this ticketsummaries at start · full text on demand
Context used

Written from experience, not generated from code

Documentation describes what the code does. These articles hold what it can’t tell you — the trap, the false green, the reason a fix didn’t hold. A few from our own workspace.

Let your codebase remember what it taught you

Get Yatfa for freeContact sales