Situational Writing Timing and Recovery | Allocate Time, Protect the Final Third, Recover from Stalls and Finish the Task

51. The second checkpoint asks whether the middle is still ordinary

Midway through drafting, the writer should still be using the same operating rules as at the start. If every sentence now feels urgent, if clock checking has increased, or if source rereading becomes broader, execution has changed state. The checkpoint asks whether ordinary work is still ordinary before visible collapse begins.

52. Midpoint checks should compare work state, not emotion

Feeling nervous does not prove the task is behind. Feeling comfortable does not prove it is on time. Compare completed paragraph jobs, remaining required content and current reserve. Operational evidence is more reliable than subjective pace.

53. A healthy midpoint has a visible remaining route

The student should know what remains: perhaps one development paragraph, one practical paragraph and a closing. If the remaining route cannot be stated, architecture or fulfilment has become unstable. Timing recovery begins by restoring the route before increasing speed.

54. A bad midpoint is not always a time problem

The writer may be on schedule but working from a faulty interpretation, or behind because one language stall consumed time. Diagnose the mechanism. Pacing interventions cannot solve a content misunderstanding, and grammar interventions cannot solve an oversized plan.

55. Time debt has sources

Common sources include over-reading, over-planning, opening perfectionism, source-search loops, vocabulary stalls, sentence rewrites, unnecessary format decisions, overdevelopment and repeated checking. The repair should target the debt source rather than merely tell the student to “write faster”.

56. Over-reading debt requires a stopping rule

If the student repeatedly rereads the whole stimulus, define what must be known before drafting: role, audience, purpose, requirements, core source meaning and material constraints. Once those states are stable, further rereading should be local to named uncertainties.

57. Over-planning debt requires plan compression

If planning contains complete sentences, transition wording and multiple backup ideas, reduce it to jobs and evidence anchors. Planning should preserve decisions, not pre-write the response. Training can gradually compress a full plan into a low-load execution map.

58. Opening perfectionism requires an opening ceiling

The opening should establish context and purpose sufficiently. If the writer has rewritten it twice while later requirements remain untouched, an opening ceiling has been crossed. Move forward. A functional opening can be refined only after the full task exists.

59. Source-search loops require evidence corridors

If the writer keeps returning to the stimulus for the same paragraph, mark which source detail supports that job before drafting. One evidence corridor is cheaper than repeated source-wide searches. SW-100 uses the source system built earlier; it does not reteach source interpretation.

60. Vocabulary debt requires lexical fallback

Students should have a trained fallback behaviour: if the exact word is unavailable, paraphrase accurately and continue. A simple known word can be revisited during checking if needed. Waiting for the “best” word is rarely a good use of scarce exam time.

61. Rewrite debt requires edit thresholds

If the sentence is understandable and semantically correct, defer stylistic rewriting. If it changes meaning, breaks grammar severely or makes the next sentence impossible to write, repair it now. This threshold keeps local editing from turning into recursive drafting.

62. Overdevelopment debt requires one-more-job testing

Before adding another sentence, ask what new reader job it performs. If the answer is none, stop. A sentence that repeats significance is costing time without increasing task value.

63. Reassurance checking is not the same as verification

Students sometimes reread because they feel uncertain, not because they know what they are checking. Verification has a target: source ownership, deadline, condition, quantifier or sentence boundary. Reassurance rereading often consumes time without changing any state.

64. Time recovery begins by stopping the leak

If time debt comes from sentence rewrites, writing faster does not solve the leak; stopping unnecessary rewrites does. If debt comes from broad source search, narrow search. Recovery should remove the current cost driver before adding speed pressure.

65. Then reduce optional work

After the leak is stopped, remove low-value work: secondary examples, stylistic transitions, elaborate sentence variation, extra concessions and non-essential detail. Preserve required jobs and decisive evidence.

66. Then simplify future syntax

When serious debt remains, use structures the writer can execute reliably. One clean reason sentence and one clean action sentence are better than a compressed complex sentence that creates a run-on or drops a condition.

67. Then protect closure

Do not spend recovered minutes making the middle richer if the required action and closing remain unwritten. Recovery should point the response toward first completion.

68. Clock panic often creates global speeding

A student notices they are behind and starts writing every sentence faster. This can increase grammar errors, source distortion and missing conditions. Global speeding is blunt. Better recovery compresses optional work while preserving accuracy on high-risk content.

69. Clock panic can also create global slowing

Some students respond to pressure by checking more, hesitating longer and rewriting more often. Their subjective urgency increases while output slows. Training should identify this pattern explicitly because “hurry up” may intensify the very behaviour causing the delay.

70. A recovery mode should be predefined

Students should know what changes when serious time debt appears: simpler sentences, one decisive reason, local source checks, minimum viable paragraph jobs, shortened transitions and protected action. A predefined mode is faster than inventing a rescue strategy while already under pressure.

71. Recovery mode should not become normal mode too early

If the student switches into emergency compression after a minor delay, the response may become unnecessarily thin. Use checkpoint evidence to determine debt severity. Mild debt needs small adjustments; severe debt needs triage.

72. State preservation reduces return cost

Whenever the writer leaves an unresolved item, record enough state to resume immediately: missing evidence, exact word, deadline check, source owner, comparison criterion. Returning to an unlabelled concern requires re-diagnosis and wastes reserve.

73. Unresolved items should be ranked by value

A missing eligibility condition outranks an uncertain synonym. An incomplete request outranks an awkward transition. The return queue should be ordered by expected mark and communication value, not by the order in which problems were noticed.

74. The return queue should remain short

Too many flags indicate the writer is parking ordinary decisions rather than solving them. Most sentences should be completed sufficiently on the first pass. Skip-and-return is a recovery tool, not a default drafting style.

75. First completion converts uncertainty into bounded revision

Before first completion, unresolved uncertainty competes with unwritten content. After first completion, the task exists and revision becomes bounded. This is why completion is a major state transition rather than simply “finishing the last sentence”.

76. First completion should trigger a requirement scan

Confirm every required communication job exists. Check the explicit task requirements and any high-risk source conditions. This scan protects against the common failure of a polished script that quietly omits one required point.

77. Then scan mechanical certainty

Look for blanks, unfinished sentences, wrong dates, missing names, missing negation, broken labels and obviously incomplete punctuation. Certain loss should be recovered before interpretive polishing begins.

78. Then scan high-risk meaning

Check conditions, quantities, source ownership, modality and required action. These small language units can change who qualifies, what is required and how certain a claim is.

79. Then use personal error knowledge

