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

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

Placement. Narrow local-repair branch inside the broader AuthoredUnitDiscipline umbrella.

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 head before the authored unit inherits it.

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

Governed object in plain terms. The governed object here is one pressured head inside one authored unit. The governed move is to restore the head kind, active lane, governed object when one is active, move or burden, 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 head has become the pressure point, but the authored unit has not yet proved that it needs full object-of-talk 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 head. You do not yet need a whole new surface-level law check. You need the local head repaired before the rest of the unit can be trusted.

What goes wrong if you miss this. One vague 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 move, a branch, or wider work.

What this buys you in practice. It lets a team stabilize the smallest honest unit first. You repair the pressured head, keep local lane and burden 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 drifts after local repair and now needs one stable answer to what it is about, what move it carries, and what remains outside;
• the real burden is already one bounded comparative review move over an otherwise stable surface;
• the main issue is view, face, carrier, publication architecture, or downstream authority work rather than a pressured local 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 head before the whole text overclaims.

Problem-owning practice reading. In ordinary practice, this branch helps teams editing review notes, status notes, decision memos, architecture notes, and semio-heavy paragraphs where one familiar 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 head names here.

Quick recovery route. 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 head still stays primary; if that recovery already lands in bounded comparison or authored-unit stabilization, hand back or reroute before you open the heavier extension.

Quick first check. Do not open the whole branch yet. Ask these five questions first:

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

Local-repair threshold. One honest local repair should restore the pressured head, its head kind, the active lane, the governed object when one is active, and the move or burden 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 head, local repair is no longer the only primary burden.

Neighboring-lane boundary check. If one honest local repair stabilizes the unit and the remaining burden is one bounded comparative review move over already pinned material, hand back to E.17.ID.CR (ComparativeReading) rather than thickening this local-repair branch. If the same authored unit still cannot keep one stable object, one move, and one outside-work boundary visible after local repair, reroute to E.17.AUD.OOTD (AuthoredUnit Object-of-Talk Discipline) instead of stacking more qualifiers onto the pressured head.

Quick kind stack. AuthoredUnitDiscipline names the wider umbrella. Local Head Restoration names the local-repair branch used when one pressured head inside one authored unit still needs its head kind, active lane, governed object, move or burden, and any umbrella or branch stack restored before the rest of the unit inherits ambiguity. When that broader stack is doing real work, write one explicit output line: umbrella = ... | branch = ... | 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 reroute to E.17.AUD.OOTD. The canonical authored-unit law/check surface remains E.17.AUD.OOTD; this section governs only the narrower local-repair branch.

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

Anti-workflow note. The quick checks, ordinary card, worked slices, and reroute 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 lawful cases move through one fixed sequence. One case may stabilize after one head repair, another may reopen when outside observation changes the honest burden, and another may reroute to E.17.AUD.OOTD when the authored unit still drifts.

#Keywords

• pressured head
• 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 reroute 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 lawful cases move through one fixed sequence. One case may stabilize after one head repair, another may reopen when outside observation changes the honest burden, and another may reroute to E.17.AUD.OOTD when the authored unit still drifts.

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 owner-boundary load without being restored first.

#Problem

Without a named local restoration move:

1. teams keep asking qualifiers to rescue an unstable 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 umbrella;
4. later authored-unit discipline is opened too early for a problem that was still local;
5. or the opposite happens: a authored-unit drift defect is hidden because nobody repaired the local pressure first.

#Solution

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

It restores head kind, active lane, move or burden, and any umbrella/branch/object stack that the sentence is quietly relying on.

#Pairwise plain glosses

• Pressured head = the word doing more work than the sentence has honestly restored.
• 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/burden = what the sentence is doing with that governed object, if anything.
• Umbrella/branch/object stack = when a broader umbrella or narrower branch is active, name the umbrella, branch, governed object, move, and outside work separately rather than letting one familiar head carry them by implication.

Local reading lens. Treat the pressured head as one typed surface anchor inside one authored unit. This local lens restores one pressured 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 axes. The smallest honest local lens asks five things: what head kind is named here, which lane is primary, what governed object is in play, what move or burden 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 reroute.

#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 head remains the main defect.

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

Read the card as a three-way recovery surface:

• if rows 1-5 stabilize around one repaired local head, one restored lane, one governed object, and one honest local burden, stay here;
• if rows 1-5 stabilize locally and the remaining burden is one bounded comparative review move over already pinned material, hand back to E.17.ID.CR rather than thickening this local-repair branch;
• 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 head, reroute 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;
• lawful hand-back to bounded comparison: E.17.AUD.LHR:5.4;
• lawful authored-unit reroute: 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 head;
• restored head kind;
• restored active lane;
• restored governed object;
• restored move or burden;
• restored outside-work boundary;
• any umbrella/branch/object distinction now made explicit;
• reroute 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 burden, hand back to E.17.ID.CR before opening the extension. If the ordinary card still shows authored-unit drift after local repair, reroute to E.17.AUD.OOTD before adding declaration weight here. Do not use it to rescue a unit that still drifts at authored-unit level, and do not turn it into a second law sheet.

