AmtocSoft Tech Insights

Introduction The first time the cross-team retrospective syndication format I described in the previous post ran into a wall was not when the third product team joined the platform team's syndication pass. It was when the second corpus came online. The platform team had spent three quarters running the retrospective syndication on a single contract corpus, the customer-facing one, with the recommender team and the transactions team as the two adjacent product teams. The format worked. The cross-team register stayed honest, the consultation requirement caught two cache changes that would otherwise have surprise-paged adjacent on-call rotations, and the manager review converged in fifty minutes flat. Then the internal-tools team finished their own contract corpus, the one that backs the developer-facing internal RAG endpoint plus the support-ticket summariser plus the meeting-notes agent, and asked to plug into the same syndication pass. We did not realise at the time that pl...

Introduction The first time a platform team's quarterly retrospective produced an architecture commitment that landed in an adjacent product team's on-call rota was a Tuesday in February, and nobody on the platform side had warned the recommender on-call engineer that a runtime cache change was about to ship into her week. I watched the page fire at three in the morning her time, watched her open the runbook, watched the runbook explain a cache layer she had not been on the architecture commitment list for, and watched her ping the platform team's slack channel with a polite but noticeably tired sentence asking what had changed. The platform team had run a perfectly clean attestation-aware retrospective, had made the runtime cache refactor commitment with two-channel evidence as I described in the previous post , and had shipped the refactor on the right cadence. The recommender team had been carrying the on-call rota for three contracts that lived inside the cache l...