#AuthoredUnitDiscipline / Local Head Restoration — repair the pressured local head before the authored unit inherits it

E.17.AUD.LHR · 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. Narrow local lexical-head repair pattern inside the broader AuthoredUnitDiscipline problem-pressure classification discipline.

Builds on. A.6.P, A.7, E.10, F.18, E.14.

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

Plain-name. Repair the pressured local lexical head before the authored unit inherits it.

One-line summary. Local Head Restoration is a narrow local lexical-head repair pattern for cases where one locally familiar word such as text, document, surface, review, or interpretation is being asked to carry more meaning than the sentence has honestly restored.

Governed object in plain terms. The governed object here is one local lexical head inside one authored unit: the load-bearing word or phrase whose kind is no longer recoverable from the sentence. The governed move is to restore the lexical-head kind, active lane, governed object when one is active, carried move or live question, and nearest outside-work boundary before the rest of the authored unit inherits ambiguity.

Use this when. Use this section when one note, memo, review unit, table, or semio-heavy paragraph starts leaning on one broad familiar word and you can no longer tell what kind of thing that word names here. Use it when the local lexical head has become the pressure point, but the authored unit has not yet proved that it needs full described-entity stabilization.

First-minute working moment. A draft says this review, this text, this document, this publication, or this interpretation, and everyone in the room keeps reading a different thing into the same local lexical head. You do not yet need a whole new authored-unit rule check. You need the local lexical-head repaired before the rest of the unit can be trusted.

What goes wrong if you miss this. One vague local lexical head quietly governs the next three sentences. Review then turns into an argument about taste while the real defect is simple: the unit never said whether it was naming a description, a carrier, an authored unit, a carried move, a governing pattern, or wider work.

What this buys you in practice. It lets a team stabilize the smallest honest unit first. You repair the pressured local lexical head, keep local lane and live question visible, and avoid escalating into authored-unit review too early.

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

• the same authored unit still has unstable described-entity or carried-move reading after local repair and now needs one stable answer to what it is about, what move it carries, and what remains outside;
• the live question is already one bounded comparative review move over an otherwise stable source episteme/publication;
• the main issue is view, face, carrier, publication architecture, or downstream authority work rather than a pressured local lexical head;
• the text is already honest locally, and the unresolved problem is wider strategy, rollout sequencing, or architecture framing.

Primary working reader. The first working reader is an author, reviewer, architect, or manager who needs one quick way to repair a pressured local lexical head before the whole text overclaims.

Problem-owning practice reading. In ordinary practice, this pattern helps teams editing review notes, status notes, decision memos, architecture notes, and semio-heavy paragraphs where one familiar local lexical head has become the pressure point. The job is not to redesign the whole text. It is to make one local sentence honest enough that reviewers stop arguing past each other about what the local lexical head names here.

Quick recovery entry. If the recognition surface fits, recover the local repair through the five-row ordinary card in E.17.AUD.LHR:3.2 and the nearest worked slices in E.17.AUD.LHR:5.1 through E.17.AUD.LHR:5.6. Use the quick worked-slice starter only while one pressured local lexical head still stays primary; if that recovery already lands in bounded comparison or authored-unit stabilization, name the governing pattern or authority-source exit before you open the heavier extension.

Quick first check. Do not open the whole local repair pattern yet. Ask these five questions first:

1. Which exact word is under pressure?
2. What lexical-head kind is that word honestly naming here?
3. Which lane is actually primary here?
4. What governed object, carried move or live question, and outside work are actually in play here?
5. After one honest repair, does the unit stabilize locally, or does its reading still shift into a neighboring lane?

Local-repair threshold. One honest local repair should restore the pressured local lexical head, its lexical-head kind, the active lane, the governed object when one is active, and the carried move or live question the sentence is actually carrying. If the next sentence still borrows a different kind, a different lane, or a different outside-work boundary from the same local lexical head, local repair is no longer the only primary question.

Neighboring-lane boundary check. If one honest local repair stabilizes the unit and the remaining question is one bounded comparative review move over already pinned source epistemes/publications, return the case to E.17.ID.CR (ComparativeReading) rather than thickening this local lexical-head repair pattern. If the same authored unit still cannot keep one stable primary described entity, one carried move, and one outside-work boundary visible after local repair, move to E.17.AUD.OOTD (AuthoredUnit Primary Described-Entity Discipline) instead of stacking more qualifiers onto the pressured local lexical head.

