#AuthoredUnitDiscipline — umbrella routing for one authored unit that is starting to drift

Pattern E.17.AUD · Stable Part E - The FPF Constitution and Authoring Guides

Placement. First umbrella routing pattern for one authored-readable unit whose burden may still narrow into local head repair, whole-unit object-of-talk stabilization, bounded comparison, or a neighboring non-authored-unit pattern.

Builds on. C.2.2a, A.16.0, A.7, E.10, F.18, E.14, E.19.

Coordinates with. E.17.AUD.LHR, E.17.AUD.OOTD, E.17.ID.CR, E.17.EFP, A.6.3, A.6.3.CR, A.6.3.RT, A.15, A.20, A.21.

Plain-name. Keep one authored unit stable enough to read honestly.

One-line summary. AuthoredUnitDiscipline is the umbrella pattern for notes, memos, sheets, tables, screens, and short sections that start to drift as if they were still about one unchanged thing. It helps the reader decide whether the real burden is still local head repair, whole-unit object-of-talk stabilization, bounded comparison over already stable material, or a neighboring non-authored-unit pattern.

Governed object in plain terms. The governed object is the authored unit itself: one note, memo, sheet, table, screen, or short section that people are expected to read as one readable unit. The primary object of talk is whatever that unit is mainly about. Keep those levels separate: this umbrella governs the unit as a readable unit, while the narrower whole-unit branch checks whether that unit still keeps one stable primary object of talk by value.

Minimal lens in plain terms. Use a four-part reading: one governed unit, one primary object of talk, one carried move over that object, and one outside-work boundary. The outside-work boundary usually needs one light exit type too: neighboring pattern move, downstream authority/deontic use, or ongoing workflow/process continuation. If any of those shifts quietly, the unit is no longer honest enough to read as one unchanged authored unit.

Local working vocabulary.

• governed unit = the note, memo, sheet, table, screen, or short section being kept honest as one unit;
• primary object of talk = what that unit is mainly about right now;
• carried move = what that unit is actually doing over that primary object of talk;
• outside-work boundary = stronger work or exit class that still remains outside the unit.

Use this when. Use this pattern when one note, memo, sheet, screen, table, or short section is no longer trustworthy as one stable reading unit. Use it when people keep arguing about a paragraph, but the real question is simpler: is this still a local head problem, a whole-unit drift problem, a bounded comparison problem, or a neighboring pattern altogether?

First-minute working moment. A memo starts by naming one thing, then quietly starts doing something else with it, or quietly becomes about a different thing. One reviewer wants to repair one vague local word. Another wants to rewrite the whole memo. A third person thinks the real burden is already a bounded comparison or a downstream decision text. You need one honest routing surface before the unit gets patched in three incompatible ways.

What goes wrong if you miss this. Teams keep fixing sentences without agreeing on the governed unit. Local head repair gets asked to carry whole-unit stabilization. Whole-unit stabilization gets asked to carry bounded comparison. Comparison gets mistaken for approval or rollout. A stronger-looking format gets mistaken for stronger authority. The text stays readable enough to circulate, but no longer honest enough to trust.

What this buys you in practice. It gives one quick umbrella check before the draft widens or reroutes. Teams can decide earlier whether to stay local, stabilize the whole authored unit, hand over to bounded comparison, or leave the authored-unit family entirely for a more honest neighboring pattern or downstream text.

Not this pattern when. This is not the right pattern when:

• one pressured local head is still the only real defect and Local Head Restoration is enough;
• the authored unit is already stable and the real burden is one bounded comparison over already pinned material;
• the main burden is explanation classification over an existing face, view/face/carrier discipline, or another neighboring semio pattern rather than authored-unit stability;
• the text is already being used to approve, direct, assign, or adjudicate work and should move into the more honest downstream decision or action surface.

Primary working reader. The first working reader is an author or reviewer who needs to stop one memo, note, sheet, table, screen, or short section from quietly changing what it is about or what it is licensing. Architects, managers, and program leads are important secondary readers when they need the same reroute signal, but they are not the first-minute reader for this opening surface.

Quick kind stack. AuthoredUnitDiscipline names the first umbrella routing pattern for one drifting authored unit. Local Head Restoration is the narrower branch when one pressured head is still the primary defect. AuthoredUnit Object-of-Talk Discipline is the narrower branch that owns the whole-unit law/check burden once the unit itself must keep one stable primary object of talk, one carried move, and one outside-work boundary by value. ComparativeReading is the neighboring branch when the authored unit is already stable and the primary move is bounded comparison over already available material. This umbrella helps readers route one authored unit honestly; it does not by itself decide publication form, carrier choice, or downstream authority.

