a governance layer nobody asked for
python · opa · postgresPolicy, audit and approval routing wrapped around a model gateway. Every enterprise wants it in month six. Nobody puts it in the demo.
[ placeholder content ] — shipped with the site so the layout can be reviewed. Not a published project.
The gap this fills
The demo shows a model answering a question. The deployment shows a model answering a question on behalf of someone, with a record of who asked, what data it touched, which policy allowed it and who signs off when the policy says no.
That second system is most of the work and none of the slide deck.
What worked
The audit trail. Append-only, one row per decision, with the policy version that produced it. When someone asks “why did it do that in March”, there is an answer that does not involve reading logs.
What failed
The latency budget, comprehensively. Evaluating policy synchronously on every request added enough milliseconds to make the interactive use case feel broken. The architecture was correct and the product was unusable, which is a specific kind of failure worth filming.
This is placeholder content shipped with the site so the layout can be reviewed with realistic text. Replace it with a real project.