On 22 October, to make later maintenance and extension work easier, the team started modularising the code. They studied several Go modularisation approaches — caddy, plugin and pingo among others — compared how they extend and how tightly they couple, and settled on a module design for the project.

On top of that the team borrowed the request-context pattern from gin-gonic and defined a single workflow: a request enters and moves through a fixed sequence of stages, each business module only caring about its own part. Boundaries survived and execution became regular — new capabilities have a place to plug in, and troubleshooting has a path to follow.