Give the Specialist a Flight Envelope

Define the evidence contract for every answer or action produced by this specialist.

Require the output to report the selected scope; source files, tables, APIs, or tools used; passages or columns examined; filters, joins, grouping, and calculations; document or row counts when available; missing or conflicting evidence; assumptions; limitations; and the human approvals obtained.

Design a structured response format that supports both a readable explanation and machine-verifiable provenance. Include rules for neutral language, citations, incomplete results, unsupported conclusions, and refusing to cross the selected project or data boundary.

Provide one complete example, one example with missing evidence, and one example that must stop for human review.