Decision Review Playbook
Use the same evidence-first review sequence for every governance decision.
Review Sequence
- Open the decision by ID in Studio or through the decision API.
- Confirm the target, decision status, type, confidence, tenant scope, policy versions, and timestamps.
- Read the persisted explanation and policy outcomes before interpreting the graphs.
- Inspect the evidence graph to verify the facts and evaluation results supporting the outcome.
- Inspect ontology lineage to understand related assets, candidates, jobs, policies, and prior decisions.
- Check audit records plus request and correlation identifiers before recording a review conclusion.
Evidence is the bounded reasoning input. Lineage provides broader traceability context.
Respond by Outcome
APPROVED
Confirm the evidence and policy version, then pass the decision reference—not an informal summary—to the separate release workflow.
REJECTED or BLOCKED
Identify the matching rule and evidence value. Correct the candidate or evidence gap, then produce new governed evidence instead of editing history.
PROPOSED or INVESTIGATE
Treat the result as a review queue. Determine whether more evidence, a human decision, or a versioned policy change is required.
Missing Evidence
Find the unavailable metric, source, or evaluation record. Never infer a pass from absent evidence.
Record the Conclusion
Keep the decision immutable
A review conclusion belongs in your change-management or release process. Do not alter the historical decision, policy version, or source evidence to make the outcome more convenient.Read Policy Engine for rule semantics and Reviewing Governance Decisions for the Studio detail workflow.