Design a complete DPI-AI service in 6 guided steps — from use case selection and Public Agent configuration to citizen journey mapping, AI Block selection, YAML workflow generation, and a full governance checklist.
1 · Use Case
2 · Agent
3 · Journey
4 · AI Blocks
5 · Workflow
6 · Governance
Select a service to design
Filter by sector, region, and complexity, then pick a use case. You can customise the journey and AI Blocks in the next steps.
Sector
Region
Complexity
Configure the Public Agent
The Public Agent is the citizen-facing interface. It orchestrates the interaction — collecting intent, triggering the DPI Workflow, and delivering results. It is not a decision-maker; it is a constrained, accountable extension of government.
Channels (select all that apply)
Languages supported
Escalation path
Agent persona (optional)
The name or persona the citizen interacts with. Cosmetic only — does not affect workflow logic.
Constraints (locked — accountable by design)
AI Model — underlying LLM powering this agent
Affects capability, cost, and data residency. For government deployments consider on-premises or regional cloud options.
Map the citizen journey
Define the touchpoints from first contact to service delivery. These are the steps the Public Agent orchestrates — add, remove, or reorder as needed.
Select AI Blocks
We've pre-selected the AI Blocks typically used for your chosen service — review them and adjust to match your context. Add or remove blocks based on what your team has available and what the service actually needs.
🧩 Foundational — General-purpose functions (translation, speech-to-text, OCR, summarisation). Most services need at least one.
⚙️ Sector-Specific — Policy and operational logic: identity verification, eligibility checks, payments, registry lookups. These are pre-filtered to your region and use case.
🛡️ Safeguards — Governance blocks (bias check, consent verification, anomaly detection, human review) that can be inserted at any point. At least one safeguard is recommended for every service.
Your DPI Workflow specification
This is your service design output. The diagram on the left shows how the Public Agent, AI Blocks, and DPI systems connect. The specification on the right is the machine-readable definition of your service.
You don't need to understand the code — just download or copy it and share with your implementation team. Switch between Code / Custom (portable YAML for any tech stack) and No-Code / OpenFn (ready-to-deploy for OpenFn users).
Architecture Overview
Select a use case to see the architecture diagram
Portable YAML spec for any tech stack or implementation team.
Before any AI-enabled service goes live, your team needs to confirm these governance decisions. These are not technical settings — they are policy and accountability commitments that must be made by service owners, legal teams, and programme leads.
Tick each item your team has addressed. You can proceed at any stage — unchecked items will be flagged as deployment risks in your downloaded specification, so your implementation team knows what still needs to be resolved.