One learner checks tense drift; another checks vague pronouns; another checks lost conditions. Personal error maps make final checking efficient because the search focuses on defects the learner actually produces.

80. Style refinement is the final layer

Only after required content and high-risk meaning are secure should the writer consider replacing awkward repetition, improving one transition or refining vocabulary. Style is valuable when there is genuine reserve.

81. A checking reserve has diminishing returns

The first minute of targeted checking can recover obvious loss. Later minutes may find smaller improvements. The student should stop once high-risk categories are checked and remaining changes are mainly preference.

82. The final third should have its own risk profile

Late-script errors often include rushed syntax, missing articles, vague pronouns, reduced development, forgotten conditions and abrupt closure. Training should measure the final third separately rather than average it into whole-script performance.

83. Final-third deterioration can be caused by early overcost

The writer may appear to lack stamina, yet the real problem is spending too much cognitive effort perfecting early prose. Reducing early cost can improve late performance without any separate endurance intervention.

84. Final-third deterioration can be genuine fatigue

If late accuracy still falls after pacing and early cost are controlled, stamina may be involved. SW-100 can detect the execution signature, while broader endurance training can be developed elsewhere if needed.

85. Final-third deterioration can be confidence shock

One difficult source or sentence can trigger panic and rushed writing afterward. Recovery should include a reset: identify the local block, contain it, restore the ordinary plan and avoid carrying urgency into unrelated paragraphs.

86. Final-third deterioration can be decision overload

If too many choices were deferred, the closing phase becomes crowded with unresolved decisions. Better planning and state preservation can reduce late cognitive load. The problem is not always physical tiredness.

87. Timed recovery should be practised deliberately

Do not wait for mistakes to occur accidentally. Create drills where a source condition is revealed late, a sentence stalls, a required point is discovered missing or a clock checkpoint shows debt. The student rehearses the recovery behaviour while the stakes are low.

88. Practice should vary the type of disruption

Vocabulary stalls, source ambiguity, late condition, wrong paragraph order, missing action, time debt and register drift require different responses. A student who practises only “write faster” has not trained recovery.

89. Practice should vary when the disruption occurs

An early misread offers more repair time than a late omission. A stall at minute five is different from one in the final two minutes. Recovery skill depends on horizon: how much time and unfinished work remain.

90. Practice should include clean runs

Students also need uninterrupted simulations where the normal system operates end to end. Too much disruption training can make them expect crisis. Recovery exists to restore ordinary execution, not replace it.

91. The goal of recovery is restoration, not heroics

A successful recovery is often small: simpler sentence, corrected condition, local source check, one skipped wording issue, return to the plan. The aim is to make the rest of the response ordinary again.

92. Timing plans should be tested on unfamiliar tasks

A budget that works only for rehearsed topics may be misleading. Use unfamiliar source packs and forms so the learner sees whether orientation, planning and drafting phases remain stable when interpretation cost rises.

93. Timing plans should survive different source densities

Dense sources increase selection cost; sparse sources can increase hesitation and invention risk. The same broad phase system should survive both, with local adjustments to reading and planning rather than a complete new strategy.

94. Timing plans should survive different forms

A report may need more visible structural planning; an email may move to drafting sooner. Format can shift the internal budget slightly, but the core sequence—decode, plan, draft, complete, verify—remains stable.

95. Timing plans should survive audience changes

A difficult audience relationship can increase wording hesitation. Register decisions should be settled during planning so the writer does not recalibrate politeness or authority in every sentence. Upstream clarity protects timing downstream.

96. Timing plans should survive mark-pressure psychology

Students may overinvest in the task they believe is worth more or in the paragraph they think sounds most impressive. The budget should follow actual assessment structure and task needs, not fear-driven importance estimates.

97. Readiness means the plan can bend without breaking

A rigid student can perform well only when every phase ends on schedule. A ready student can absorb a small delay, compress optional work, preserve mandatory jobs and still finish. Flexibility is part of timing competence.

98. Readiness means recovery does not spread

One difficult sentence remains one difficult sentence. One source correction remains one local repair. The student avoids turning a local defect into global rushing, global doubt or complete-plan abandonment.

99. Readiness means the final check is intentional

The student knows which high-risk categories to inspect, which flags to return to and what kinds of edits are too risky late. Final checking is a designed phase, not random rereading.

100. Mature timing is controlled state management

The student knows whether they are orienting, planning, drafting, recovering, completing or checking. They know what remains unfinished and what risk is active. Timing becomes the management of task state under a finite clock rather than a constant attempt to move faster.

101. Practice Lab: the ten-minute opening

Maren spends ten minutes perfecting the opening of a task whose total time is limited. The opening is polished, but two required communication jobs remain unwritten later. Diagnosis: opening overinvestment. Repair: set an opening ceiling, accept the first accurate functional version and preserve the final third.

102. Practice Lab: planning becomes prose

Iona writes complete sentences in the planning space, including alternative introductions and transitions. By the time drafting begins, the clock is already in debt. She compresses planning to paragraph jobs, evidence anchors and one action line. The plan becomes a navigation tool rather than a hidden first draft.

103. Practice Lab: repeated source rereading

Leonie rereads the entire source each time she begins a paragraph. Most of the information is already understood. The intervention is local search: mark which source detail belongs to which paragraph job before drafting, then return only to uncertain details.

104. Practice Lab: vocabulary freeze

Maren cannot recall a sophisticated word for “easy to reach” and stops for almost a minute. The safe fallback is “easy to reach” or “accessible”. A precise ordinary phrase preserves meaning and time. The vocabulary can be improved only if genuine reserve appears later.

105. Practice Lab: sentence rescue consumes the paragraph

Iona tries to repair one overloaded sentence repeatedly, crossing out and restarting. The paragraph job is still clear. Recovery: end the unstable sentence with the core proposition, start a new sentence for the remaining condition, and move on. Structural simplification restores forward motion.

106. Practice Lab: reassurance rereading

Leonie rereads the opening several times because she worries it sounds weak. She cannot name a defect. Her rule becomes: no reread without a target. If she cannot state what she is checking, she continues drafting.

107. Practice Lab: the clock check every minute

Maren monitors the clock constantly and becomes more anxious each time. The checks do not change strategy. She replaces them with phase checkpoints: after planning, around the midpoint, before the final third and at first completion. Clock use becomes decision-linked.

108. Practice Lab: mild debt triggers panic mode

Iona is two minutes behind her plan and immediately switches to bare, underdeveloped sentences. The debt is mild. Better response: stop stylistic polishing, keep one necessary development move per high-value point, and continue the normal structure.

109. Practice Lab: serious debt is ignored

