Request
Intent enters from a portal, API, ITSM tool, or another upstream trigger.
How it works
Request -> PolicyOutcome -> Plan -> Execute -> Evidence
This is the supported path. PolicyFabric uses it to keep policy-informed decisions, controlled execution, and evidence aligned.
PolicyOutcome
An external policy system evaluates the request. PolicyOutcome becomes the semantic source of truth for supported planning.
Plan
PolicyFabric constructs a governed persisted plan. Supported approval requirements can block a request from proceeding to runnable execution.
Execute
The runner path executes the plan deterministically from persisted state and explicit ownership rules.
Evidence
Summary, policy-evidence, and step-state reads make it possible to reconstruct what happened and why.
Supported today
- Approval-aware supported flows
- Deterministic execution from persisted plans
- Explainable evidence and request-to-evidence reconstruction
Not implied
- No generic workflow authoring
- No provider-side exactly-once guarantee claims
- No broad current checkpoint runtime enforcement claims
Next step