Decision contracts (governance)¶

Decision contracts are the same alert rules you build in Alerts; this page is the governance view — ownership, lifecycle, linked data products, and activity — without the authoring UI.

When to choose this¶

Use Decision contracts when you need to:

Audit ownership and domain classification across all alert rules
Scan lifecycle (draft, review, active, paused, archived) from a contracts lens
See linked data products and navigate to ownership contracts
Open the builder only when someone needs to edit SQL, thresholds, or actions

Author new rules in Alerts — there is no Create button here.

Setup¶

Same prerequisites as Alerts: Databricks integration, roles logicengine.rules.read / logicengine.rules.write for builders; viewers with read access can open this list.

What users see¶

Surface	Path	Content
List	`/contracts/decision`	KPI strip (totals, active, needs attention, drafts), filters (owner, lifecycle, domain), table with last activity and linked product
Detail	`/contracts/decision/{id}`	Read-only overview, workflow progress if applicable, activity sparkline, linked products, Edit in Alerts

How it works¶

Data is loaded from the same Alerts API as the builder; two URLs, one object.
Row actions and the detail CTA jump to /logic-engine/{id} to edit.
The Automation Alerts entry and sidebar View as decision contract(s) link bring you back to governance when needed.

Limitations¶

No rule authoring on this surface — preview, activate, pause, and SQL edits stay in the builder.
Databricks-first execution model is unchanged (see Alerts doc).

Audit & compliance¶

Question	Where
Who owns this rule?	List / detail owner column and overview
What workflow state?	Workflow progress on detail (if configured)
Full change history	Administration audit log filtered by logic engine

Troubleshooting¶

Symptom	Cause	Fix
Empty list	No rules yet	Create a rule under Alerts
Cannot edit	On governance detail only	Click Edit in Alerts
Linked product missing	No data product wrapping the rule	Register the rule as a data product from the builder detail