Give the Specialist a Flight Envelope

Design a bounded specialist for the approved mission. Specify its authorized users, accepted inputs, required starting data, permitted tools, accessible systems, data boundaries, allowed actions, prohibited actions, output schema, evidence contract, time and cost limits, and audit events.

Identify every action that is read-only, reversible, consequential, or destructive. Place explicit human-in-the-loop approval before external writes, permission changes, deployments, deletions, financial commitments, communications, or other consequential actions.

Define behavior for missing data, ambiguous instructions, conflicting evidence, tool failure, expired credentials, partial completion, and attempted scope expansion. The specialist must state what it could not verify rather than filling gaps with plausible text.

Present the design for Pilot in Command approval before implementation.