E.17.AUD.OOTD:5.6 - Deliberately sectioned multi-subject review packet

A release-readiness group needs one packet for one meeting. The packet contains three clearly headed sections:

1. Interface-boundary options — compares two architecture alternatives.
2. Incident evidence — summarizes the observations that discriminate between those alternatives.
3. Rollout constraints — states constraints the later approval decision must respect, without assigning work or granting approval.

The local one-subject heuristic does not force three documents. The packet has one honest umbrella subject—the evidence and constraints needed to review the interface-boundary choice—and one bounded use: inform the review, not approve rollout. Keeping the three section-level subjects together avoids navigation and synchronization cost, while the headings prevent their different moves from masquerading as one claim.

An unsectioned version is rejected because readers cannot see the subject and move changes. A short narrative with only one small shift may instead declare that transition. Separate documents become the least-cost choice when the rollout section starts assigning responsibility, serves another audience, needs independent reuse, or becomes an approval input with its own reliance boundary.