#AuthoredUnitDiscipline - problem-pressure classification for one authored-readable unit with unstable described-entity or carried-move reading

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

#About this pattern

This is a generated FPF pattern page projected from the published FPF source. It is canonical FPF content for this ID; it is not a fpf-memory product feature page.

#How to use this pattern

Read the ID, status, type, and normativity first. Use the content for exact wording, the relations for adjacent concepts, and citations to keep active work grounded without pasting the whole specification.

Placement. First problem-pressure classification pattern for authored-readable units whose active pressure must be assigned to one of the existing governing patterns or authority-source exits: local lexical-head repair, whole-unit primary-described-entity 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 problem-pressure classification discipline for notes, memos, sheets, tables, screens, and short sections whose primary-described-entity reading, carried publication move, or outside work/reliance boundary has become unstable while the unit still looks unchanged. It helps the reader decide whether the active problem pressure is still local lexical-head repair, whole-unit primary-described-entity stabilization, bounded comparison over already stable source publications, or a neighboring non-authored-unit pattern.

Governed authored unit in plain terms. The governed unit is the authored-readable publication unit itself: one note, memo, sheet, table, screen, or short section that people are expected to read as one readable unit. The primary described entity is the U.Entity / U.Holon / episteme target that the unit is mainly about. Keep those roles separate: this pattern governs the unit as a readable unit, while the whole-unit repair pattern checks whether that unit still keeps one stable primary described entity by value.

Minimal lens in plain terms. Use a four-part reading: one governed unit, one primary described entity, one carried publication move over that described entity, and one outside work/reliance boundary. The outside work/reliance boundary usually needs one light exit type too: neighboring pattern move, downstream claim/effect, or ongoing engineering-process continuation. If any of those reading relations changes 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 described entity = the U.Entity / U.Holon / episteme target that the unit is mainly about right now;
• carried publication move = the claim, reading, comparison, explanation, or downstream claim/effect move that the unit performs over that primary described entity;
• outside work/reliance boundary = downstream U.Work, U.WorkPlanning, decision, gate, or reliance claim that still remains outside the unit;
• downstream claim/effect = an approval, assignment, go/no-go, gate, work, or reliance claim/effect that readers infer from the unit but that belongs outside this pattern unless explicitly assigned to its governing pattern or authority source. A.6.P unpacking of overloaded local words. This pattern does not use route, branch, head, or unit as hidden ontology. Use these roles instead:
• local lexical head = the head word or phrase inside one load-bearing sentence or heading, such as review, reading, interpretation, note, or text; it is not an FPF pattern head, not a package-family head, and not a language-state branch;
• problem-pressure family = the current defect family: local lexical-head repair, whole-unit primary-described-entity stabilization, bounded comparison, explanation/representation/coarsening/retargeting pressure, or downstream decision/gate/work/reliance pressure;
• governing pattern or authority-source exit = the named pattern or authority source that already governs the current pressure;
• authored-unit repair family = the relation among E.17.AUD, E.17.AUD.LHR, E.17.AUD.OOTD, and neighboring comparison/explanation patterns; it is not a runtime path and not a transduction workflow;
• presentation-form label = note, memo, sheet, screen, and similar form words; these are only form clues until the governed authored unit and primary described entity are restored.

When any of those roles is load-bearing, record the selected role in the working card rather than polishing the sentence with another generic word.

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 lexical-head problem, a whole-unit reading-stability problem, a bounded comparison problem, or a neighboring pattern altogether?

First-minute working moment. A memo starts by naming one described entity, then quietly makes a different publication move over it, or quietly becomes about a different described entity. One reviewer wants to repair one vague local lexical head. Another wants to rewrite the whole memo. A third person thinks the active problem pressure is already a bounded comparison or a downstream decision/reliance publication. You need one honest problem-pressure classification check 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 lexical-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 more polished or official-looking format gets mistaken for downstream claim/effect. The text stays readable enough to circulate, but no longer honest enough to trust.

What this buys you in practice. It gives one quick problem-pressure classification check before the draft widens or needs assignment to another governing pattern or downstream publication. Teams can decide earlier whether to stay local, stabilize the whole authored unit, move to bounded comparison, or leave the authored-unit family entirely for a more honest neighboring pattern or downstream publication.

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

• one pressured local lexical head is still the only real defect and Local Head Restoration is enough;
• the authored unit is already stable and the active problem pressure is one bounded comparison over already pinned source publications;
• the main problem pressure 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, gate, work, or reliance publication.

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 its primary described entity, carried publication move, or downstream claim/effect. Architects, managers, and program leads are important secondary readers when they need the same governing-pattern/source boundary signal, but they are not the first-minute reader for this opening recognition surface.

