Lock Down the Shared Kernel
Hard About 35 min Katabench Pro
The stable kernel reaches UP into two features: it borrows tax math from Pricing and a rounding helper from Checkout. Inlining the obvious tax edge clears one rule but leaves the allowlist and the helper-placement rule red, because a single forbidden-pair fix misses the second back-edge. Pull EVERY borrowed helper down into the kernel to turn all three green.
The full brief is part of Katabench Pro
Pro opens this kata's brief, its starter code and its grader. To see how the track works first, try Break the Checkout Cycle, which is free.
How it is graded
You work across multiple files, and architecture rules turn the design boundaries into executable feedback.
What it practices
- Stable dependencies
- Stable kernels and contracts must not depend on volatile features.
Related katas
- Break the Checkout Cycle Hard Free Orders, Pricing and Promotions import each other in a three-hop cycle while Pricing also reaches into Inventory's internals. Moving the obvious call only rotates the cycle; hoist the shared vocabulary into a kernel leaf and reach Inventory through its published port to turn every rule green.
- Contracts Don't Depend Back Hard Pro The stable shared-contracts module depends back on a volatile feature to build a label. Invert the arrow without changing what Describe returns, and don't just drag the feature's service into the contract.
- Events Flow Up, Not Down Hard Pro A stable events hub reaches DOWN into a feature for a helper, and one feature reaches SIDEWAYS into a sibling to send an SMS. Cleaning up the hub is the obvious move, but it leaves the feature-to-feature edge red; only routing the sibling call through a hub-published port turns everything green.
- The Shared Kernel That Wasn't Hard Pro Support routes tickets off a tier it reads straight out of Sales's private Customer entity. Decouple the two features through the shared kernel, but publishing the fat entity isn't sharing, it's fusing.