Darcy AI assistance
Darcy is the AI assistant in the Builder. Use it to understand Govform, discuss the service you are working on, improve its content and configuration, or investigate a problem in a prototype.
Start a conversation
Open Darcy in the Builder. For questions about a particular journey, open the relevant service and page before asking. Darcy can use the current Builder context and inspect the service's pages, components, conditions and actions through its tools.
State the outcome you need and include the rule or constraint that matters. For example:
- “Explain how this service decides which page comes next.”
- “Rewrite this question and hint text for someone applying for the first time.”
- “Only ask for employer details when the applicant says they are employed.”
- “Explain why this calculation is blank in my current prototype journey.”
Darcy can ask structured follow-up questions when information is missing. Answer those questions to continue the same task. Start a separate conversation for independent work so the requirements and decisions remain easy to follow.
What Darcy can help with
- Product guidance: explain where settings live and how platform features fit together.
- Service design: discuss page structure, task lists, branching, reusable patterns and review steps.
- Content: draft or revise page titles, questions, hints, validation messages and supporting text.
- Configuration: create and update supported pages, components, selections, conditions and actions.
- Liquid and integrations: explain templates, pre-population, calculations and action data, and help configure supported integration behaviour.
- Diagnosis: inspect the current prototype journey and Flow view, saved history and recorded deployment state where that context is available.
Darcy can also illustrate a journey or workflow with a diagram in chat. A diagram helps explain the design; review the actual pages and conditions to check the implemented behaviour.
Choose how changes are made
| Change mode | Behaviour |
|---|---|
| Allow changes | Darcy can create and edit as you work, within your existing permissions. |
| Ask before changing | Darcy presents a plan for you to approve before making the requested changes. |
| Advice only | Darcy can inspect and explain without making changes. |
These modes do not increase your library permissions. Library administration operations use dedicated confirmation controls even in Allow changes mode. Publication remains a controlled step: a proposed deployment or approval request is not evidence that a version has been deployed.
Investigate a prototype problem
- Reproduce the issue in User view using representative test data.
- Tell Darcy the page, answer or action involved and what you expected to happen.
- Ask it to inspect the current prototype journey or Flow view and explain the relevant condition, value or action result.
- Review any proposed change, then repeat the affected route and its alternative branches.
Prototype actions may use mock results. Test real integrations in QA before relying on them. Darcy's recorded deployment information describes what Builder published; it does not check the health of a running service.
Review the result
Inspect edited content and configuration, then test the journey, including validation and Back navigation. Confirm that Darcy has used the business rules you supplied and that shared settings or integration changes have the intended scope.
For larger creation tasks, see Darcy AI form build. For release review, see Explain differences between service versions.