Anti-corruption civic reporting platform, government scale

The problem

A provincial government secretariat needed a citizen corruption-reporting platform built for government scale: intake that could handle a high and unpredictable volume of reports, routing that got each report to the right department, and an accountability trail that made it possible to track what happened to a report after it was filed. This isn't a system where you can ship a rough version and iterate quietly — it's public-facing and it has to hold up under scrutiny from day one.

What I built

I architected the platform around a multi-agent orchestration pattern: an S1 architect stage that plans the work, followed by S2, S3 and S4 execution stages that implement, verify and integrate it. Rather than treat this as a one-off way of working, I committed two reusable engineering templates to the repository — ORCHESTRATION_TEMPLATE.md and S1_ARCHITECT_TEMPLATE.md — so the same delivery pattern could be picked up by future engineers or future phases of the same platform without reconstructing the method from scratch.

Outcome

The platform shipped with intake, routing and accountability tracking in place, using a delivery method that leaves behind reusable templates rather than a one-time process that only existed in one engineer's head.

Why it mattered

Civic infrastructure at government scale is a different kind of pressure than a typical client project — it has to be auditable and it has to survive turnover on both the client and vendor side. Committing the orchestration method itself as a template, not just the code it produced, was a deliberate choice to make the delivery process as inspectable and reusable as the platform it built.