Operating Modes - dazense Docs

dazense supports three user experiences:

Direct Analytics — fastest path, minimal controls
Trusted Analytics V1 — policy + contract + semantic governance
Trusted Analytics V2 — V1 runtime with OpenMetadata-fed governance inputs

Mode comparison

Mode	What users get	Guardrails	Best for
Direct Analytics	Natural-language SQL analytics	Minimal (LLM-guided only)	Prototyping, internal technical teams
Trusted Analytics V1	Contracted analytics with provenance	Dataset bundles, policy checks, PII block, time filters, audited contracts	Production analytics where trust matters
Trusted Analytics V2	V1 + enterprise metadata intelligence	Same V1 enforcement + OpenMetadata signals (PII, lineage, glossary, ownership, quality)	Enterprise-scale governed analytics

How this maps to your project files

File	Direct Analytics	Trusted Analytics V1	Trusted Analytics V2
`semantics/semantic_model.yml`	Optional	Required for governed metrics	Required
`semantics/business_rules.yml`	Optional	Recommended	Required
`datasets/<bundle_id>/dataset.yaml`	Not used	Required	Generated/synced from metadata + reviewed
`policies/policy.yml`	Not used	Required	Auto-populated/synced + reviewed
`contracts/runs/*.json`	Usually absent	Generated per governed run	Generated per governed run

Recommended rollout

Start with Direct Analytics for onboarding speed.
Move to Trusted Analytics V1 for production trust and auditability.
Add Trusted Analytics V2 when OpenMetadata is available and stable.

V2 does not replace V1. V2 keeps the same enforcement runtime and upgrades the governance signal source.

Business Rules Trusted Analytics V1