The editor
Validation
The readiness checks a draft passes before it can publish, and the difference between an error and a risk.
Before a draft can publish, the validator runs. It drives the readiness dots on the rail, the badge on the publish control, and the publish refusal itself, so what you see while editing is exactly what the publish gate enforces.
The same rules apply whether you edit by hand, through the Builder Chat, or over the API.
Two severities
- Errors block publishing. The publish is refused and the blocking issues are listed, each with a link straight to the section that needs fixing.
- Risks do not block. They flag a known weak spot so you can fix it or acknowledge it and ship anyway.
Representative errors
| Example check |
|---|
| The prompt is empty, or references a variable you have not added |
| A tool has a duplicate name, points at a missing prerequisite, or sits in a prerequisite loop |
| A variable used by the agent has no value, or holds a placeholder |
| No voice is selected |
| A disclosure is switched on but its line is blank |
Representative risks
| Example check |
|---|
| No way to transfer to a human, or no way to end the call cleanly |
| Recording is on but no recording disclosure is spoken |
| The knowledge search tool is on but no sources are ready |
| The most recent run of a test failed |