A named concept earns its place only when you can point to it operating in a real artifact — the bridge from the concept library to the systems and articles that prove it.
A named concept earns its place only when you can point to it operating in a real artifact — the bridge from the concept library to the systems and articles that prove it.
A concept library is easy to fill with clever-sounding terms. The discipline is that a concept isn't earned until you can show it working in something real — an article that demonstrates it, a system that runs on it, an engagement where it did the job. "Structure Beats Magic" is a slogan until you can open the backbone that was built on it. "Eat Your Own Dogfood" is a maxim until you can point at the 700 articles you actually ran through your own pipeline. The named idea is the claim; the artifact is the evidence. Concepts in action is the rule that every concept should have at least one.
This is the bridge between two layers of the system: the concept library (the named, reusable ideas) and the use-cases / articles (a concept applied to a concrete situation — see the use-cases convention). It's also the antidote to a library that drifts into abstraction: if a concept has no artifact demonstrating it, that's a signal — either it isn't real yet, or the demonstrating piece is the next thing to write. It ties directly to Proof, Not Slides and Show the Machinery: don't just define the idea, show it running. As a content structure, "Concepts in Action" is the natural series/hub label for the collection of pieces that each demonstrate a concept working in reality.
Related: Proof not slides · Show the machinery · Eat your own dogfood · Practice what you evangelize · Structure beats magic.