Quick recognition matrix.

Recognition-surface note. The opening card above is the quick recognition surface. The sections below carry the heavier assurance surface: burden typing, branch and reroute discipline, worked slices, and SoTA/domain grounding.

Anti-workflow note. The branch checks, recognition matrix, and worked slices below are routing aids for one authored unit under review. They are not a fixed lifecycle and not a promise that every lawful case moves through one mandatory sequence.

#Keywords

• authored unit
• primary object of talk
• carried move
• outside-work boundary
• umbrella routing
• authored-unit stability.

#Relations

#Content

#Problem frame

Anti-workflow note. The branch checks, recognition matrix, and worked slices below are routing aids for one authored unit under review. They are not a fixed lifecycle and not a promise that every lawful case moves through one mandatory sequence.

This pattern is for real authored units used in review, design, architecture, coordination, onboarding, and similar reading situations. It is for the moment when one authored unit still sounds like one unchanged note even after its object of talk, carried move, or stronger downstream force has already changed.

The recurring defect family is simple:

• one authored unit begins as if it were about one thing;
• the unit then quietly changes what it is about, what move it is making, or what still remains outside;
• the surrounding team starts repairing different defect families at once because nobody first named the real authored-unit burden.

Typical moments include:

• a semio-heavy note where one broad head starts carrying more load than the sentence restored;
• an architecture or status memo that starts about one bounded object and ends by sounding like rollout or approval work;
• a comparison sheet that is already stable enough locally, but is still being overworked as if it needed full authored-unit stabilization;
• an onboarding aid, dashboard card, or review note that quietly drifts into explanation, policy, or decision language while still sounding like one unchanged unit.

#Problem

Without a named umbrella discipline:

1. teams repair local wording when the real defect is whole-unit drift;
2. teams open whole-unit stabilization when the real defect is still one pressured local head;
3. teams keep thickening an authored-unit repair when the real burden is already bounded comparison;
4. teams mistake note/sheet/table/screen language for different governed objects when the real object is still one authored unit in different surface forms;
5. teams over-attribute workflow, approval, or rollout force to a text that never honestly became that kind of unit.

#Forces

#Solution

AuthoredUnitDiscipline is the first routing surface for one unstable authored unit.

It asks what the unit is mainly about, what move it is carrying, and which narrower branch or neighboring pattern should actually govern the case.

#Minimum lawful reading

A locally lawful reading keeps four things visible enough to inspect by value:

• one governed unit;
• one primary object of talk;
• one carried move over that object;
• one outside-work boundary, with one light exit type when that distinction matters: neighboring pattern move, downstream authority/deontic use, or ongoing workflow/process continuation.

If the authored unit changes any of those four without saying so, the unit has already drifted even when the sentences still look polished.

#Umbrella burden vs branch burden

AuthoredUnitDiscipline is the first routing surface for one unstable authored unit. Its job is to decide whether the burden stays local with Local Head Restoration, moves into whole-unit stabilization through AuthoredUnit Object-of-Talk Discipline, hands over to ComparativeReading, or leaves the authored-unit family altogether.

It does not re-own the narrower whole-unit law/check burden that already belongs to AuthoredUnit Object-of-Talk Discipline once the active question becomes: can this one unit still keep one stable primary object of talk, one carried move, and one outside-work boundary by value?

#Inherited dynamic frame

This umbrella governs authored-readable-unit stability over the inherited lineage/move frame already carried by C.2.2a / A.16.0. It is about how one authored unit speaks about that inherited moving thing or move. It is not a standalone theory of documents, carriers, or publication forms.

#Kind and boundary

This pattern governs one authored unit as a readable unit. It does not treat that unit as automatically identical with:

• the primary object of talk inside the unit;
• a publication face;
• a carrier or evidence object;
• a view or viewpoint;
• a workflow stage;
• a downstream approval, action, or authority surface.

Those may become relevant neighboring concerns, but they are not the burden being governed here just because the same note, sheet, or screen happens to mention them.

#Ordinary working card

Use this seven-row card before you widen the repair:

#Branch and reroute rule

