GovernanceDoo · Govern & Trust
Status: Coming SoonGovern data, AI and decisions from one control plane.
One inventory of your data assets, pipelines, dashboards, models, agents and applications — with the owner, policy, risk and history of each.
- What it is
- GovernanceDoo is designed as the control plane of DooHorizon: a shared inventory, policy, permission and audit layer across every asset the other products create.
- Who it is for
- Data governance, security, risk and compliance leaders — and the product owners who answer to them.
- Status
- Coming Soon. In development. Capabilities described are the design intent.
The problem
You cannot govern what lives in eight different tools.
Each tool has its own permissions, its own log and its own idea of who owns what.
Lineage breaks at every hand-off, so the question “where did this number come from?” takes days.
AI adoption is outpacing the inventory: models and agents go live before anyone has recorded that they exist.
Core capabilities
What GovernanceDoo is designed to do.
GovernanceDoo is not yet released. These are the capabilities it is being designed around.
Data catalog
Find datasets and understand what they contain and who answers for them.
Lineage
Trace an output back through the pipelines, models and sources that produced it.
Ownership
Give every asset a named owner and a steward.
Classification
Label sensitive data and let policy follow the label.
Quality
Record expectations for data and see when they stop being met.
Policy
Write a rule once and apply it across products.
RBAC
Role-based access shared by every Doo product.
Audit
One record of who did what, to which asset, and when.
Model governance
Inventory, review and approve models with their evidence attached.
AI governance
Register agents, prompts and tools, and control what each may reach.
Risk
Rate assets by risk and focus review where it matters.
Approval workflows
Route changes and releases to the people who must sign them off.
Monitoring
Watch for policy breaches and assets drifting out of compliance.
Reporting
Produce the evidence an internal or external review asks for.
How it works
How it is intended to work.
Step 1: Inventory
Assets created in FlowDoo, VizzDoo, MLDoo and AIDoo register themselves; nothing is catalogued by hand.
Step 2: Assign and classify
Give each asset an owner, a classification and a risk rating.
Step 3: Apply policy
Set who may see, change, approve and deploy — once, for every product.
Step 4: Review and evidence
Follow lineage, read the audit trail and report on the state of the estate.
Example workflow
What it looks like in practice.
The design intent: every governed asset passes through the same four controls.
- DataModelsAgents
- Inventory
- Policy
- Approval
- Audit
Part of DooHorizon
How GovernanceDoo connects to the platform.
Governance that lives where the work happens, instead of in a catalogue the work never touches.
FlowDoo
Pipelines and their runs become lineage: which sources fed which outputs, and when.
About FlowDooVizzDoo
Datasets and dashboards carry owners, classifications and sharing policy.
About VizzDooMLDoo
The model registry, Model Passports and approvals become model governance.
About MLDooAIDoo
Status: Coming SoonAgents, prompts and tool permissions become AI governance with a trace per run.
About AIDoo
Security and governance
Governed like the rest of the platform.
Designed with enterprise security and governance requirements in mind. No certification is claimed that has not been obtained.
How DooHorizon approaches security- Designed around a single identity and permission model for the whole platform.
- Designed so audit records are append-only and evident when altered.
- Policies are intended to be enforced by the products, not merely documented beside them.
- No compliance certification is claimed; the compliance roadmap is published in the Trust Center.
Use cases
What you can build with GovernanceDoo.
Govern AI adoption
Know which models and agents exist, who owns them and what they are allowed to do — before they multiply.
Answer “where did this come from?”
Follow a number on a dashboard back to its source in minutes.
Prepare for review
Give auditors the inventory, the approvals and the history from one place.
Protect sensitive data
Classify once and let access rules follow the data through pipelines, dashboards and prompts.
The concept
What GovernanceDoo could look like.
- Data Assets
- Pipelines
- Dashboards
- Models
- Agents
- Applications
| Asset | Risk | Policy | Owner | Status | Last Activity | Audit |
|---|---|---|---|---|---|---|
| churn-risk v3 | Medium | Model review | Customer Analytics | Approved | Today | 12 events |
| credit-scoring v1 | High | Model review + sign-off | Risk | In review | Yesterday | 31 events |
| demand-forecast v5 | Low | Standard | Operations | Approved | 3 days ago | 8 events |
| pricing-uplift v2 | Medium | Model review | Commercial | Draft | Last week | 4 events |
FAQ
GovernanceDoo: common questions.
Is GovernanceDoo available today?
Not yet. GovernanceDoo is in development. Governance features already built into the individual products — roles, audit trails, the model registry — are described on their own pages.
Does GovernanceDoo make us compliant with a regulation?
No product can do that alone. GovernanceDoo is designed to help teams keep the inventory, controls and evidence that compliance work relies on.
Will it govern assets outside DooHorizon?
The first release is designed around assets created in the Doo products. Interoperability with external catalogues is part of the longer-term direction.
How is this different from a data catalogue?
A catalogue describes assets. GovernanceDoo is designed to also enforce policy on them, because it shares the platform's identity, execution and audit layers.
Follow GovernanceDoo from concept to release.
Start with one use case. Expand across the ecosystem.