Hired to administer the Treaty 8 annuity file (19 First Nations, about $3M). I did that, but I also became the directorate's de-facto developer and data person. I built the app and the cleaned datasets that the roughly 30-person team used to run a ~$120M annual funding program, and the director came to rely on me directly for the data senior management asked for. In my final two months, the directorate gave me a dedicated mandate to find digital solutions and push them toward production. I used it to start scoping how to bring AI into the department's data and funding work, the same thread I now build on at StyroRail.

• Built a .NET 8 Blazor Server app, running locally, that read from GCdocs and the directorate's large Excel files and gave officers a web-app experience over data they used to handle by hand. It produced funding recommendations in one consistent format and exported them to Excel, so every officer's work followed the same pattern without losing the tool they were comfortable in. It cut the formatting and cleanup time on a recommendation by at least half. After I demoed it to senior management, several directors pushed to turn it into a funded departmental system.
• Wrote custom .NET console apps, plus Power Query and SQL, to clean and reconcile more than 9 years of legacy funding data: thousands of requests processed by different teams in different styles, full of noise and errors. That cleaned dataset is what made everything built on top of it trustworthy.
• Built Power BI dashboards covering all 19 communities and 9 years of funding history, with interactive maps and enough filters to stay easy to navigate. Officers, directors, and senior management all used them.
• Supplied the evidence behind a major change in how the directorate funds: a new model where recommendations follow the negotiation stage and rest on data instead of each officer's personal write-up. That shift needed years of clean history in front of senior management, and I was the person they came to for pulling it together and presenting it. The change went through.

TLTS (Trust, Lands and Treaty System) is the federal system that manages over $1B in trust assets and more than $500M in annual cash flows for Indigenous communities across Canada. I was one of five developers on it. My work was full-stack feature development with a heavy database focus, built to Protected B security standards and delivered in Agile sprints.

• Built and expanded features across the ASP.NET MVC application, with most of my time in the data layer: writing and optimizing Oracle queries and wiring system-to-system integrations in SQL.
• Contributed to the Treaty Annuity Payments module, which now processes annuity payments for hundreds of thousands of recipients a year. That volume used to live outside the system; moving it in meant building for the accuracy and audit trail a federal financial platform has to hold.
• Contributed to a separate .NET Minimal API service that connects TLTS to other government systems and third-party platforms like OneFeather, so data moves across departments instead of being re-entered by hand.
• On my own, designed and integrated the field hardware for in-person annuity events: signature pads, receipt printers, and barcode scanners. It replaced paper signature records and a separate legacy application, so payments are now captured, signed, and receipted digitally on site.