Leonie reaches the midpoint with two major paragraphs still unwritten and continues writing at normal depth. She needs triage: one decisive reason per major job, simpler syntax, local source checks and immediate protection of the required closing action.

110. Practice Lab: being ahead causes expansion

Maren sees that she is ahead and adds a second example to the first body paragraph. Ten minutes later she is no longer ahead. The rule is to bank surplus until first completion. Extra time is reserve, not permission to enlarge the task.

111. Practice Lab: source ambiguity stalls the whole script

Iona is unsure whether one figure belongs to Group A or Group B. She starts doubting the entire plan. Recovery: mark the local attribution issue, continue with unaffected content, then verify that source before using the figure. One uncertainty stays local.

112. Practice Lab: unfamiliar form causes template search

Leonie sees “briefing note” and spends several minutes trying to remember a model. She instead returns to invariants: reader, purpose, required content and action. She borrows only the useful affordances—concise, scannable, decision-facing—and resumes.

113. Practice Lab: register doubt repeats every sentence

Maren knows the reader is a principal but recalibrates politeness repeatedly. She uses a three-word anchor: student → principal → recommend. That relationship remains constant, so local wording decisions become faster.

114. Practice Lab: too many flags

Iona marks six places to return to in one page. The queue is now a second task. She raises the threshold: only unresolved meaning, condition, source or action risks are flagged. Ordinary wording decisions are completed once and released.

115. Practice Lab: skipped recommendation

Leonie finds the recommendation difficult and decides to write the logistics first. Later, time runs out before the recommendation is fully stated. High-value paragraph jobs need a minimum viable version before they are skipped. She should write the core recommendation, then return for refinement if needed.

116. Practice Lab: skipped word, state preserved

Maren cannot recall a word and writes a simple substitute, mentally marking it for possible upgrade. Because the meaning is already complete, the return cost is low. This is healthy skip-and-return behaviour.

117. Practice Lab: missing requirement found late

Iona notices near the end that she has not addressed the registration deadline. She does not rewrite the earlier logistics paragraph. She inserts the deadline in the current action paragraph and checks whether the location remains logically acceptable. Recovery protects the requirement with minimal disruption.

118. Practice Lab: wrong audience discovered mid-draft

Leonie realises she has been writing as though the recipient were a peer rather than a committee. She identifies which sentences are actually affected, resets register from the next sentence and repairs only conspicuous earlier mismatches during final checking. Full restart would be too costly.

119. Practice Lab: wrong source group discovered mid-draft

Maren assigned a statistic to all students when it applies only to surveyed club members. She corrects the population and any dependent claim. The paragraph structure remains valid. Recovery follows the error’s downstream footprint instead of rewriting everything.

120. Practice Lab: late condition changes one sentence

Iona notices that free transport applies only before Friday. She does not rewrite the whole invitation. She restores the condition beside the transport claim and adjusts the action line. Local repair is sufficient.

121. Practice Lab: final-third syntax collapses

Leonie’s early prose is controlled, but the last paragraph becomes a long run-on. Her late-mode rule is to reduce complexity deliberately: shorter clauses, direct action verbs, one condition per sentence where necessary. Accuracy is protected before style.

122. Practice Lab: final-third development collapses

Maren gives rich early reasoning and a bare final recommendation. Her training budget now protects one evidence bridge for every major late decision. Early paragraphs are capped before optional fourth sentences appear.

123. Practice Lab: final-third source search expands

Iona cannot remember one date and rereads all sources. The reserve disappears. The repair is local verification: search only the relevant notice or note for the date, then return immediately to the script.

124. Practice Lab: confidence shock after one hard sentence

Leonie struggles with a comparison sentence and concludes the whole response is weak. She begins rushing. Her reset is explicit: identify sentence-level problem, simplify it, restate remaining paragraph jobs and resume ordinary pace.

125. Practice Lab: fatigue or early overcost?

Maren’s late language errors disappear when she stops rewriting early paragraphs. The issue was not endurance; it was cognitive overcost. Diagnosis prevents unnecessary stamina training.

126. Practice Lab: genuine fatigue remains

Iona’s late accuracy still falls after pacing and early cost are stabilised. Now the execution signature suggests endurance. SW-100 records when deterioration starts and what functions fail, creating a better target for later endurance work.

127. Practice Lab: first completion with no reserve

Leonie reaches the closing exactly as time expires. The response is complete but unverified. Training objective: move first completion slightly earlier by reducing avoidable early cost, not by removing required development.

128. Practice Lab: reserve protected too rigidly

Maren stops drafting when the planned checking window begins, leaving one requirement incomplete. The reserve should be partially converted into completion time. A shorter final check is better than a polished incomplete response.

129. Practice Lab: reserve spent on style

Iona reaches first completion with four minutes left and immediately upgrades vocabulary. She misses a wrong date. Her checking hierarchy changes: requirement scan, task-critical meaning, personal risks, then style only if time remains.

130. Practice Lab: reserve spent rereading from line one

Leonie performs a slow top-to-bottom reread and reaches only half the response before time. She replaces it with targeted passes: completion, dates/conditions, personal error hotspots and flagged items.

131. Practice Lab: one-minute check

With one minute left, Maren scans only high-risk tokens: dates, names, “not”, “all”, “must”, “will”, conditions, unresolved pronouns and the final requested action. She does not attempt stylistic improvement.

132. Practice Lab: three-minute check

Iona has three minutes. She checks requirements, conditions, quantities, source ownership and sentence boundaries, then returns to one flagged comparison. Vocabulary remains untouched unless clearly wrong.

133. Practice Lab: five-minute check

Leonie has five minutes. After high-risk verification, she repairs one awkward transition and one repeated phrase. Style is allowed only because the core risk layers are already secure.

134. Practice Lab: harmful final edit

Maren changes “most students” to “all students” because the sentence sounds stronger. The edit creates factual error. Her final rule becomes: every late change must name the defect it fixes. Stronger-sounding is not a defect.

135. Practice Lab: safe final non-edit

Iona sees a plain but correct sentence and considers rewriting it. She cannot identify a problem. She leaves it. Deliberate non-change protects the script.

136. Practice Lab: clean run, no recovery needed

Leonie decodes, plans, drafts, reaches each checkpoint and finishes early enough to verify. Recovery skills remain unused. This is success. The timing system should not manufacture crises merely because recovery has been trained.

137. Practice Lab: report needs longer planning

Maren faces a report with several findings and recommendations. She gives planning slightly more time because section jobs and evidence distribution matter. She compensates by using concise section-level plans, not full sentences. The phase budget adapts without abandoning the timing model.

