Free tool Tier a model against OSFI E-23 in about five minutes — seven risk dimensions, the controls your tier requires, and a report you can print. Open it →
osfi-gate

About

Compliance as code

Infrastructure stopped being a thing people configured by hand, and became a thing people declare, review and version. Security followed. Compliance mostly did not. It is still a quarterly round of assertions, kept in documents, evidenced by screenshots, and trusted because of who signed it.

osfi-gate treats a control the way the industry already treats infrastructure. The rules that decide whether a change is acceptable are code, in a repository your second line owns. They are reviewed in a pull request, versioned, and identified by commit. They run automatically on every change, and what they produce is not a status in a dashboard but a signed artefact that records the decision and everything needed to reach it again.

That produces three things a document cannot:

Why it exists

Canadian federally regulated institutions have no shortage of control frameworks. What they tend to lack is evidence — the kind somebody outside the team can check without taking the team's word for it.

The usual arrangement is a control attested quarterly by the people who operate it, recorded in a platform that is itself trusted, and reviewed by someone with no practical way to reproduce the finding. Every step is reasonable. The result is a chain of assertions with no point at which anyone can independently confirm anything.

This takes the opposite position: the evidence should survive not being trusted. If the tool that produced it disappeared tomorrow, the evidence would still check out.

That constraint is what shaped the design, and it is also what rules things out. It is why approvals happen in Git rather than in a web form, why the tool refuses to report "unknown" as "passing", and why there is no hosted service that would require sending you evidence you were told you did not have to trust us about.

Who builds it

Blake — one person, not a team. Twenty-five years leading enterprise technology teams, working as a digital transformation and AI architect, now building this.

What that means for you is on the front page under Where this is, plainly: what is finished, what is not, and what nobody can tell you yet.

osfi@melx.buzz Connect on LinkedIn

What is on this site