Quick kind stack. AuthoredUnitDiscipline names the wider authored-unit problem-pressure classification discipline. Local Head Restoration names the local lexical-head repair pattern used when one pressured local lexical head inside one authored unit still needs its lexical-head kind, active lane, governed object, carried move or live question, and any family/governing-pattern stack restored before the rest of the unit inherits ambiguity. When that broader stack is doing real work, write one explicit output line: repair family = ... | governing pattern = ... | governed object = ... | move = ... | outside work = .... This local repair works over the inherited frame; it does not redefine the moving lineage, carrier, face, or publication architecture that sits outside the current authored-unit repair. Authored-unit stability stays outside unless local repair still fails, in which case the case should move to E.17.AUD.OOTD. The canonical authored-unit rule/check locus remains E.17.AUD.OOTD; this section governs only the narrower local lexical-head repair pattern.

If those five questions are the right questions, start here.

Anti-workflow note. The quick checks, ordinary card, worked slices, and governing-pattern/source boundary rules in this section are local aids for one authored unit under review. They are not a canonical transduction workflow, not a mandatory lifecycle, and not a promise that admissible cases move through one fixed sequence. One case may stabilize after one lexical-head repair, another may reopen when outside observation changes the honest question, and another may move to E.17.AUD.OOTD when the authored unit still has unstable described-entity or carried-move reading.

#Keywords

• pressured local lexical head
• lexical-head kind
• active lane
• local repair
• governed object
• outside-work boundary
• local wording repair.

#Relations

#Content

#Problem frame

Anti-workflow note. The quick checks, ordinary card, worked slices, and governing-pattern/source boundary rules in this section are local aids for one authored unit under review. They are not a canonical transduction workflow, not a mandatory lifecycle, and not a promise that admissible cases move through one fixed sequence. One case may stabilize after one lexical-head repair, another may reopen when outside observation changes the honest question, and another may move to E.17.AUD.OOTD when the authored unit still has unstable described-entity or carried-move reading.

The recurring defect is small but expensive:

• one broad familiar word enters early;
• the word is never restored to one kind or lane;
• later sentences inherit its ambiguity as if nothing happened.

Typical high-pressure heads include:

• document
• text
• artifact
• note
• sheet
• publication
• surface
• face
• view
• review
• interpretation
• reading

These words are not uniformly wrong. They become risky when one of them starts carrying governed-object load, lane load, move load, or governing-boundary load without being restored first.

#Problem

Without a named local restoration move:

1. teams keep asking qualifiers to rescue an unstable local lexical head;
2. one sentence names a thing while the next sentence names the move over it;
3. readers over-infer authored-unit meaning from one under-restored broad-family word;
4. later authored-unit discipline is opened too early for a problem that was still local;
5. or the opposite happens: an authored-unit reading-stability defect is hidden because nobody repaired the local lexical-head pressure first.

#Solution

Local Head Restoration repairs the pressured local lexical head before the rest of the authored unit is allowed to inherit it.

It restores lexical-head kind, active lane, carried move or live question, and any family/governing-pattern/governed-object stack that the sentence is quietly relying on.

#Pairwise plain glosses

• Pressured local lexical head = the word doing more work than the sentence has honestly restored.
• Lexical-head kind = what kind of thing that word names here: for example description, carrier, authored unit, governed object, face, or view.
• Active lane = where the local work is happening here: for example review, publication, comparison, process, or authority.
• Governed object = what the local sentence or authored unit is actually about here.
• Move/live question = what the sentence is doing with that governed object, if anything.
• Family/governing-pattern/governed-object stack = when a broader family or governing pattern is active, name the family, governing pattern, governed object, move, and outside work separately rather than letting one familiar local lexical head carry them by implication.

Local reading lens. Treat the pressured local lexical head as one typed anchor inside one authored unit. This local lens restores one pressured local lexical head; it does not settle authored-unit modeling-lens policy, redefine the inherited moving lineage or its publication-form and face/carrier lanes, or replace neighboring semioarchitecture characteristics. The smallest honest local lens asks five things: what lexical-head kind is named here, which lane is primary, what governed object is in play, what carried move or live question is carried, and what still remains outside. If that local lens no longer stabilizes the same unit, local repair has already reached its limit and the case should move to its governing pattern or authority-source exit.