#Ordinary repair order

Use this order when one head is carrying too much:

1. name the pressured word;
2. restore the head kind;
3. restore the active lane;
4. restore the governed object when one is active;
5. restore the move or burden, if any;
6. restore any umbrella/branch/object distinction and nearest outside-work boundary the sentence is relying on;
7. decide which of three landings is honest: stay with local repair, hand back to bounded comparison, or reroute 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 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 object, one move, and one outside-work boundary, stop local repair and reroute to E.17.AUD.OOTD. If the local head is now honest and the only remaining burden is one bounded contrast over already available material, hand back to E.17.ID.CR instead of escalating the local card into a heavier surface by habit. If the local 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 reroute instead of treating the starter as step one of a fixed flow.

#Worked slices

Worked-slice status. Read the release-boundary, publication-surface, semio-heavy, bounded-comparison, authored-unit-reroute, and outside-observation cases as a heterogeneous example bank, not as one recommended repair ladder. They show different lawful landings for this local-repair branch: some cases stabilize after one honest head repair and stop here, some hand back to E.17.ID.CR, some reroute 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 lawful hand-back to E.17.ID.CR, and E.17.AUD.LHR:5.5 as lawful authored-unit reroute to E.17.AUD.OOTD. Then read E.17.AUD.LHR:5.6 as the separate stop-and-reopen or neighboring handoff 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 head | head kind | active lane | governed object | move or burden | 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 ownership to platform.

Local repair first:

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

The repaired unit can now either stay with the boundary review or explicitly hand off to the ownership lane. Without that repair, the note quietly overclaims.

#text quietly drifts into carrier or document status

A paragraph says: This text is the policy.

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

Local repair:

• pressured head = text;
• restored head kind = authored publication surface;
• 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 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 head is now honest, the same local unit no longer drifts, and no neighboring lane has become primary.

#Semio-heavy umbrella 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 head = interpretation;
• restored head kind = comparative review unit anchor inside one semio-heavy paragraph;
• active lane = bounded comparative reading, not umbrella-level package explanation;
• governed object = comparative review unit;
• stack restored = umbrella InterpretationDiscipline, branch 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 material, not a authored-unit drift case and not yet a route choice.

Local repair:

• pressured head = review;
• restored 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 material;
• outside work = route choice or approval.

Once that local head is repaired, do not keep thickening this branch by habit. The lawful next move is to hand the now-stable unit back to E.17.ID.CR, because the remaining burden is one bounded contrast rather than authored-unit object-of-talk drift.

Recovery reading. This is the honest hand-back branch: 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 drift and must reroute

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 head:

• pressured head = document;
• restored 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 burden.

But the repaired 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 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 lawful authored-unit-reroute branch: stop thickening the local repair, keep the restored head as the last honest local result, and move to E.17.AUD.OOTD because the same unit still drifts 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 burden.

Local repair can still make the current sentence honest:

• pressured head = note;
• restored head kind = authored review unit;
• active lane = current review unit, not downstream approval surface;
• 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 stronger burden as if the same local repair simply continued. Stop, reopen with a newly declared burden, or hand off 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 lawful landing is stop-and-reopen or neighboring handoff, not one more local qualifier.

#Reroutes

Assurance-recovery note. Read these reroutes as a heavier audit surface over the same ordinary five-row card and the same three honest landings. They are not a second compact law list. If a reroute 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.

Reroute away from this branch when:

• the repaired local head is no longer the real problem and the authored unit still drifts;
• the same unit is already stable enough and the remaining burden is one bounded comparative review move over already pinned material;
• the problem is really view/face/carrier architecture;
• the unit has already become downstream approval, gate, adjudication, or execution work;
• outside observation or environmental drift has changed what the same local unit can honestly carry, so the case now needs stop-and-reopen or a neighboring handoff rather than one more local qualifier.

Reroute recovery map.

The comparison-side neighbor is E.17.ID.CR ComparativeReading: use that branch when the local head is now honest, the unit already stays about the same object of talk, and the remaining burden is one bounded comparative reading over already available material.

The main authored-unit neighbor is E.17.AUD.OOTD AuthoredUnit Object-of-Talk Discipline: use that branch when local head repair is no longer enough and the whole authored unit still cannot keep one stable object, one 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 hand back to bounded comparison under E.17.ID.CR, and some will reroute to authored-unit stabilization under E.17.AUD.OOTD once the honest burden changes.

#Consequences

Used well, this branch:

• prevents one vague 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 head burden 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 drifts after local repair, do not keep polishing the pressured head forever. Hand off.

#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 burden, landing, or safeguard; if a citation starts carrying the case by itself, recover the ordinary surface first.

Read E.17.AUD.LHR:6 - Reroutes 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 Object-of-Talk Discipline
• E.17.ID.CR ComparativeReading

Authority note. This monolith section is the canonical branch-law 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