138. Practice Lab: email can draft sooner

Iona’s email task has a clear recipient, request and short source pack. She completes a compact plan quickly and begins drafting. Equal planning time across all formats would be unnecessary rigidity.

139. Practice Lab: dense source pack

Leonie receives a dense stimulus and spends slightly more time selecting evidence. She avoids copying every source detail into the plan. The timing system adjusts at the source-selection phase while protecting first completion.

140. Practice Lab: sparse source pack

Maren receives little source material and begins hesitating about what else to say. She remembers that Development can work through significance and relation without invention. Sparse sources should not create longer planning simply because the student feels there is “not enough”.

141. Practice Lab: unfamiliar audience

Iona needs extra seconds to settle the relationship stance. Once the register anchor is fixed, she proceeds. Re-deciding politeness in every sentence would multiply the audience cost.

142. Practice Lab: unfamiliar topic

Leonie feels slower because the topic is technical. She resists compensating with broad rereading. She uses source labels, simple accurate vocabulary and the normal phase sequence. Timing stability under unfamiliarity is part of transfer readiness.

143. Practice Lab: paper medium recovery

Maren discovers a misplaced sentence on paper. Moving it physically would create clutter. She repairs forward with a clarifying transition and avoids duplicating the content later. Recovery respects the medium’s editing cost.

144. Practice Lab: digital medium recovery

Iona can move a paragraph easily in a digital interface. After moving it, she checks pronouns, transitions and source references. Cheap relocation does not eliminate downstream cohesion risk.

145. Practice Lab: keyboard stall

Leonie makes repeated typing corrections that interrupt thought. She lowers local sentence complexity and postpones cosmetic typo repair unless meaning is affected. Mechanical execution should not steal the cognitive budget from task completion.

146. Practice Lab: handwriting slowdown

Maren’s handwriting becomes slower late in the task. She uses shorter sentence structures and avoids unnecessary rewriting. The language system adapts to mechanical constraints while preserving meaning.

147. Practice Lab: false sense of security after fast drafting

Iona finishes early and assumes the task is strong. Her first-completion scan reveals a missing eligibility condition. Speed without verification is not timing mastery. Reserve converts fast completion into reliable completion.

148. Practice Lab: slow drafting but stable completion

Leonie writes more slowly than a classmate but completes every requirement, preserves language control and has a small reserve. Her raw words-per-minute rate is not a problem. Timing should be evaluated by task state and stability, not comparison with others.

149. Practice Lab: delayed recovery practice

Maren practises a missing-condition recovery today and succeeds. A week later, a different task includes a late eligibility discovery. She still repairs locally without panic. The recovery routine is becoming transferable rather than remembered from one exercise.

150. Practice Lab: ordinary finish

Iona reaches the final paragraph on schedule, writes it with the same sentence quality as the middle, reaches first completion, checks the high-risk categories and stops. Nothing dramatic happens. That uneventful finish is the visible result of a mature timing system.

Technical Appendix A: Phase-budget design

A transferable timing plan should identify phases rather than impose one universal minute formula. The phases are: orient and decode; build the execution plan; draft toward first completion; run a completion scan; use remaining reserve for targeted verification. The proportion assigned to each phase depends on the examination’s total time, marks, source density and format.

Start from the end. Decide what minimum verification window is useful, then work backward to the latest safe first-completion point. From there estimate the drafting window. Orientation and planning must fit before it. This backward method makes checking a designed state while still allowing the reserve to be partially converted into drafting time if first completion is endangered.

Budgeting should be trained with variation. A dense report source may justify a larger orientation share than a short email task. An unfamiliar form may need a slightly larger planning share. What should remain stable is the existence of all phases and the protection of first completion.

Teachers should record where real scripts exceed their budgets. If three students all lose time in source rereading, the solution may be source-routing practice. If one student loses time only in sentence rewriting, the budget is not the primary defect. Phase data should lead to mechanism diagnosis.

Technical Appendix B: Checkpoint matrix

Checkpoint 1 — after planning: every required job has a home, the main evidence anchors are known, the action is clear. Checkpoint 2 — middle: drafting remains ordinary, the remaining route is visible and no local stall has become global. Checkpoint 3 — before the final third: major late jobs are protected and serious time debt has been identified if present. Checkpoint 4 — first completion: all required communication exists and reserve allocation can begin.

Each checkpoint should have a small branch set. On time: continue normally. Mild debt: stop optional polishing and compress low-value elaboration. Serious debt: enter recovery mode, protect required jobs and use simpler syntax. Ahead: bank the surplus. Checkpoints are useful because each result maps to a known action.

Do not create so many checkpoints that monitoring becomes a second task. A checkpoint should occur when a decision about strategy could reasonably change. Between checkpoints, the writer should work rather than measure.

Checkpoint practice can be separated from full writing. Give students partial drafts and a fictional clock state, then ask what they should do next. This trains strategy selection before real pressure makes the choice emotionally loaded.

Technical Appendix C: Time-debt taxonomy

Reading debt: too much global rereading or repeated source search. Planning debt: over-detailed plans, alternative versions, sentence drafting. Opening debt: repeated rewrites before later work exists. Language debt: vocabulary retrieval, sentence rescue or grammar correction loops. Development debt: optional examples and repeated significance. Checking debt: reassurance rereading during drafting. Decision debt: too many unresolved choices carried into the final third.

The taxonomy matters because the same symptom—being five minutes behind—can require different repairs. Reading debt is treated by narrowing search; language debt by safe paraphrase and simpler syntax; development debt by stopping rules; decision debt by stronger planning and state preservation.

Time debt should be logged after practice. Record not only how late the student was, but where the minutes went. The goal is not to punish slow phases; it is to distinguish necessary cost from avoidable leakage.

A student can also have negative debt—unused surplus created by rushed underdevelopment. Finishing early is not automatically good. Timing quality must be judged alongside task fulfilment, development sufficiency and language stability.

Technical Appendix D: Stall decision tree

1. Name the blocked operation. Word, source, paragraph job, format, sentence, relationship or confidence?
2. Ask whether the block threatens meaning. If not, use a safe placeholder or simple alternative and move.
3. Ask whether the block is local. If yes, contain it; do not reopen the whole task.
4. Apply the lowest-cost recovery. Paraphrase, simplify, local reread, restate job, label source, or reset register.
5. Use the stall ceiling. If no progress after the threshold, preserve state and move.
6. Return by value. High-risk condition or action before low-value vocabulary upgrade.

The decision tree should become automatic enough that “stuck” quickly turns into a category. This is one reason deliberate recovery drills matter: the student is building a library of responses before the examination clock makes diagnosis expensive.