• If row 5 still points to one pressured local head, stay with Local Head Restoration.
• If row 5 shows that the whole authored unit still cannot keep one stable primary object of talk, one carried move, and one outside-work boundary visible, move to AuthoredUnit Object-of-Talk Discipline.
• If the authored unit is already stable enough and the real move is bounded comparison over already available material, hand to ComparativeReading.
• If the main burden is explanation classification over an existing face, move to the more honest neighboring explanation pattern rather than keeping the case inside authored-unit stability by inertia.
• If the real burden is publication form, bridge work, or downstream authority/action, leave the authored-unit family and move to the more honest neighboring pattern or downstream text.

#Local naming and lexical-governance rule

Treat ordinary labels such as note, memo, sheet, table, screen, review, and status as surface-form clues, not as self-authenticating object kinds.

Working rule:

• if one pressured local head is doing most of the semantic work, repair that head first through Local Head Restoration;
• if the head is not the real issue, keep the authored unit stable at whole-unit level instead of hiding the drift under one more qualifier;
• do not let cleaner or more formal wording stand in for stronger authority, stronger comparison basis, or stronger downstream warrant.

#Modeling-basis surfacing rule

If the primary object of talk or the carried move depends on a modeling basis, surface that basis briefly in the unit or reroute the case to a heavier surface that can carry it honestly. Do not let a formally loaded case pretend it is only prose hygiene.

#Local assurance dock

When the authored unit carries load-bearing explanation, comparison, or downstream-use pressure, keep five quick checks visible enough to audit:

• evidence/source-pin status when the unit leans on already available material;
• current admissible use and forbidden stronger uptake;
• whether this unit is the canonical locus or a derivative helper surface;
• any load-bearing modeling basis;
• and that the assurance surface only tightens the opening recognition claim rather than silently broadening it into stronger authority.

#Worked slices

#Local-head case

A semio note keeps saying this review and this interpretation, but nobody can tell what kind of thing those heads name here. The rest of the governed unit is still locally stable once the head is repaired. The honest move is not broad authored-unit stabilization. It is Local Head Restoration.

#Whole-unit drift case

A memo starts about one bounded architecture question over an inherited lineage or move, then drifts into wider rollout or approval language without declaring the transition. Repairing one sentence does not stabilize the governed unit because the primary object of talk and the carried move have both widened. The honest move is AuthoredUnit Object-of-Talk Discipline.

#Stable-unit comparison case

A comparison sheet already keeps one stable primary object of talk and one clear outside-work boundary, but the team is using authored-unit drift language because the comparison is contentious. The honest move is not more authored-unit stabilization. It is ComparativeReading.

#Explanation-laundering case

An onboarding explainer starts from one stable source-pinned note, but then the simplified prose begins to sound like canonical assurance or policy. The authored unit may still be readable, yet the main burden is no longer authored-unit stability. The honest move is to leave this umbrella and route to the neighboring explanation/faithfulness discipline.

#Downstream-authority case

A status card starts as one bounded summary of progress, then quietly becomes the place where people infer approval, assignment, or go/no-go force. The problem is no longer only authored-unit stability. The honest move is to stop treating the card as if it were still only one neutral note and route to the downstream authority or action surface.

#Compact scenario and anti-case pack

Use this quick contrast set when the first reading is still foggy:

#Common Anti-Patterns and How to Avoid Them

#Consequences

• You slow down long enough to name the real authored-unit burden before patching the draft.
• You reduce pointless escalation from one pressured local head into a whole-unit rewrite.
• You reduce the opposite failure too: trying to solve whole-unit drift with one more qualifier on the same local head.
• You keep neighboring authored-unit branches and non-authored-unit patterns explicit instead of letting one umbrella name quietly absorb them.
• You make it harder for clearer prose, stronger formatting, or wider circulation to masquerade as stronger authority.

#Rationale

AuthoredUnitDiscipline is worth stating explicitly because local head repair and whole-unit object-of-talk stabilization are both already real burdens, but authors and reviewers still need one umbrella surface that says when the case is local, when it is whole-unit, when it is already bounded comparison, and when it has left the authored-unit family entirely.

The pattern stays intentionally narrow. It does not turn every authored-unit problem into publication design or downstream authority work. Its job is simpler and more load-bearing: keep one authored unit honest enough that readers can still tell what it is mainly about, what it is doing, and what stronger work remains outside.

#SoTA-Echoing

Claim 1. Best-known current architecture-description practice keeps the entity of interest and the description expressing it explicit enough that one document does not silently change its concern while still sounding continuous.

