Match the decision to the proposed work
Connect issues and verifies context, plan, mutation, diff and promotion decisions bound to digests. Production hosts use durable-required mode with injected receipt storage and signing. The README describes a permit as usable only after its receipt has been stored and exact read-back matches. Verification at the point of use checks freshness, scope and integrity. This gives a concrete integration rule: changing the target, plan or relevant context requires the corresponding decision binding to be reassessed.
Use decisions for branching, then enforce effects
DecisionRuntime evaluates shared predicates and immutable decision graphs without evaluating creator-authored code. It validates before execution, bounds complexity and traces, pins subgraphs by revision/digest, and produces replayable results. Form conversion lives in a dedicated adapter. Workflow conversion only admits exact outcome-operation revisions in the server-controlled allowlist; the workflow/product runtime still owns effect execution and authorization. Keep a graph evaluation trace available to explain why a branch was selected.
Make human review useful
HumanReview, ReviewQueue and the governance modules provide product composition around assignment, escalation and review outcomes. Present the exact proposed action, its scope, material changes and supporting evidence. A review record should identify the decision it produced and the work it applies to. Keep obligations visible: an allow decision can still require a host to fulfill conditions or persist evidence before an action is eligible. A button label or a previously granted role is not a replacement for that current decision.
Follow a practical path.
Inspect a protected action
Follow its approval requirement, trusted actor/context and decision request. Locate the receipt store/signature ports and the point at which the executor re-reads or verifies the resulting permit.
Trace a changed proposal
Compare the approved target with a changed input, stale plan or different scope. Use the maintained validation path to see which binding invalidates the old receipt and which review must be repeated.
Check the operator experience
Review how pending, denied, expired, superseded and completed decisions appear in the queue. Link the operator back to the exact evidence and outcome rather than collapsing every non-success state into a generic failure.