Stall recovery should not become overcomplicated. If the student cannot remember a seven-step protocol under pressure, compress it to: name → contain → simplify → move → return if valuable. The full model is for training; the exam behaviour should be low-load.

Technical Appendix E: Skip-and-return state protocol

When something is skipped, preserve three pieces of information where practical: what is unresolved, why it matters and what evidence or decision is already known. Example: “word choice only; meaning complete; maybe replace ‘easy to reach’.” Return is now optional. Another: “eligibility condition missing; must verify poster small print.” Return is mandatory and high priority.

The protocol distinguishes cosmetic flags from semantic flags. Cosmetic flags can disappear if no reserve remains. Semantic flags—condition, source, required action, date, negation—belong near the top of the return queue.

Digital and paper media need different flag behaviours. Digital systems may support comments or markers; paper may use a small symbol or blank. The chosen mark should be fast and unambiguous. Elaborate coding systems can cost more than they save.

The return queue should be closed after checking. Unresolved low-value flags should not tempt risky last-second edits. A flag means “consider returning”, not “must change”.

Technical Appendix F: First-completion protocol

First completion is reached when the response has a usable opening, every required development job, necessary practical information, the requested or recommended action, and a functional closing. It is a state of task existence, not a claim that every sentence is final.

Immediately after first completion, run a rapid whole-task scan: required points present? Any obvious blank? Any unfinished sentence? Any marked semantic flag? Any critical date or condition unchecked? This scan is designed to find certain loss before detailed proofreading begins.

If a major omission is found, the response returns temporarily to drafting state. Repair the missing job before spending time on lower-risk editing. If the script is complete, transition into reserve triage.

Students should practise recognising first completion explicitly. Some continue expanding because they do not realise the task is already complete; others stop too early because the page “looks long enough”. The state should be defined by required communication jobs, not appearance.

Technical Appendix G: Reserve-triage protocol

Reserve time should be allocated by expected return. Tier 1: completion defects—missing point, blank, unfinished sentence, wrong action. Tier 2: meaning risks—condition, quantity, source ownership, negation, modality, date. Tier 3: sentence stability—run-on, broken reference, tense drift. Tier 4: lexical or cohesion improvement. Tier 5: stylistic preference.

The reserve is not required to reach every tier. One minute may cover only Tier 1 and a handful of Tier 2 checks. Five minutes may allow Tier 3 and selected Tier 4 repairs. A long reserve can support broader polishing, but only after high-value risk is secure.

Students should know their personal Tier 2 hotspots. A learner who repeatedly drops eligibility conditions should scan conditions first. Another who changes “most” to “all” should scan quantifiers. Personalisation raises return without increasing check length.

Reserve triage ends with a stop decision. If no named high-value defect remains, submit. Continued stylistic experimentation has negative expected value when it can create new errors.

Technical Appendix H: Final-third diagnostic

Compare the first, middle and final third of the script on five measures: requirement depth, sentence stability, source accuracy, register consistency and correction frequency. A visible late decline should be diagnosed before calling it “bad time management”.

If the final third improves when early rewriting is reduced, the cause was early overcost. If decline begins after one difficult sentence, confidence shock is plausible. If decline appears at a similar elapsed duration across well-paced tasks, endurance may be involved. If late paragraphs contain many deferred decisions, decision debt is the stronger explanation.

Training follows the diagnosis. Early-overcost students practise ceilings and stopping rules. Confidence-shock students practise local resets. Decision-debt students practise stronger planning and state preservation. Endurance cases practise longer integrated work only after the other explanations are controlled.

The diagnostic prevents the simplistic instruction “write faster at the end”. Final-third control improves when the mechanism causing late degradation is changed earlier in the system.

Technical Appendix I: Teacher protocol for timing and recovery

1. Measure phases before prescribing speed. Record orientation, planning, drafting, first completion and checking states.
2. Name the source of time debt. Reading, planning, language, development, checking, decision or mechanical cost.
3. Protect first completion. Do not reward polished beginnings that cause missing late requirements.
4. Teach checkpoints as decisions. On time, mild debt, serious debt and ahead should each trigger known actions.
5. Train local recovery. One stall should remain one stall rather than becoming global panic.
6. Use deliberate disruptions. Practise missing conditions, late source corrections, vocabulary stalls, wrong audience and time debt.
7. Include clean simulations. Recovery skill should restore normal work, not create a permanent crisis mindset.
8. Separate knowledge from execution. If a learner knows the correct decision untimed, practise retrieval under the clock rather than reteaching from zero.
9. Use personal risk maps. The final checking queue should reflect recurring high-cost errors.
10. Fade scaffolds. External time calls and teacher prompts should gradually become internal checkpoint behaviour.

Teacher feedback should describe the execution mechanism. “Poor time management” is too broad. Better feedback is: “You spent four extra minutes rewriting the opening and then underdeveloped the recommendation,” “You reread the full source three times after the necessary evidence was already identified,” or “One vocabulary stall became global rushing.” Mechanism language gives the student something trainable.

Use video, screen recordings, visible timing notes or teacher observation where appropriate to reconstruct the process. A finished script alone shows the damage but not always its timing cause. Two equally incomplete responses may come from very different execution failures.

Teachers should preserve genuine deliberate pace. A student who writes more slowly but completes reliably and controls language may not need generic speed work. The target is sufficient throughput for the assessment, not speed ranking inside the class.

When introducing a recovery behaviour, practise it first without full task pressure. A vocabulary stall drill may last two minutes; an omission-recovery drill may use a nearly complete response. Only after the response becomes automatic should it be embedded inside full timed work.

Technical Appendix J: Self-study timing protocol

A self-studying learner can keep a short execution log after timed work. Record: when drafting began; midpoint state; first-completion time; checking time; largest stall; main source of time debt; one successful recovery; one harmful edit. The log should be compact enough to use consistently.

Do not diagnose from one run. Compare several unseen tasks. If planning repeatedly consumes too much time, that pattern is stronger evidence than one difficult source pack. If the final third repeatedly weakens despite stable pacing, the learner can investigate endurance or decision overload.

Choose one timing variable per practice cycle. For opening overinvestment, impose an opening ceiling. For broad source rereading, use local-search rules. For excessive checking, require a named check target. For time-debt panic, rehearse mild and severe debt branches. Narrow changes are easier to verify than a generic attempt to “be faster”.

Retest on fresh material after several days. A recovery routine is not stable because it worked once immediately after being taught. It is stable when a new stall triggers the same useful response without an external reminder.

