Assignment Composition

You are turning each named dimension into a self-contained autonomous-work-assignment envelope. After this phase, each envelope must be dispatch-ready — a recipient subagent reads only that envelope and executes, without needing to come back asking questions.

The envelope standard

Every assignment envelope MUST contain all of the following sections. Missing any section means the envelope is incomplete and the no-pingpong gate will reject it.

1. Identifier

A short slug: assignment-NNN-<dimension-slug>. Stable across the rest of the protocol.

2. Scope (positive)

What the recipient is being asked to produce. One paragraph. Concrete, not abstract. If you cannot write this in one paragraph, the dimension is probably not yet pruned enough.

3. Scope (negative)

What the recipient is not being asked to produce. Lists adjacent work this assignment explicitly omits. This is where you preempt the "should I also do X?" question.