Capability capture is the quiet cost no one invoices. When a tool does something faster than you can, you stop doing that thing — and within a few years, you lose the ability to do it at all. This is not laziness; it is the normal logic of cognitive offloading. But the eleventh-century Islamic polymath Al-Biruni noticed something structurally similar when he studied how astronomical tables spread across the Islamic world: scholars who inherited finished tables gradually lost the geometric intuition needed to reconstruct them if the tables were wrong. They could use the output without being able to audit the process. The tool had become a trust relationship they couldn't verify. This is precisely the risk profile of modern business technology — not that your CRM or recommendation engine is malicious, but that its outputs become the water you swim in, and your ability to detect when it's wrong degrades quietly and without alarm. Al-Biruni's antidote was deliberate reconstruction: periodically working through the underlying calculation yourself, not to replace the table, but to retain the capacity to question it. The discipline that transfers: every tool you depend on for decisions deserves, once in a while, a manual pass — not to be efficient, but to stay in a position where you could catch the tool failing.

Pick one piece of software that generates outputs you regularly act on — what would you do first if you discovered it had been silently wrong for six months?

Drawing from Islamic scientific philosophy / History of knowledge transmission — Al-Biruni (Abu Rayhan al-Biruni)