Documentation

Open App

Core Concepts

Validation

How PIILOT validates workflow structure before users trust a generated automation.

PIILOT validates generated workflow drafts before presenting them as usable automations. Validation checks the structure of the graph and records issues with severity levels so users can review what needs attention.

The planner uses deterministic validation after workflow generation. If structural errors are found, PIILOT attempts one repair pass and then validates again. When errors remain, the workflow is downgraded so it is not treated as a clean ready-to-run draft.

Validation and repair loop
flowchart TD
  A[Generated workflow skeleton] --> B[Adapt to WorkflowSpec]
  B --> C[Validate graph]
  C --> D{Structural errors?}
  D -- No --> E[Simulate workflow]
  D -- Yes --> F[Repair attempt]
  F --> G[Validate repaired graph]
  G --> H{Still invalid?}
  H -- No --> E
  H -- Yes --> I[Downgrade status and add review notes]
  I --> E
  E --> J[Compile setup and enrichment]

Validation issue levels

  • Info: useful context that does not block review.
  • Warning: something the user should inspect before setup or execution.
  • Error: a structural problem in the graph that prevents a clean automation state.
Validation is not legal or business approval

PIILOT validation checks workflow structure and setup readiness. It does not replace business approval, security review, legal review, or user judgment.