Quick kind stack. AuthoredUnitDiscipline classifies the current problem pressure for one authored-readable unit. E.17.AUD.LHR governs the local lexical-head repair case: one word or phrase inside the unit is carrying too much semantic load while the unit otherwise stays stable. E.17.AUD.OOTD governs the whole-unit stabilization case: the same authored unit no longer keeps one primary described entity, one carried publication move, and one outside work/reliance boundary visible. E.17.ID.CR governs the bounded-comparison case once the authored unit is stable and the primary move is comparison over available source publications. Other explanation, representation, bridge, gate, approval, or work/reliance pressures belong to their own governing patterns or authority sources. This pattern names that classification; it does not create a path, call chain, workflow, or new runtime control path.

Quick recognition matrix.

Recognition-surface note. The opening card above is the quick recognition surface. The sections below carry the heavier assurance surface: problem-pressure typing, A.6.P unpacking, governing-pattern/source boundary decisions, worked slices, and SoTA/domain grounding.

Anti-single-sequence note. The problem-pressure checks, recognition matrix, and worked slices below are problem-pressure classification aids for one authored unit under review. They are not a fixed engineering process and not a promise that every admissible case moves through one mandatory sequence.

#Keywords

• authored unit
• primary described entity
• carried move
• outside-work boundary
• problem-pressure classification
• authored-unit stability.

#Relations

#Content

#Problem frame

Anti-single-sequence note. The problem-pressure checks, recognition matrix, and worked slices below are problem-pressure classification aids for one authored unit under review. They are not a fixed engineering process and not a promise that every admissible 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 described entity, carried publication move, or downstream claim/effect has already changed.

The recurring defect family is simple:

• one authored unit begins as if it were about one described entity or claim target;
• the unit then quietly changes its primary described entity, carried publication move, or outside work/reliance boundary;
• the surrounding team starts repairing different defect families at once because nobody first named the active authored-unit problem pressure.

Typical moments include:

• a semio-heavy note where one broad local lexical head starts carrying more load than the sentence restored;
• an architecture or status memo that starts about one bounded described entity or question 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 shifts into explanation, policy, or decision language while still sounding like one unchanged unit.

#Problem

Without a named authored-unit problem-pressure classification discipline:

1. teams repair local wording when the real defect is whole-unit reading instability;
2. teams open whole-unit stabilization when the real defect is still one pressured local lexical head;
3. teams keep thickening an authored-unit repair when the active problem pressure is already bounded comparison;
4. teams mistake note/sheet/table/screen language for different governed unit kinds when the real governed unit is still one authored unit in different presentation forms;
5. teams over-attribute engineering-process, approval, or rollout claim/effect to a text that never honestly became that kind of unit.

#Forces

#Solution

AuthoredUnitDiscipline is the first problem-pressure classification check for one authored unit whose reading is unstable.

It asks what the unit is mainly about, what move it is carrying, and which governing pattern or authority-source exit owns the case.

#Minimum admissible reading

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

• one governed unit;
• one primary described entity;
• one carried publication move over that described entity;
• one outside work/reliance boundary, with one light exit type when that distinction matters: neighboring pattern move, downstream claim/effect, or ongoing engineering-process continuation.

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

#Branch-selection problem pressure vs branch requirement

AuthoredUnitDiscipline is the first problem-pressure classification check for one authored unit whose reading is unstable. Its job is to name the current problem-pressure family and then assign the case to the governing pattern or authority-source exit that already owns that family: E.17.AUD.LHR for local lexical-head repair, E.17.AUD.OOTD for whole-unit stabilization, E.17.ID.CR for bounded comparison, or another neighboring pattern when the pressure has left authored-unit stability.

It does not re-own the narrower whole-unit admissibility/check requirement that already belongs to AuthoredUnit Primary Described-Entity Discipline once the active question becomes: can this one unit still keep one stable primary described entity, one carried publication move, and one outside work/reliance boundary by value?

#Inherited dynamic frame

This pattern governs the problem-pressure classification for 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 described entity inside the unit;
• a publication face;
• a carrier or evidence carrier;
• a view or viewpoint;
• an engineering-process stage;
• a downstream decision, gate, work, or reliance publication.

Those may become relevant neighboring concerns, but they are not the problem pressure 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 exit rule

• If row 5 still points to one pressured local lexical head, stay with Local Head Restoration.
• If row 5 shows that the whole authored unit still cannot keep one stable primary described entity, one carried publication move, and one outside work/reliance boundary visible, move to AuthoredUnit Primary Described-Entity Discipline.
• If the authored unit is already stable enough and the real move is bounded comparison over already available source publications, move to ComparativeReading.
• If the main problem pressure 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 active problem pressure is publication form, bridge work, or downstream claim/effect, leave the authored-unit family and move to the more honest neighboring pattern or downstream publication.

#Local naming and lexical-governance rule

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

Working rule:

• if one pressured local lexical head is doing most of the semantic work, repair that local lexical head first through Local Head Restoration;
• if the local lexical head is not the real issue, keep the authored unit stable in the whole-unit stabilization pattern instead of hiding the reading shift under one more qualifier;
• do not let cleaner or more formal wording stand in for unsupported downstream claim/effect or unsupported comparison basis.

#Modeling-basis surfacing rule

If the primary described entity or the carried publication move depends on a modeling basis, publish that basis briefly in the unit or move the case to a heavier publication form or neighboring pattern 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 claim/effect pressure, keep five quick checks visible enough to audit:

• evidence/source-pin status when the unit leans on already available source publications;
• current admissible reliance/work reading and forbidden unsupported decision/work/gate claim;
• whether this unit is the canonical locus or a derivative helper publication;
• any load-bearing modeling basis;
• and that the assurance surface only tightens the opening recognition claim rather than silently broadening it into downstream claim/effect.

#Worked slices

#Local-head case

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

#Whole-unit reading-shift case

A memo starts about one bounded architecture question over an inherited lineage or move, then shifts into wider rollout or approval language without declaring the transition. Repairing one sentence does not stabilize the governed unit because the primary described entity and the carried publication move have both widened. The honest move is AuthoredUnit Primary Described-Entity Discipline.

#Stable-unit comparison case

A comparison sheet already keeps one stable primary described entity and one clear outside work/reliance boundary, but the team is using authored-unit instability 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 problem pressure is no longer authored-unit stability. The honest move is to leave authored-unit stability and move to the neighboring explanation/faithfulness discipline.

#Downstream decision/reliance 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 claim/effect. 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 move to the downstream decision, gate, work, or reliance publication.

#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 active authored-unit problem pressure before patching the draft.
• You reduce pointless escalation from one pressured local lexical head into a whole-unit rewrite.
• You reduce the opposite failure too: trying to solve whole-unit reading instability with one more qualifier on the same local lexical head.
• You keep neighboring authored-unit repair patterns and non-authored-unit patterns explicit instead of letting one broad problem-pressure classification name quietly absorb them.
• You make it harder for clearer prose, official-looking formatting, or wider circulation to masquerade as downstream claim/effect.

#Rationale

AuthoredUnitDiscipline is worth stating explicitly because local lexical-head repair and whole-unit primary-described-entity stabilization are both already real problem pressures, but authors and reviewers still need one problem-pressure classification check 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 decision/gate/work/reliance 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, which carried publication move it makes, and which downstream U.Work, U.WorkPlanning, decision, gate, or reliance claim 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 primary-described-entity shift 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/reliance effect 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/reliance boundaries, adapts that discipline from information-for-use to notes, memos, sheets, tables, and screens, and rejects the shortcut where a clearer or official-looking unit is treated as if it had already become approval, policy, gate, work, or reliance 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 downstream claim/effect.

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 governing-pattern/source boundary 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 described entity, carried publication move, and outside work/reliance boundary remain explicit enough for cold readers to recover, and when neighboring problem pressures are moved to their governing patterns 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 presentation-form labels stand in for the governed authored unit.
2. CC-AUD-2 - Primary described entity and carried publication move are explicit enough to identify the governing pattern. The case keeps visible which primary described entity the unit is about and which carried publication move it performs over that described entity right now.
3. CC-AUD-3 — Outside-work boundary is explicit. The case states what downstream U.Work, U.WorkPlanning, decision, gate, or reliance claim still remains outside the governed unit, including neighboring pattern move, downstream claim/effect, or ongoing engineering-process continuation when that distinction matters.
4. CC-AUD-4 — The active problem-pressure family is named honestly. The case makes explicit whether the live problem pressure is local lexical-head repair, whole-unit primary-described-entity stabilization, bounded comparison, or another neighboring pattern rather than patching several problem pressures at once under one vague stability claim.
5. CC-AUD-5 - Problem-pressure and governing-pattern boundary choice is explicit. When the problem pressure belongs with Local Head Restoration, AuthoredUnit Primary Described-Entity Discipline, ComparativeReading, a neighboring explanation/faithfulness pattern, or a downstream decision, gate, work, or reliance publication, that governing pattern or authority-source exit is explicit rather than hidden inside broad-family wording.
6. CC-AUD-6 — Presentation-form labels do not launder governed-unit kind or downstream claim/effect. note, memo, sheet, table, screen, and similar labels remain presentation-form clues and do not silently change the governed unit or mint downstream claim/effect.
7. CC-AUD-7 - Load-bearing modeling basis is published or moved to a governing publication form. If the primary described entity or carried publication move depends on a modeling basis, that basis is published briefly enough for review or the case is moved to a heavier publication form or neighboring pattern that can carry it honestly.
8. CC-AUD-8 — Clearer prose does not silently strengthen downstream claim/effect. Readability, formatting, and wider circulation may improve the unit, but they do not by themselves turn the unit into approval, policy, assignment, gate, work, or reliance text.

#Relations

• Builds on: A.7, E.10, F.18, E.14, E.19
• Coordinates with: Local Head Restoration, AuthoredUnit Primary Described-Entity Discipline, ComparativeReading, neighboring explanation/faithfulness discipline, and downstream decision, gate, work, or reliance 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 decision/gate/work/reliance assignment to the governing pattern or authority source when the authored unit can no longer stay honest inside this problem-pressure classification pattern

#E.17.AUD:End

---

Last Updated: 2026-05-10 — this section last modified in upstream FPF commit 136be3bb (github.com/ailev/FPF)