Technical Appendix K: Parent support without becoming the clock

Parents can support timing practice by asking what consumed the minutes rather than repeating “write faster”. After a practice task, ask: When did you first fall behind? What were you doing then? Did you know what remained? What did you change? Did the final paragraph feel different from the first?

Avoid constant external time warnings during every practice. If a parent calls out every minute, the learner may become dependent on outside monitoring. Use a few agreed checkpoints, then reduce prompts as the student learns to manage time state independently.

Parents should not judge success only by whether the task finished early. An early finish with missing reasoning or no check can be as problematic as a late finish. Look for complete requirements, stable final-third quality and a short intentional verification phase.

When the learner freezes, resist supplying the exact word immediately. Ask whether a simpler accurate phrase can keep the task moving. This reinforces recovery instead of rewarding stall dependence.

Technical Appendix L: Six-week Timing and Recovery programme

Week 1 — Baseline and phase map. Run two unseen tasks without intervention. Record orientation, planning, drafting, first completion, checking, stalls and final-third quality. Identify the primary debt source rather than changing multiple variables immediately.

Week 2 — Planning and opening ceilings. Compress plans to paragraph jobs and evidence anchors. Cap opening revision. The objective is to reach the first major development paragraph earlier without reducing task accuracy.

Week 3 — Stall recovery. Use focused drills for vocabulary loss, sentence overload, local source uncertainty and format unfamiliarity. Practise name → contain → simplify → move. Record whether stalls remain local.

Week 4 — Time-debt branches. Start partial simulations at on-time, mild-debt and serious-debt states. The learner must choose the correct compression level, protect mandatory jobs and avoid unnecessary global speeding.

Week 5 — First completion and reserve. Practise reaching the end with a small reserve, then run Tier 1–5 checking. Track harmful final changes and the number of high-value defects actually recovered.

Week 6 — Full transfer. Mix unfamiliar topics, source densities, audiences and forms. Include clean runs and one or two deliberate disruptions. Readiness means the phase model bends without breaking and late quality remains recognisable.

Technical Appendix M: Twelve-week progression from external timing to internal state control

Weeks 1–2: map baseline phase costs and separate necessary time from leakage. Weeks 3–4: compress planning, establish opening ceilings and train local source search. Weeks 5–6: build stall ceilings, safe paraphrase and sentence-simplification recovery.

Weeks 7–8: train mild and serious time-debt branches, return-queue value and minimum viable completion. Weeks 9–10: strengthen first-completion recognition, reserve triage and final-third diagnostics. Weeks 11–12: use full unseen simulations with variable form, source density, medium and audience.

External scaffolds should fade in stages. At first, a teacher may announce checkpoints. Next, the clock is visible but no calls are given. Finally, the learner manages phase state independently. The objective is not to memorise timestamps; it is to know what state the task should be in when the clock reaches meaningful landmarks.

Progression should also fade emergency language. Early learners may use a written recovery card. Advanced learners should need only a compact internal sequence: local problem, low-cost repair, required jobs, first completion, risk-based check.

Technical Appendix N: Timing and Recovery performance dashboard

A useful dashboard can track: orientation cost, planning cost, first-completion time, reserve length, stall count, largest stall duration, return-queue size, final-third error change, completion rate, harmful final-edit count and recovery containment.

Do not optimise every metric simultaneously. If completion is unreliable, first-completion time and unfinished-job count matter more than elegant checking. If completion is stable but late errors remain, final-third quality and reserve use become more informative.

Use three states—unstable, developing, reliable—rather than false precision where exact numbers add little. A learner can be reliable in completion but developing in stall containment. Another can be fast in planning but unstable in reserve checking.

The dashboard should expose hidden progress. A student’s total writing time may remain unchanged while broad rereading disappears, first completion moves earlier and final-third errors fall. The same clock time can contain a much stronger execution system.

Technical Appendix O: Full walkthrough — early overinvestment creates late collapse

Maren begins a timed situational-writing task with a correct plan. She then spends too long refining the opening, rewrites the first development paragraph twice and checks vocabulary as she goes. At the midpoint she is only slightly behind by the clock, but two high-value communication jobs remain untouched. The final third becomes compressed and her recommendation is underdeveloped.

Diagnosis: the visible late collapse begins earlier than the late paragraph. The first weak link is early overcost. Her language knowledge is not the problem; the task is paying too much for already-acceptable prose. The repair therefore begins with an opening ceiling and a drafting edit threshold.

Cycle 1: Maren must accept the first accurate opening once purpose and reader are visible. She may correct a meaning defect immediately but cannot rewrite for rhythm before first completion. Her first-completion time moves earlier, and the recommendation receives enough evidence and feasibility discussion.

Cycle 2: the same rule is tested on an unfamiliar topic. She initially wants to reread because the prose feels less fluent. Instead she checks whether the meaning is accurate, then continues. The final third remains stable despite lower subjective confidence.

Cycle 3: the opening ceiling becomes internal. Maren no longer counts rewrites; she recognises when the reader has enough orientation. The timing gain is not spent on more early detail. It becomes reserve until first completion.

The longitudinal lesson is that “late weakness” can be a resource-allocation problem originating early. Training final-third speed alone would treat the symptom. SW-100 reconstructs the whole execution path.

Technical Appendix P: Full walkthrough — mid-draft source misread with local recovery

Iona is halfway through a proposal when she notices that a survey percentage applies only to club members, not all students. The first paragraph correctly establishes the event and audience. The second paragraph uses the mis-scoped statistic to justify Thursday. Later logistics do not depend on the statistic.

Step 1 — contain. Iona does not reopen the entire task. She identifies the first wrong state: population scope in one evidence sentence. Step 2 — repair dependent meaning. She changes “students” to “surveyed club members” and recalibrates the conclusion so it no longer sounds school-wide.

Step 3 — preserve valid architecture. The recommendation paragraph still belongs in the same place. Venue capacity, deadline and action remain valid. No full restart is needed. Step 4 — update the return queue. She flags the final conclusion for a quick scope check because it may repeat the broad claim.

Step 5 — resume ordinary work. The correction takes less time than a full reread and prevents the error from spreading. At first completion she checks the conclusion, confirms the population is correctly bounded and removes the flag.

This walkthrough shows recovery as state containment. The misread matters, but only the dependent branch is repaired. The clock is protected because the student can distinguish invalid work from unaffected work.

Technical Appendix Q: Full walkthrough — serious midpoint debt and minimum viable completion

Leonie reaches the midpoint of a task with the opening and one development paragraph complete. Two required development jobs, practical details and the closing remain. The source has been decoded correctly, but she spent too long on a difficult sentence and a comparison paragraph. This is serious debt because several required jobs remain.

