E.17.AUD.OOTD:4.3 - Ordinary declaration and optional diagnostic
The complete ordinary result is one natural-language declaration from which a reader can recover:
- the bounded publication unit;
- its primary subject;
- the claim or communicative move it carries; and
- the wider work or use that remains outside.
One sentence or two short sentences are enough. For example:
This review note compares the interface-boundary options under the current incident evidence. Rollout responsibility and approval remain outside this note.
Do not require a separate card, record, identifier, table, or field set when that declaration is already clear. Add an explicit transition only when the unit actually changes subject, concern, carried move, or downstream use. Name a neighboring pattern only when one concrete unresolved question remains and that pattern supplies the needed instruction; an empty transition row or speculative neighbor lookup adds no value.
When the sentence is hard to write or a reviewer suspects a hidden shift, use these six prompts privately as an optional diagnostic:
| Prompt | Diagnostic question |
|---|---|
| 1 | What single publication unit am I asking people to read as one bounded unit? |
| 2 | What is its primary subject: what is it mainly about? |
| 3 | Which concern is foregrounded, and what claim or communicative move does the unit carry? |
| 4 | What downstream use is permitted or blocked, and what wider work is outside this unit? |
| 5 | Has subject, concern, carried move, downstream use, or the exact C.2.1 entity participant changed, and is that exact change named? |
| 6 | If this remains unstable after local repair, what exact question remains, and which neighboring pattern supplies the needed repair or boundary? |
These prompts guide attention; they are not six publication rows. Discard the diagnostic once it has yielded the clear ordinary declaration.
If local repair is still enough, go back to E.17.AUD.LHR (Local Head Restoration) instead of adding more structure here.
If the unit remains one publication unit but a claim or downstream use depends on the neighboring-boundary claim kind, misuse risk, or cross-interpretation ambiguity, use the heavier extension as the assurance section.
If the same unit is already stable as one primary subject, one carried move, and one outside-work boundary, and the remaining question is one bounded comparative review move over already available source epistemes or publications, apply E.17.ID.CR rather than thickening the declaration.
If the unit cannot stay stable even after local repair, reopen the unit or apply the neighboring pattern that answers the exact remaining question; do not stack more fields onto the declaration.