Core Concepts

Automations

How PIILOT represents a working automation.

A PIILOT automation is a graph-shaped workflow specification. It is composed of nodes, edges, connector contracts, safety gates, validation results, simulation output, and setup enrichment.

The automation is generated from natural language, then saved to the workspace so it can be reviewed in Workflows and inspected visually in Canvas.

Automation fields

Name and summary describe what the workflow does.
Real need captures the operating problem beneath the original wording.
Stated request preserves what the user literally asked for.
Recommended status indicates whether PIILOT should clarify, draft, modify, or not build.
Risk level indicates low, medium, or high operational risk.
Success metric describes how the workflow should be evaluated.
Nodes and edges define the workflow graph.
Validation, simulation, setup, variables, and time estimates support safe review.

Automation object anatomy

flowchart TD
  A[Workflow Spec]
  A --> B[Intent layer]
  B --> B1[Name, summary, real need]
  B --> B2[Stated request and success metric]
  A --> C[Graph layer]
  C --> C1[Nodes]
  C --> C2[Edges]
  A --> D[Execution layer]
  D --> D1[Connector contracts]
  D --> D2[Safety gates]
  A --> E[Review layer]
  E --> E1[Validation]
  E --> E2[Simulation]
  E --> E3[Setup and variables]