Delegation brief

Use one brief per independent assignment. Set permissions in the runtime as well when the access boundary needs enforcement.

• Question: The specific question this child should answer.
• Assigned material: Exact documents, repositories, ranges, or files.
• Expected coverage: What must receive a reviewed/empty/excluded/error disposition?
• Mode: Read-only research, review, test, or an explicitly scoped implementation.
• Allowed actions: Tools and changes within this assignment.
• Ownership: Files or separate checkout owned by this child; integration owner.
• Publication boundary: What may appear in the returned publication candidate?
• Evidence: Locations, revisions, commands, or observations required for conclusions.
• Return format: Findings, limitations, disagreements, coverage, and next question.
• Budget and stopping rule: The useful bound and what to return when it is reached.

Parent integration note

Reconcile all coverage against the original assignment. Check the evidence behind conclusions. Keep unresolved disagreements visible. Review the final change as a whole after integrating children. Record failures and missing access as coverage gaps; do not infer that silence means success.