Article
Releasing a multi-portal platform without losing state between components
The examples in this article are a composite of late-stage failures between roles, portals and integrations. The guide shows how to isolate each failure for agent-assisted implementation and human review.
A platform can pass the tests for each screen and still fail across a complete workflow. An applicant submits a record in one portal, an operator sees an earlier version in another, and an external service confirms an action that neither portal displays. None of those components looks broken when inspected alone. Their views of the shared state disagree.
The situations below combine patterns drawn from late-stage platform work. They do not describe one organisation or reconstruct a private project. I use the same investigation method for each one: name the state, follow its transitions, isolate the smallest failing contract, and give the implementation agent and human reviewer enough evidence to check the repair.