About ProvenanceOS

Software now decides what we drive, what we get approved for, and what news we see. We built ProvenanceOS so every team can answer one question with certainty: where did this code come from?

Why we exist

In 2025 it became trivial to generate code with AI, but almost impossible to tell afterward which parts were AI-generated, which were copied from a public repo, and which were written by a human. For regulated industries, that opacity is a blocker. For everyone else, it's a slow-burn liability.

What we believe

  • Provenance is infrastructure. It belongs in the same tier as authentication, logging, and CI. Not bolted on after a regulator asks.
  • AI origin is a first-class signal. Not a flag in a comment. Not a vibes-based review. Statistical evidence that survives an audit.
  • Compliance should be a side effect. If your day-to-day engineering is good, SOC 2 and ISO 27001 should generate themselves.

Who builds it

ProvenanceOS is a product of Developer312, a one-person software studio focused on supply-chain integrity and AI-governance tooling. The team is led by Edward Brooks, an AV engineer by day and a full-time builder by night.

What's next

We're heads-down on real-time drift detection, multi-tenant policy libraries, and an open-source CLI so you can run the same checks in your terminal that power our dashboard. If that sounds useful, tell us what you'd build first.