#Ordinary working card

Use this five-row card for ordinary cases:

Treat that card as the recognition surface. It is a local repair aid, not a universal lifecycle rail. Use it while one pressured local lexical head remains the main defect.

When family or governing-pattern language is load-bearing, add one explicit conditional output line next to the card: repair family = ... | governing pattern = ... | governed object = ... | move = ... | outside work = ....

Read the card as a three-way recovery aid:

• if rows 1-5 stabilize around one repaired local lexical head, one restored lane, one governed object, and one honest local question, stay here;
• if rows 1-5 stabilize locally and the remaining question is one bounded comparative review move over already pinned source epistemes/publications, return the case to E.17.ID.CR rather than thickening this local lexical-head repair pattern;
• if rows 2-5 still cannot stay stable because the same authored unit keeps borrowing a different object, move, or outside-work boundary from the same local lexical head, move to E.17.AUD.OOTD instead of pretending one more qualifier will rescue the same unit.

The nearest worked slices for those three landings are:

• ordinary stay-local: E.17.AUD.LHR:5.2;
• admissible return to bounded comparison: E.17.AUD.LHR:5.4;
• admissible authored-unit move to governing pattern: E.17.AUD.LHR:5.5.

#Load-bearing extension

If the local case is close to a seam and the ordinary card already stabilizes the unit, add these checks:

• pressured local lexical head;
• restored lexical-head kind;
• restored active lane;
• restored governed object;
• restored carried move or live question;
• restored outside-work boundary;
• any family / governing pattern / governed object distinction now made explicit;
• governing-pattern/source decision.

Use that extension as the assurance surface only when ordinary repair is already holding and the remaining risk is misuse at a neighboring seam. It is for the stay-local landing, not for re-deciding whether the case really belongs in E.17.ID.CR or E.17.AUD.OOTD. If the ordinary card now shows one stable local repair plus one bounded comparative review question, return the case to E.17.ID.CR before opening the extension. If the ordinary card still shows authored-unit reading instability after local repair, move to E.17.AUD.OOTD before adding declaration weight here. Do not use it to rescue a unit whose authored-unit reading still shifts, and do not turn it into a second rule sheet.

#Ordinary repair order

Use this order when one local lexical head is carrying too much:

1. name the pressured word;
2. restore the lexical-head kind;
3. restore the active lane;
4. restore the governed object when one is active;
5. restore the carried move or live question, if any;
6. restore any family / governing pattern / governed object distinction and nearest outside-work boundary the sentence is relying on;
7. decide which of three landings is honest: stay with local repair, return the case to bounded comparison, or move to authored-unit discipline.

A narrowing qualifier alone does not count as restoration. Treat this order as one local repair aid, not as a canonical flow. Steps 1-6 restore the pressured local lexical head; step 7 classifies what the repaired unit can honestly do next. If step 6 keeps reopening because the same unit still cannot hold one stable primary described entity, one carried move, and one outside-work boundary, stop local repair and move to E.17.AUD.OOTD. If the local lexical head is now honest and the only remaining question is one bounded contrast over already available source epistemes/publications, return the case to E.17.ID.CR instead of escalating the local card into a heavier record by habit. If the local lexical head is honest and no neighboring lane has become primary, stop here rather than manufacturing extra extension weight.

#Quick worked-slice starter

If you need one ordinary entry sentence fast, start from one of these:

Use these starters only as local examples. If outside observations or downstream constraints change what the sentence can honestly carry, reopen or move to the governing pattern or authority-source exit instead of treating the starter as step one of a fixed flow.

#Worked slices

Worked-slice status. Read the release-boundary, publication-face, semio-heavy, bounded-comparison, authored-unit stabilization move, and outside-observation cases as a heterogeneous example bank, not as one recommended repair sequence. They show different admissible landings for this local lexical-head repair pattern: some cases stabilize after one honest lexical-head repair and stop here, some return the case to E.17.ID.CR, some move to E.17.AUD.OOTD, and some stop and reopen when outside observation changes what the same local sentence can honestly carry. For quickest recovery of the three main landings, read E.17.AUD.LHR:5.2 as ordinary stay-local repair, E.17.AUD.LHR:5.4 as admissible return to E.17.ID.CR, and E.17.AUD.LHR:5.5 as admissible authored-unit move to E.17.AUD.OOTD. Then read E.17.AUD.LHR:5.6 as the separate stop-and-reopen or neighboring governing-pattern move case after outside observation changes what the same local unit can honestly carry.

