Why Our Tool Catalog Keeps Moving

A public tool catalog only stays useful if it moves. The moment it becomes a static list of logos, it starts lying about how work actually happens. Tools get promoted, demoted, retired, replaced, and sometimes moved out of sight because the team has not earned an opinion yet.

That is why we treat the Replace Works catalog less like a trophy case and more like an operating system. Tool Stack is for software we actually rely on. Tool Lab is for things worth testing before they become part of the workflow. Company Stack is for business infrastructure. Company Lab can be empty when we do not have a real recommendation. Empty is better than decorative.

This matters more in AI work because the market changes faster than normal procurement cycles. A model wrapper can become obsolete in a week. A workflow tool can become essential after one project. A product analytics platform might belong in the stack, while an experimental social intelligence product belongs in the lab until we have enough reps with it. The label is part of the judgment.

The rule we keep coming back to is simple: publish what reflects current practice. If something has moved into daily use, it should graduate. If it no longer fits, remove it. If we are only curious, say that clearly. The catalog should make our standards visible, not make the site look full.

That is also why the boring data hygiene matters. Slugs, sources, active flags, and deduping rules are not just database chores. They are how the site preserves meaning. A tool should not live in both Stack and Lab. A business lab with no real candidates should not pretend otherwise. The interface is only trustworthy when the underlying catalog is honest.