E.17.AUD.OOTD:1 - Problem frame

Use the examples as alternatives. The quick checks, ordinary declaration, optional diagnostic, heavier extension, and worked slices are alternative aids for one publication unit, not a required sequence. One case may stop after the declaration; another may reopen when outside observations change the honest concern, claim, or downstream use; another may use the neighboring pattern whose instructions fit once approval, work, reliance, or another question becomes primary.

Teams repeatedly write one publication unit that begins with one primary subject and ends with another subject, concern, carried move, or downstream use while still sounding like one unchanged text.

Typical moments include:

• an architecture note that starts about a system boundary and ends by directing rollout work;
• an operations review note that starts about an incident episode and ends as an action approval;
• a requirements or policy note that starts about an exact entity and ends about its carrier or document status;
• an episteme-publication-heavy note that starts about one pattern section or publication form and ends about wider architecture strategy;
• a comparison sheet that starts about one subject and quietly shifts into engineering-process, approval, work, or reliance pressure.

That interpretation instability is usually not caused by one bad sentence alone. It is caused by one whole publication unit no longer holding a stable answer to what it is about, which concern it foregrounds, what move it carries, how readers may use it, and what wider work still stays outside.