Worked-slice mini-schema. When a case turns semio-heavy or seam-heavy, recover the same compact output in this order: pressured local lexical head | lexical-head kind | active lane | governed object | carried move or live question | outside work | landing.

#review is really carrying two jobs

A note says: This review establishes the release boundary for the service.

Two sentences later it says: The review should therefore assign rollout responsibility to platform.

Local repair first:

• pressured local lexical head = review;
• restored lexical-head kind = authored review unit;
• active lane = boundary review, not responsibility assignment;
• governed object = the release boundary as made visible in this review unit;
• carried move = make one boundary visible;
• outside work = responsibility assignment.

The repaired unit can now either stay with the boundary review or explicitly move to the responsibility-assignment lane. Without that repair, the note quietly overclaims.

#text quietly shifts into carrier or document status

A paragraph says: This text is the policy.

But what it really means is one authored publication form that describes the policy rather than being the policy object itself.

Local repair:

• pressured local lexical head = text;
• restored lexical-head kind = authored publication form;
• active lane = authored unit, not governed policy object;
• governed object = the policy description visible in this unit;
• carried move = describe the policy rather than claim authority for it;
• outside work = downstream authority status.

This is the ordinary stay-local case. One repaired local lexical head keeps later sentences from borrowing authority from the wrong lane without forcing authored-unit stabilization.

Recovery reading. Stay in E.17.AUD.LHR: the local lexical head is now honest, the same local unit no longer shifts, and no neighboring lane has become primary.

#Semio-heavy family name does too much work

A semio note says: This interpretation clarifies the package.

But the same paragraph is really about one bounded comparative-reading move over one review unit, not about InterpretationDiscipline as a whole and not about the whole package.

Local repair:

• pressured local lexical head = interpretation;
• restored lexical-head kind = comparative review unit anchor inside one semio-heavy paragraph;
• active lane = bounded comparative reading, not wider-family package explanation;
• governed object = comparative review unit;
• stack restored = family InterpretationDiscipline, governing pattern ComparativeReading;
• move = bounded comparative reading;
• outside work = wider architecture strategy.

Now the local paragraph stops pulling package-level load it never declared.

#Local repair lands back in bounded comparison

A comparison note says: This review shows option A is safer than option B.

But the unit is really one comparative review note over already pinned source epistemes/publications, not an authored-unit reading-instability case and not yet a problem-pressure classification case.

Local repair:

• pressured local lexical head = review;
• restored lexical-head kind = comparative review unit;
• active lane = bounded comparative-reading unit, not whole release workflow;
• governed object = the already pinned option contrast;
• carried move = make one bounded contrast visible over already available source epistemes/publications;
• outside work = rollout choice or approval.

Once that local lexical head is repaired, do not keep thickening this pattern by habit. The admissible next move is to return the now-stable unit to E.17.ID.CR, because the remaining question is one bounded contrast rather than authored-unit described-entity instability.

Recovery reading. This is the honest return-to-bounded-comparison case: finish the local repair here, then let E.17.ID.CR carry the remaining bounded contrast over the now-stable unit.

#Local repair exposes authored-unit reading instability and must move to whole-unit discipline

A release note says: This document records the release decision for the candidate.

After one sentence, the same unit starts talking as if it were:

• the authored review unit that compares evidence;
• the decision object itself;
• and the rollout work that follows if approval lands.

Local repair can still restore the pressured local lexical head:

• pressured local lexical head = document;
• restored lexical-head kind = authored review unit;
• active lane = authored unit, not decision object or rollout work;
• carried move = record the current release reasoning visible in this unit;
• outside work = actual approval, rollout execution, and downstream authority question.

But the repaired local lexical head does not keep the same authored unit stable. The next sentences still slide between the object being decided, the move of comparing evidence, and the wider work that happens after the decision. That means local lexical-head repair has done its job and shown the remaining defect honestly: the authored unit still cannot keep one stable object, one move, and one outside-work boundary visible.

