Compliance-Native Flow Builder · The Visual Builder With Compliance Built In
Standard flow nodes plus unique Audact Compliance-Overlay-Nodes — every flow you build inherits Article 50 + GDPR + per-jurisdiction policy enforcement at runtime.
§1 · Standard library
Standard nodes
The composable primitives every flow is built from. Parity with what you expect from a modern voice-AI flow builder.
Conversation
Turn-based dialogue with model-of-choice. Default LLM, configurable per tenant.
Subagent
Sub-flow invocation. Compose larger flows from reusable building blocks.
Function
Deterministic logic — date math, lookups, calculation. No model in the loop.
Custom Function
Developer-defined logic executed in your runtime. Sandboxed by default.
Logic Split
Branching condition. Route the flow based on extracted variables or function output.
Extract Variable
Entity extraction from natural-language utterance. Typed, validated, audit-logged.
Call Transfer
Warm or cold transfer to human agent, queue, or external SIP destination.
End
Terminate the session and emit the signed compliance receipt.
§2 · Governance layer
Compliance-Overlay-Nodes
These nodes embed runtime governance directly into the visual flow. Drag a node onto the canvas, inherit the compliance.
Article 50 Attestation Node
- What it does
- Injects the right disclosure for each jurisdiction and emits a signed attestation receipt at runtime.
- Why it matters
- Maps directly to EU AI Act Article 50 enforcement. The disclosure is injected and signed before the caller hears it — not reconstructed after the fact.
Cross-Jurisdiction Consent Node
- What it does
- Validates consent across multiple Member States with a full provenance trail, reconciling national overlays into one consent state.
- Why it matters
- Single-source-of-truth consent across the EU — one consent state your end-clients can rely on in every jurisdiction.
Scope-of-Practice Node
- What it does
- Blocks out-of-scope claims at runtime — medical advice, legal advice, financial advice — and hands off cleanly when needed.
- Why it matters
- A safety harness regulated sectors can actually deploy — out-of-scope advice is blocked before it is spoken.
Compliance Checkpoint Node
- What it does
- Validates compliance state before any output is committed to the channel, with a full audit log. Halts execution before a non-compliant utterance is sent.
- Why it matters
- Compliance happens before harm — not after the fact, like reactive monitoring tools.
Vulnerable Person Detection Node
- What it does
- Detects vulnerability markers in real time and automatically routes to a human or a modified, safer path.
- Why it matters
- Critical for healthcare, finance and public-sector deployments where extra care is non-negotiable.
Biometric Consent Governance Node
- What it does
- Validates voice-cloning and biometric consent for banking, insurance, telecom and identity flows, including revocation and freshness checks.
- Why it matters
- Keeps biometric and voice-cloning flows on the right side of GDPR Art. 9 and high-risk AI requirements.
§3 · Compliance built in
Every template ships with the same compliance built in.
When you publish a template, the Compliance-Overlay-Nodes travel with it. Anyone who builds on your template inherits the same Article 50, consent and scope-of-practice governance at runtime — so compliance is consistent across every flow your agency ships, without re-implementing it each time.
§4 · Architecture
Tech stack
Visual canvas
A versioned canvas with diff view, undo and sharing, so flows are easy to author and review.
Runtime
EU-hosted execution with per-node observability, latency budgets and retry semantics.
Versioning
Every flow is versioned. Every publish is an immutable, tagged artifact you can roll back to.
Sandbox vs Production
Dual environments per policy. Sandbox carries a stricter policy preset; production needs explicit promotion.
Join the early-access list
We're onboarding agencies onto the flow builder. Compliance-Overlay-Nodes available from day one.