Recovery mode begins. She stops stylistic correction immediately. Each remaining high-value paragraph gets a minimum execution pattern: required point → decisive evidence or reason → material condition if any → move. She chooses sentence structures she can write reliably without further syntax experiments.

Development is compressed selectively. The main recommendation receives one strong reason and one feasibility condition. A secondary benefit that would normally receive an example remains one sentence. Practical details are grouped accurately. The closing states the required action directly.

The reserve becomes flexible. Leonie originally planned several minutes of checking. Part of that reserve is converted into completion time. She reaches first completion with a shorter check window rather than preserving an empty reserve while the response remains incomplete.

Final triage: she verifies required content, deadline, condition, one source attribution and the closing action. She does not improve vocabulary. The final response is less polished than her ideal version but remains complete, accurate and usable.

Minimum viable completion is an emergency floor, not a standard drafting style. Its value appears when the alternative is leaving mark-bearing communication unwritten.

Technical Appendix R: Full walkthrough — one-, three- and five-minute reserve branches

Use the same completed draft and imagine three reserve states. The script contains one wrong date, one vague pronoun, one repeated phrase, one slightly awkward connector and a correct but plain recommendation sentence.

One minute: scan completion and task-critical meaning. The wrong date is corrected. The vague pronoun is repaired if immediately visible. Repetition, connector and plain recommendation remain untouched. The student stops when time expires.

Three minutes: after correcting the date and pronoun, check conditions, quantities, modality and sentence boundaries. The connector is corrected only if its logic is genuinely wrong. The repeated phrase remains if it is harmless.

Five minutes: the same high-risk checks occur first. With reserve still available, the repeated phrase may be compressed and one awkward transition improved. The correct plain recommendation is still left alone because no defect has been identified.

The branch model teaches that checking quality is not measured by how many sentences are changed. A shorter reserve can still be highly effective if it targets the highest-return defects first.

Technical Appendix S: Medium and format transfer

Email: orientation may be shorter when reader and purpose are direct; the timing risk can shift toward wording a sensitive request. Report: planning may need more visible section jobs and evidence distribution. Speech: drafting may require slightly more listener-facing phrasing, but the phase system remains decode → plan → draft → complete → verify.

Paper: structural relocation is expensive, so planning quality and forward recovery matter more. Crossed-out rewrites can reduce space and legibility. Digital: paragraph movement and local correction may be cheaper, but scrolling, cursor placement and accidental deletion create different risks. Recovery should reflect the medium without changing the communication priorities.

Timing systems should be practised in the actual or closest available medium. A student who always drafts digitally may underestimate handwriting slowdown; a student trained only on paper may not practise digital navigation, scrolling or answer-field constraints.

Format and medium can change local cost, but they do not change the canonical job of SW-100. The student still needs a usable budget, visible checkpoints, stall containment, first completion, reserve triage and a stop rule.

Technical Appendix T: How SETC-SEC-SW-100 connects to the lane

SETC-SEC-SW-100 owns the execution layer after the earlier communication systems exist. 010 Task Decoding determines role, audience, purpose, context and requirements. 020 Source Transformation determines what stimulus information can legitimately mean. 030 Task Fulfilment protects complete coverage.

040 Audience and Register controls relationship stance. 050 Information Architecture places content into paragraph jobs. Decision Architecture controls the reader’s judgement path. Format Transfer adapts the communication across interfaces.

Development and Elaboration controls reasoning depth. 090 Language Control protects grammar, reference, cohesion, modality, vocabulary and editing inside the sentence system. SW-100 does not replace those owners. It decides how the whole system is scheduled, protected and recovered under finite time.

Qualification-specific children may use exact timings appropriate to their current specifications. Those pages remain distinct. SW-100 owns the transferable timing-and-recovery mechanics above them.

Final principle: protect the unfinished work before polishing the finished work

Maren asks what remains unwritten and whether the plan still has a visible route. Iona asks which unresolved conditions, requirements or evidence relationships can still change the message. Leonie asks what the clock state permits, which stall must be contained and where the next minute has the greatest expected return.

The mature writer does not try to be fast everywhere. She spends enough time to make the right decisions, refuses to let local problems spread, reaches first completion while meaningful reserve remains, and checks the highest-risk parts before touching style.

PROTECT THE UNFINISHED WORK BEFORE POLISHING THE FINISHED WORK. WHEN THE TASK IS COMPLETE, SPEND THE RESERVE WHERE ONE MINUTE CAN STILL CHANGE THE MOST.

Advanced Timing and Recovery Lab 1: same clock position, different unfinished-job load

Maren and Iona both reach the midpoint at the same minute. Maren has completed the opening and two major development jobs; Iona has completed the opening and only one. Their clock position is identical, but their task states are not. Maren can remain in normal mode; Iona needs compression. Timing decisions should follow unfinished work as well as elapsed time.

Advanced Timing and Recovery Lab 2: same time debt, different cause

Leonie and Maren are both three minutes behind. Leonie lost time to source rereading; Maren lost time to rewriting sentences. Leonie’s repair is local evidence search. Maren’s repair is an edit threshold and simpler syntax. “Three minutes behind” is a symptom, not a diagnosis.

Advanced Timing and Recovery Lab 3: ahead because the response is underdeveloped

Iona reaches first completion unusually early. The script contains every required point, but major recommendations are bare. The surplus is not automatically a success signal. She uses reserve to restore minimum sufficient development before lower-value style checking. Timing quality must be read together with content quality.

Advanced Timing and Recovery Lab 4: behind because high-value work is being done correctly

Leonie is slightly behind because a dense source required careful comparison of two conditions. The cost is necessary rather than wasteful. She makes only mild adjustments elsewhere instead of forcing aggressive recovery. Not all delay is leakage.

Advanced Timing and Recovery Lab 5: one semantic flag and four cosmetic flags

Maren reaches first completion with five flags. One concerns an eligibility condition; four concern vocabulary preferences. She checks the eligibility condition first and may ignore the rest if reserve is short. Flag count matters less than flag value.

Advanced Timing and Recovery Lab 6: late wrong condition plus serious debt

Iona discovers that free entry applies only before a deadline while the final paragraph remains unwritten. She first corrects the condition where the benefit is stated, then completes the required action paragraph using simple syntax. She does not reread the entire response. Semantic repair and completion are sequenced by value.

Advanced Timing and Recovery Lab 7: late wrong audience plus mild debt

