Back to Projects
Data + AI governancev1.0
Flagship project

Governance Spine

Controls for lineage, policy, release discipline, and evidence so AI operations stay safe when they move fast.

Safe output is a system property. If the controls are weak, the prompts will not save you.

LineageApprovalsRollback
What this proves
Trace data lineage before it touches a model or an agent.
Require policy checks and release gates for consequential actions.
Keep audit logs and rollback paths available from day one.
Open-source stack
OpenLineagedbtGreat ExpectationsOPAPlaywrightAudit logs
Experience mode
Step 1
Asset
Step 2
Owner
Step 3
Purpose
Step 4
Registry
Data catalog
You cannot govern what you have not named.
Live pattern
Engineering lens
  • Every critical asset needs a known owner.
  • The registry becomes the shared source of truth.
  • Unknown data should not be allowed to masquerade as trustworthy data.
Platform fit
This project belongs in Llewellyn Systems because it turns a repeated engineering pattern into a governed operating asset. The page is not a slide deck. It is a proof surface for how the system is built and how it behaves.
Toolchain note
Use JupyterBook for publication, MyST for source text, Voilà for notebook apps, Binder for reproducible environments, and JupyterLab or Colab for interactive editing. The page itself is the front door to that workflow.
Related projects
Governance Spine v1.0 | Llewellyn Christian