Trust & Safety

Alpha limitations

How to use PIILOT responsibly while the product is in alpha.

PIILOT is currently in alpha. The product is designed to become a production-grade automation and agent builder, but alpha users should treat generated workflows as reviewable drafts until configured, validated, tested, and approved.

The safest alpha workflow is to generate, inspect, connect, validate, simulate, and refine before relying on an automation in live operations.

Use extra review for

Customer-facing messages or replies.
Financial, billing, payroll, legal, HR, or compliance workflows.
Destructive actions such as deleting, overwriting, or bulk-updating records.
Actions that trigger external notifications or commitments.
Workflows that use broad integration scopes or shared service accounts.
Any workflow where an incorrect action would create operational, legal, or reputational risk.

Safe alpha workflow

flowchart TD
  A[Generate draft]
  A --> B[Inspect graph]
  B --> C[Check validation notes]
  C --> D[Configure integrations]
  D --> E[Review mappings]
  E --> F[Confirm approval gates]
  F --> G[Test with safe data]
  G --> H[Refine]
  H --> I[Use in controlled operations]

Production rule

Do not run a generated automation against sensitive or irreversible systems until the workflow, permissions, mappings, approval gates, and expected outputs have been reviewed.