What ValarIQ delivers on the control path.

Know which people, systems and agents can propose financial actions.

Not a full enterprise CMDB. Discovery promote is separate from authorisation.

Define what each actor may do: amounts, destinations, actions and owners.

Financial authority deepest; non-financial templates limited.

Return ALLOW, ESCALATE or DENY before actions reach execution systems.

ValarIQ does not execute payments or hold funds.

Apply transaction policy bands and controls at decision time.

Core refund defaults are operational via the Action Gateway. Expanded governance catalogues deepen with customer programmes.

Evaluate evidence confidence so decisions are proactive, not retrospective.

Deterministic core is operational. External evidence providers require integration. Does not independently guarantee that source facts are true.

Build profiles from observed actions so verification focuses on what looks off.

Templates require tenant adoption. Playbooks do not self-certify readiness. Mappings do not imply compliance. Recommendations are SUGGESTED — not predicted ROI. Patterns are tenant-specific observations — no benchmarks. Provider reliability and execution outcomes remain Configurable without activated providers.

Route exceptions to named approvers with segregation of duties.

Advanced dual-control patterns limited.

Record attributable decisions with integrity checks within implemented scope.

Signed decision evidence is operational within implemented scope. Broader relationship traversal is provided by Evidence Graph.

Keep historical truth fixed when current authority or applicability changes.

Operational for signed decision evidence. Completeness depends on what was captured when the decision was sealed. Confirming that a payment rail actually executed remains a separate capability. Re-authorisation after change requires a complete agent and policy setup.

Integrate decide and verify into customer applications, workflows and agent runtimes.

Gateway client is available for integration programmes. Not distributed as a public package-registry release.

Isolate customer environments with roles, membership and onboarding controls.

Workspace lifecycle and onboarding are operational with logical isolation. Dedicated residency is roadmap.