Practice / source / alignment / adoption. ISO/IEC/IEEE 42010:2022 distinguishes the architecture of an entity from the architecture description that expresses it and requires explicit structure and concern handling. AuthoredUnitDiscipline adopts that explicit concern discipline, adapts it from architecture descriptions to authored units more broadly, and rejects silent object-of-talk drift inside one readable unit. For a reviewer or architect, this is the practical guard behind worked slices 5.2 and 5.3: one authored unit must not quietly shift concern and still be treated as one unchanged note.

Claim 2. Best-known current information-for-use practice treats user-facing units as purpose-bound, structured information rather than as loose bundles that can mix explanation, instruction, warning, and decision force by convenience.

Practice / source / alignment / adoption. IEC/IEEE 82079-1:2019 requires information for use to be purpose-directed, structured, and evaluated for usability. AuthoredUnitDiscipline adopts purpose-bound authored units and explicit outside-work boundaries, adapts that discipline from information-for-use to notes, memos, sheets, tables, and screens, and rejects the shortcut where a clearer or stronger-looking unit is treated as if it had already become approval, policy, or action text. For a manager or operator, this is the practical guard behind worked slices 5.4 and 5.5: better explanatory form does not itself mint stronger downstream force.

Claim 3. Best-known current pattern-writing and pattern-validation practice keeps patterns tied to recognisable situations, explicit problem/solution/consequence structure, and reviewable rationale rather than elegant internal naming alone.

Practice / source / alignment / adoption. Iba (2021) and Riehle et al. (2020) both treat pattern writing and validation as requiring recognisable situations, explicit structure, and reviewable reasoning rather than only elegant naming. AuthoredUnitDiscipline adopts worked slices, recognisable entry cues, and explicit reroute discipline, adapts those expectations to authored-unit stability work, and rejects a pattern text that is cleanly labeled but domain-thin or reader-thin. For the current working reader, this is the practical guard behind the recognition surface and slices 5.1 through 5.5: the pattern should be usable before one has to reconstruct the surrounding rationale from scratch.

Local stance. The current SoTA claim is narrow. This pattern is not claiming one universal theory of documents. It claims a smaller and more practical point: one authored unit stays trustworthy only when its primary object of talk, carried move, and outside-work boundary remain explicit enough for cold readers to recover, and when neighboring burdens are rerouted rather than hidden.

#Conformance Checklist

1. CC-AUD-1 — One governed authored unit is explicit. The case names one note, memo, sheet, table, screen, or short section as the governed unit rather than letting surface-form labels stand in for the governed object.
2. CC-AUD-2 — Primary object of talk and carried move are explicit enough to route the case. The case keeps visible what the unit is mainly about and what move it is carrying over that object right now.
3. CC-AUD-3 — Outside-work boundary is explicit. The case states what stronger work still remains outside the governed unit, including neighboring pattern move, downstream authority/deontic use, or ongoing workflow/process continuation when that distinction matters.
4. CC-AUD-4 — The active burden family is named honestly. The case makes explicit whether the live burden is local head repair, whole-unit object-of-talk stabilization, bounded comparison, or another neighboring pattern rather than patching several burdens at once under one vague stability claim.
5. CC-AUD-5 — Branch and reroute choice is explicit. When the burden belongs with Local Head Restoration, AuthoredUnit Object-of-Talk Discipline, ComparativeReading, a neighboring explanation/faithfulness pattern, or a downstream authority/action surface, that route is explicit rather than hidden inside umbrella wording.
6. CC-AUD-6 — Surface-form labels do not launder object kind or authority. note, memo, sheet, table, screen, and similar labels remain surface-form clues and do not silently change the governed unit or mint stronger downstream force.
7. CC-AUD-7 — Load-bearing modeling basis is surfaced or rerouted. If the primary object of talk or carried move depends on a modeling basis, that basis is surfaced briefly enough for review or the case is rerouted to a heavier surface that can carry it honestly.
8. CC-AUD-8 — Clearer prose does not silently strengthen use. Readability, formatting, and wider circulation may improve the unit, but they do not by themselves turn the unit into approval, policy, assignment, or action text.

#Relations

• Builds on: A.7, E.10, F.18, E.14, E.19
• Coordinates with: Local Head Restoration, AuthoredUnit Object-of-Talk Discipline, ComparativeReading, neighboring explanation/faithfulness discipline, and downstream authority/action texts when the unit stops being only a readable authored unit
• Impact radius: primary touch is the authored-unit stability family; secondary touch is adjacent explanation, comparison, publication, and downstream authority routing when the authored unit can no longer stay honest inside this umbrella

#E.17.AUD:End