Block Zero: Oh, no! Claude, Kiro and I over-engineered the throwaway.

In a story of over-engineering, an AI-assisted builder named Block Zero learned a valuable lesson. Builder Block Zero was tasked with creating an agent named Porch Light, which monitored public meeting agendas for a single city. The process involved Kiro building, Claude reviewing, and Block Zero validating and deciding.

Block Zero's initial plan was a simple two-hour spike to prove the stack and deploy to Bedrock AgentCore. However, it turned into a much longer endeavor. By the end of the day, Kiro had written a byte-identity test to protect a throwaway folder tagged [THROWAWAY]. Block Zero, who had approved the task list, had also approved the test without questioning its necessity.

During the block, Block Zero questioned the slow progress, which led to the creation of Spike B. The purpose of Spike B was to uncover any wrong assumptions early on, as the cost of correcting a mistake later on would be significantly higher. Kiro diligently reported discrepancies, and Block Zero agreed with the need for rigor and local reasoning.

However, a significant issue arose when the deployed runtime used a built-in logger instead of the designed logging module. This oversight meant that the redaction processor, size cap, and context binding never executed, leaving a large security loophole. The fix involved adding a few log lines and redeploying, but the lesson learned was clear: a control that has never run in the environment it protects is not a control at all.