Pilot Requirements

A Compex pilot needs enough context to define a governed execution boundary. The requirements below help teams avoid vague pilots and focus on a workflow that can be reviewed.

Required inputs

• Business owner and technical owner.
• Data owner and processor roles.
• DPO / legal reviewer or equivalent review owner.
• Workflow type: Train, Analyze, or Serve.
• Dataset or synthetic substitute.
• Allowed workload or service.
• Output expectations and review rules.
• Evidence records required for decision-making.

What this means

For business readers, requirements protect the pilot from becoming a broad platform evaluation with no decision point. Scope is what makes approval possible.

Current status

Compex can start with a discovery call and convert the above inputs into a pilot plan.

Limitations

Missing legal, data, or technical ownership can block a pilot. Compex cannot compensate for unclear authority between the participating teams.