Hexagram 18: 蠱

The CRT sits on the workbench, casing shattered into a dozen pieces. Corporate reflex says: replace it, file the incident report, move on. Kintsugi says: no—this break has information. You gather the fragments. Mix the urushi lacquer with gold powder. Begin the painstaking reassembly, seam by seam. The gold veins aren't cosmetic—they're a map of exactly how this thing failed. Each join is documentation. The repaired screen doesn't pretend the break never happened; it makes the fracture pattern permanently visible. Hexagram 18 teaches work on what has been spoiled. Not blame, not disposal—repair. But the repair must be honest. The classical text warns: before you start (three days), understand why it broke. After you finish (three days), ensure the pattern doesn't repeat. Here's what corporate culture gets wrong: they treat failure as shameful, something to hide. Root cause analysis becomes theater—find someone to blame, write the report no one reads, declare the problem 'resolved.' Six months later, same failure, different team. Kintsugi is the opposite: you show the seam. You make the repair visible. The gold lines say 'this broke here, we fixed it here, we learned this.' The repaired vessel becomes more trustworthy than the original because its history is legible. Your equivalent: when the system fails, document exactly how. Make the fix visible in the architecture. The refactored code should show where the weakness was. The new tests should specify what broke. The updated runbook should explain the failure mode. Don't hide the scar—consecrate it. The gold isn't decoration. It's an invoice for the lesson. Each seam represents specific knowledge purchased through specific failure. Hiding that knowledge to avoid embarrassment is choosing to pay for the same lesson twice. Too little energy: you tolerate the rot, apply duct tape, avoid the real repair. The system fails again. Too much energy: you smash everything, rewrite from scratch, lose the institutional knowledge the breaks could have taught you. The middle path: patient repair that makes failure visible and therefore valuable. Wind beneath mountain. Gentle persistence beneath rigid stillness. The workbench patience that says: this thing broke, we will mend it properly, and the mended version will carry forward the knowledge of how it breaks. That's not weakness. That's governance.