Leonie notices that two phrases are too casual for the committee reader. The overall relationship and content are correct. She resets from the current sentence, finishes the task and flags the two earlier phrases. Mild debt means local repair can wait until reserve rather than triggering a full stylistic rewrite.

Advanced Timing and Recovery Lab 8: late wrong format assumption

Maren planned a report-like response but the required output is a short email. The semantic spine is correct. She does not restart the evidence analysis. She compresses sectioning into paragraph jobs, foregrounds the request and continues. Format recovery reuses valid decisions instead of discarding them.

Advanced Timing and Recovery Lab 9: accidental digital deletion

Iona accidentally deletes part of a paragraph. She first restores the required proposition and condition rather than trying to reconstruct every original word. The recovery target is communication state, not textual memory. Once meaning is restored, she resumes the plan.

Advanced Timing and Recovery Lab 10: handwriting correction overload

Leonie’s paper draft becomes crowded with crossings-out. Further local rewriting risks legibility. She shifts to forward repair: complete the next sentence cleanly, use a short clarification if needed and avoid cosmetic editing. Medium constraints change the cheapest recovery.

Advanced Timing and Recovery Lab 11: clock is hidden or difficult to see

Maren cannot monitor the clock as frequently as planned. She relies more heavily on task-state cues: paragraph route, remaining requirements and planned reserve point. Timing competence should not depend entirely on constant visual clock access.

Advanced Timing and Recovery Lab 12: uncertain remaining time

Iona is unsure whether three or five minutes remain. She uses the more conservative branch: check completion and Tier 2 meaning risks first. If more time proves available, she continues to sentence stability and style. Uncertainty should increase priority discipline, not panic.

Advanced Timing and Recovery Lab 13: timer checking becomes a distraction

Leonie uses a digital countdown and looks at it after nearly every sentence. The timer creates attentional switching cost. She changes to a few phase alarms or deliberate glance points. Monitoring is valuable only when it can trigger a meaningful strategy branch.

Advanced Timing and Recovery Lab 14: transition stall versus content stall

Maren knows the next paragraph’s content but cannot find a graceful transition. This is a low-value wording stall, not a content stall. She uses a plain transition or begins directly. If she did not know what the next paragraph must say, the problem would be architectural and deserve a different recovery.

Advanced Timing and Recovery Lab 15: perfect plan, unexpectedly dense source detail

Iona’s plan is strong, but one source section contains a condition she did not initially notice. She updates the relevant paragraph and action line without rebuilding the entire plan. A good timing system allows the plan to be revised locally when new information becomes material.

Advanced Timing and Recovery Lab 16: fast writer, inaccurate state

Leonie drafts quickly and reaches first completion with a large reserve, but has lost two conditions and broadened one statistic. Her problem is not insufficient speed. The reserve must be used for source and condition verification, and future training should protect semantic control during rapid drafting.

Advanced Timing and Recovery Lab 17: slow writer, stable state

Maren writes slowly but consistently reaches first completion with every required job intact and a short check. Forcing a higher words-per-minute target may create unnecessary language risk. The performance is acceptable if it fits the actual examination window reliably.

Advanced Timing and Recovery Lab 18: reserve with no flags

Iona reaches first completion with reserve and no unresolved items. She still performs the completion and high-risk scans, but she does not invent things to change simply because time remains. A clean script is allowed to stay clean.

Advanced Timing and Recovery Lab 19: reserve with one semantic flag

Leonie has one flagged population-scope issue and several minutes available. She resolves that flag before broad rereading. Once the high-value uncertainty is closed, remaining time can be used on normal risk checks.

Advanced Timing and Recovery Lab 20: final check finds wrong quantifier

Maren sees “all respondents” where the source says “most respondents”. One-word correction recovers a major evidence boundary. This is a high-return edit and exactly the kind of risk reserve time should target.

Advanced Timing and Recovery Lab 21: final check finds missing negation

Iona finds “students need to register again” instead of “do not need to register again”. The correction reverses the instruction. High-risk tokens such as not, only, must and may deserve priority because tiny edits can recover large amounts of meaning.

Advanced Timing and Recovery Lab 22: final check finds only a cosmetic issue

Leonie dislikes a repeated word but the sentence is clear. With seconds left, she leaves it unchanged. Timing maturity includes recognising when the expected return of editing is lower than the risk of introducing a new problem.

Advanced Timing and Recovery Lab 23: midpoint reset after confidence shock

Maren receives a difficult stimulus detail and starts doubting her earlier work. She uses the midpoint reset: identify what is actually uncertain, confirm the remaining paragraph route and resume the next known job. The reset prevents one difficult item from changing global pace.

Advanced Timing and Recovery Lab 24: recovery transfers to an unfamiliar task

Iona previously practised sentence-stall recovery on a school-event topic. An unfamiliar environmental task later produces the same structural stall. She still simplifies the sentence and moves. Recovery has transferred because it is tied to the blocked operation, not the topic.

Advanced Timing and Recovery Lab 25: clean run after disruption training

Leonie completes a full task with no major stalls after several weeks of recovery drills. She does not deliberately use the emergency routines. Their value is partly invisible: knowing that recovery exists reduces the need to overcheck or panic when small uncertainty appears.

Advanced Timing and Recovery Lab 26: final third stabilised through simpler syntax

Maren previously produced late run-ons. She now deliberately reduces clause load after the final checkpoint. Her vocabulary and reasoning remain strong, but sentence structures become safer. Final-third stability improves without forcing her to write faster.

Advanced Timing and Recovery Lab 27: mild debt recovered without thinning the core

Iona is slightly behind. She stops optional wording refinement and removes a secondary example, but keeps the main recommendation’s evidence and condition. She returns to schedule without turning the response into minimum viable mode. Severity calibration protects quality.

Advanced Timing and Recovery Lab 28: severe debt branch

Leonie reaches a checkpoint with several required jobs untouched and little reserve. She activates the emergency floor: one accurate sentence for each required point, one decisive reason for the central recommendation, necessary conditions, clear action, simple closing. Completion becomes the priority.

Advanced Timing and Recovery Lab 29: overcompressed recovery creates new underdevelopment

Maren enters recovery mode too aggressively and reduces the main recommendation to a bare claim. She learns that emergency compression still needs minimum sufficiency. Recovery should remove optional depth before removing the reasoning that earns the decision.

Advanced Timing and Recovery Lab 30: the timing system becomes low-load

Iona no longer consciously recites every phase rule. She begins with a compact plan, notices the midpoint, contains a local word stall, reaches first completion and checks her known high-risk categories. Afterward she can explain the system, but during writing it operates with little conscious overhead. That automatic state is the intended endpoint.