Temporal Governance
Temporal remains your workflow engine. Gvner enforces approval at activity boundaries so workflow progress is deterministic, auditable, and fail-closed.
How Gvner governs Temporal workflows
1. Workflow emits an activity intent
Before an activity executes, the workflow prepares intent payload and actor context.
2. Gvner evaluates authority + policy
The workflow calls Gvner. It waits until an ALLOW or DENY decision is returned.
3. Workflow branches on decision
ALLOW executes activity. DENY triggers compensation, escalation, or controlled termination.
4. Evidence is persisted
Decision metadata is available in workflow history and in Gvner evidence exports.
/adapters/http/*).Runtime behaviors to design for
Fail-closed execution
Unreachable policy service means activity does not execute.
Human-in-loop approvals
Route high-risk activities into explicit approval gates.
Safe rollout
Use deployment checks and canary strategy before broad release.
Resilience drills
Validate readiness, restart advisory, and maintenance controls.
Example: denied activity
Below is a representative example of a Temporal activity that was denied by Gvner during workflow execution.
Production checklist
Call to Action
Keep Temporal orchestration and add explicit execution control at every critical step.