Recovery reading. This is the admissible authored-unit stabilization move case: stop thickening the local repair, keep the restored local lexical head as the last honest local result, and move to E.17.AUD.OOTD because the same unit still has unstable reading after one honest repair.

#Outside observation changes what the same head can honestly carry

A status note says: This note captures the current rollback posture for the candidate.

Mid-review, a new vendor bulletin changes the live failure boundary and pushes the surrounding conversation toward approval pressure.

Local repair can still make the current sentence honest:

• pressured local lexical head = note;
• restored lexical-head kind = authored review unit;
• active lane = current review unit, not downstream approval source;
• carried move = capture the rollback posture visible on the current evidence slice;
• outside work = any new approval, adjudication, or widened authority step.

But this is the stop-and-reopen case. Once outside observation changes what the same local unit can honestly stay about, do not keep appending new pressure as if the same local repair simply continued. Stop, reopen with a newly declared question, or move if downstream authority or authored-unit stabilization has become primary.

Recovery reading. Do not keep thickening the local card here: outside observation has changed what the same local unit can honestly carry, so the admissible landing is stop-and-reopen or neighboring move to governing pattern, not one more local qualifier.

#Branch exits

Assurance-recovery note. Read these governing-pattern exits as a heavier audit record over the same ordinary five-row card and the same three honest landings. They are not a second compact rule list. If a governing-pattern exit bullet starts carrying the case by itself, recover the local-repair threshold, E.17.AUD.LHR:3.2 Row 5, and the nearest worked slice first.

Move away from this pattern when:

• the repaired local lexical head is no longer the real problem and the authored unit still has unstable described-entity or carried-move reading;
• the same unit is already stable enough and the remaining question is one bounded comparative review move over already pinned source epistemes/publications;
• the problem is really view/face/carrier architecture;
• the unit has already become downstream approval, gate, adjudication, or execution work;
• outside observation or environmental change has changed what the same local unit can honestly carry, so the case now needs stop-and-reopen or a neighboring move to governing pattern rather than one more local qualifier.

Governing-pattern exit recovery map.

The comparison-side neighbor is E.17.ID.CR ComparativeReading: use that governing pattern when the local lexical head is now honest, the unit already stays about the same described entity, and the remaining question is one bounded comparative reading over already available source epistemes/publications.

The main authored-unit neighbor is E.17.AUD.OOTD AuthoredUnit Primary Described-Entity Discipline: use that governing pattern when local lexical-head repair is no longer enough and the whole authored unit still cannot keep one stable primary described entity, one carried move, and one outside-work boundary visible.

Treat those as neighboring recoveries, not as a required sequence. Some cases will stop after one local repair, some will return the case to bounded comparison under E.17.ID.CR, and some will move to authored-unit stabilization under E.17.AUD.OOTD once the honest question changes.

#Consequences

Used well, this pattern:

• prevents one vague local lexical head from governing a whole section by accident;
• keeps local repair cheap instead of escalating too early;
• makes later authored-unit review cleaner because the local lexical head question has already been restored;
• gives authors and reviewers one common language for saying the problem is still local.

Used badly, it can become one more vocabulary exercise. If the authored unit still has unstable described-entity or carried-move reading after local repair, do not keep polishing the pressured local lexical head forever. Move the case to the governing pattern.

#SoTA-Echoing

Assurance-recovery note. Use these rows only after the ordinary five-row card, the local-repair threshold, and the nearest worked slices already tell you which landing is primary. Each row should recover back into the same local question, landing, or safeguard; if a citation starts carrying the case by itself, recover the ordinary card first.

Read E.17.AUD.LHR:6 - Branch exits through this table only after the landing is already visible by value. The citations do not choose the landing for you; they discipline why the already-recovered landing is reviewable and teachable.

#Relations

Builds on

• A.6.P Relational Precision Restoration Suite
• E.10 Unified Lexical Rules for FPF
• F.18 Local-First Unification Naming Protocol
• A.7 Strict Distinction

Nearest neighbors

• E.17.AUD.OOTD AuthoredUnit Primary Described-Entity Discipline
• E.17.ID.CR ComparativeReading

Authority note. This monolith section is the canonical governing-pattern boundary locus for Local Head Restoration inside the Core. Companion notes may summarize, harden, or stage adjacent recovery support, but they may not override this section.

#E.17.AUD.LHR:End

---

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