Exit Is Not a Remedy Invented After Failure
At 09:45 Friday, V3’s first stage is executable. On Monday the team will use one slot and the remaining one unit of the initial payment to check working conditions, C1’s reference state, the S-3 reading, and whether G2’s first segment can be carried forward.
If the team waits until it sees Monday’s results to discuss exit, window pressure, the fact that another slot has already been used, and each person’s hopes will all enter the rule. The same reading may be interpreted differently with a different mood.
Gu Ning decides to complete exit card X17-1 on Friday. It neither predicts Monday’s failure nor expresses a lack of confidence. It turns unfavorable paths into executable actions.
All numbers remain part of the fictional Chengwan case. The card demonstrates an action-record structure and is not a real quality or contract standard.
First Distinguish Four Exit Actions
Stopping ends V3 production, seeks no new receipt window, and enters settlement of balances and records. Pausing temporarily withholds the next stage while awaiting specified material and includes a latest adjudication time.
Reduction preserves part of the objective while deliberately removing scope, input, or commitment. When joint agreement is required, an internal decision cannot declare the reduction complete. Rechecking reacquires material for a bounded object, number of attempts, and resource allowance; it does not imply continuation.
The four actions leave different consequences. Calling all of them “wait for now” leaves executors unable to know whether to release a workstation, notify the other party, or change the state of funds.
The card chooses an action type before specifying triggers and disposition rather than hiding every path behind one vague stop button.
Why Rules Are Easier to Write Before a Favorable Result
While the result remains unknown, the team can still separate “what material is sufficient to continue” from “we hope to continue.” After the result appears, people naturally attend to favorable explanations, progress, and loss of the window.
Writing in advance does not remove preference, but it leaves a comparison point. If new material later warrants a changed rule, a new version can state the reason; the original card cannot be silently overwritten.
The rule may be too strict or omit a case. Advance writing does not claim perfection. It makes amendment visible.
Gu Ning places the freeze time, participants, and source pages in the card header. Every Monday result is first adjudicated under the same version.
Exit Conditions Must Point to Protected Objects
“The risk feels too great” cannot be executed repeatedly. X17-1 first lists its protected objects: the eight-unit cash safeguard, seven committed slots next week, one recovery slot, the V1 list’s receipt conditions, and the duty to communicate truthfully.
For each trigger, the card states which object it threatens. Insufficient capacity threatens commitments and the recovery slot; failed entry threatens receipt conditions; a changed window makes the action object mismatch.
This linkage prevents the team from accumulating cautious-looking alarms unrelated to the action, and from deleting a protected object merely to meet a window.
Exit is not abstract aversion to loss. It changes action before an explicit floor is crossed.
The First Hard Stop Protects the Cash Line
If any new V3 release would reduce the shared safeguard available when needed below eight units, production stops. A possible final payment cannot substitute for it.
The current plan uses one conditional-balance unit for Monday’s review. If that passes, Tuesday uses at most one unit of original unallocated capacity. Under the current ledger, the safeguard remains eight.
An unexpected Monday expense, withdrawal of the conditional balance, or increased safeguard need from an existing task requires a new reconciliation. Total cash of thirteen does not mean all eight units are available at the required time.
The cash stop has no retest question. Accounts and authority adjudicate it, with Gu Ning and Tang Ke jointly responsible for checking.
The Second Hard Stop Protects the Capacity Line
Of ten slots next week, seven are committed and three unallocated. V3 may request at most two, leaving at least one uncommitted as recovery capacity.
If an existing commitment adds one slot, or V3’s review shows a total need above two slots, the old plan stops. The team may propose reduction or another cycle, but it cannot displace the sole recovery slot.
Once Monday’s review slot is used, two uncommitted slots remain. One stays protected, and only one may enter Tuesday. If review shows that the first segment must be repeated before the remainder is completed, two slots would be required and V3 would no longer fit.
The capacity line is adjudicated at actual schedulable times. Paper totals cannot be transported across a deadline.
The Third Hard Stop Protects the Entry
At Monday’s start, h must be within E0’s established range of 4.2 to 4.5, the absolute value of C1’s reference quantity must be no greater than 0.3, and d obtained under S-3 must be no greater than 2.0.
If any condition fails, the round stops. No check may be skipped to chase Tuesday’s window, and execution cannot occur first with inspection added later. The raw h, r, and d readings are saved separately rather than reduced to one failure label.
Passing the entry permits only the review of G2’s first segment. It does not release Tuesday’s slot or guarantee final delivery.
The rule comes from V3’s joint confirmation and internal stage gate. Its validity is limited to this object and is not stated as a real-world process law.
The Fourth Stop Addresses Version Mismatch
If the other party changes scope, window, total fee, acceptance, or disposition of the initial payment, V3 stops accepting ordinary updates. Under Chapter 18’s protocol, the team must create V4 or archive the object.
A favorable change also triggers it. If the other party offers one additional unit while adding list items, the team cannot update only revenue and retain the old labor estimate.
If the worksite cannot uniquely trace the file in use to V1’s list, it also stops. A passing reading cannot establish execution on the correct object when version identity is unclear.
The version stop protects the meaning of the result, not merely tidy documentation.
Failed Reusability Takes the Reduction Exit
After Monday’s entry passes, Ye Cheng checks G2’s first-segment object identifier, process record, exposure to conditions, and unfinished interface against the list. Only all four passing permits carryover.
If the only issue is a repairable record gap and one recheck can finish within Monday’s already released slot, the recheck is allowed once. The original gap and supplementary material remain side by side.
If the first segment must be repeated, another half-day slot is needed, or the object changes, Tuesday’s slot is not released. V3’s original production path stops. The team may only propose a smaller receipt scope or another later version.
Reduction requires the other party’s confirmation. Chengwan may propose it; it cannot call a partial delivery complete on its own.
Rechecking Needs an Attempt Limit
Near a threshold, unlimited repetition may eventually produce a favorable reading. X17-1 permits one repeat reading on the same item only when an equipment-state alert or an operational interruption is recorded.
A normally completed first failure triggers stopping directly and is not overwritten by an average. If a repeat occurs, both raw values are preserved and the result follows a method written in advance.
A gap in reuse records likewise allows only one bounded check. Records that never existed cannot be repeatedly reconstructed. Any field that cannot be completed remains unknown.
The attempt limit turns rechecking from a search for passage into an answer to a specific doubt.
A Pause Must Have a Deadline
If the team is waiting Monday for the other party to confirm a proposed reduction, the pause lasts only until 16:00 Monday. Without confirmation by then, Tuesday’s slot is automatically withheld.
If it awaits C1’s state page or the original version index, the latest adjudication point is the end of Monday’s review slot. An absent record remains a failure; “it may be found later” cannot count as passing.
During the pause, the team may not occupy Tuesday’s workstation, prepare materials, or promise completion. Otherwise nominal suspension creates a commitment in fact.
The default action at the deadline is written on the card, preventing an indefinite wait.
Exit Must State How Resources Are Disposed
Once Monday’s review occurs, its slot and one conditional-balance unit enter actual use. Even if the entry fails, they do not return to uncommitted status.
Tuesday’s unreleased slot remains schedulable, including the one already designated as recovery margin. The one original unallocated unit proposed for Tuesday stays in cash.
If no initial-payment balance remains after review, later stopping need only confirm that the final payment was not triggered and settle existing results. If actual use is less than one unit, the difference still follows the parties’ terms; it does not automatically become income.
After an exit action, mutually exclusive resource categories must be restated. “Loss contained” is not an adequate ledger entry.
Who Is Responsible for Saying Stop
Ye Cheng owns site readings and object checks. She may stop operation when an entry condition fails but may not change the threshold. Tang Ke owns versions and external notice and may block release when an external field mismatches.
Gu Ning owns capacity, cash, and final stage authorization. Any hard stop may suspend work without a three-person vote; resumption requires the corresponding condition to pass again.
If two people disagree about a factual record, both raw records are preserved and the action pauses. A senior person may not select the favorable value.
The authority design makes stopping happen under pressure instead of leaving all responsibility to an undefined “team.”
An Exit Notice Need Not Explain the Entire Cause
After a stop is triggered, external notice states the object, time, unmet condition, and next state. It need not declare a unique mechanism before that mechanism is known.
If h exceeds E0, the accurate statement is “this round’s entry condition was not met, so production was not released,” not “the environment caused the material to fail.” The first follows from rule and reading; the second requires more mechanistic evidence.
If the capacity line caused the stop, it should not be described as a technical failure. The category of reason affects whether the other party might change the window, reduce scope, or close the engagement.
A truthful, bounded explanation protects both collaboration and later analysis from being trapped by an early story.
Favorable Results Also Trigger Review Points
The exit card does not list only bad results. After entry and reusability both pass, Monday’s stage closes. Before Tuesday’s slot is released, the window, resource state, and validity of the entry must be reviewed again.
If working conditions change from Monday to Tuesday, the prior reading cannot remain valid indefinitely. V3 requires new h and r readings at Tuesday’s start and an S-3 check of the current object.
This review occurs at the beginning of Tuesday’s slot and does not add a third slot. If it fails, work stops immediately; prepared time is not a reason to continue.
A favorable result only advances action to the next gate. It does not delete later exits.
Separate Exit Lines from Warning Lines
The team adds an alert: when h reaches 4.5, mark “near E0’s upper boundary” and inspect the work-condition record early. The value remains within the permitted range and does not by itself fail.
A warning increases attention or preparation; an exit line changes authority. Mixing them may cause an executor to treat advice as a mandatory stop, or to ignore a real gate after too many alarms.
V3 has no additional gray zone for d because the parties confirmed only the 2.0 line. A gray zone may be discussed later but cannot be added unilaterally on the eve of execution.
The card uses yellow for warnings and red for stops, while its text remains authoritative. Color has no independent meaning.
Hard Constraints Prevail When Rules Conflict
Suppose the entry passes and the other party confirms the window, but the cash safeguard is insufficient. Release is still prohibited. Several positive conditions cannot cancel one hard stop.
If capacity permits but version identity is unclear, work likewise stops. Technical, resource, authority, and temporal constraints each have a veto position.
This does not reduce all risk to zero. The card protects only identified floors; unknowns may still appear after passage.
Gu Ning writes the order of priority on the card: survival and authority constraints precede stage passage; stage passage precedes progress and opportunity benefits.
Not Every Surprise Can Be Written into the Rules
Execution may produce a case the card does not cover. If it changes the object, a floor, or the meaning of the result, the default is to pause and create a supplement rather than force it into the most similar rule.
A minor record-format omission that changes neither object nor adjudication may follow the correction process. Significance must be explained through its affected relation, not inferred merely from novelty.
The exit card is processually complete: it covers important paths currently recognizable and leaves a default pause entrance for the unknown. It does not claim to enumerate the future world.
A supplement mechanism is more executable than “handle other situations as appropriate.”
Exit Costs Must Also Be Acknowledged in Advance
Stopping may lose Tuesday’s receipt opportunity, the three-unit final payment, and a chance to complete relational repair. It also takes time to explain, archive, and settle. These consequences do not disappear merely because they belong to exit.
Continuing, meanwhile, occupies the next slot and one unit and remains exposed to execution and changing conditions. Consequences on both sides enter the decision page; exit is not portrayed as free safety.
The card says that when specified floors are crossed, action does not continue even though these opportunity costs exist. Those floors are precisely what the team decided in advance not to trade away.
If the team later changes a floor, it must restate the protected obligation before a new action, rather than change its account when an opportunity appears.
Exiting Too Early Is Also an Observable Error
An overly strict rule may stop many tolerable actions and increase repeated startup and relational costs. Advance writing allows review of premature stopping as well as excessive persistence.
Review can ask whether the trigger recurred, whether target-relevant material appeared after stopping, and whether the protected object truly needed that margin. The answers serve future versions; they do not rewrite the past execution.
In D17, E0’s range comes from little material. It is suitable as V3’s conservative entry but does not automatically become a permanent standard.
Only an auditable exit rule keeps caution from becoming an unquestionable virtue.
Exit Conditions Make Optionality Real
In RC, preserving optionality is not a retrospective claim that another route is always available. It means preserving real authority to stop, reduce, recheck, and resume before resources are released. The exit card protects unlocked margin so that, when unfavorable feedback appears, the subject can still change the direction of convergence.
Freezing triggers in advance also resists a rule framework’s self-reinforcement. If results later require amendment, the amendment enters a new version. This permits continuous correction while preventing immediate pressure from quietly consuming future choice.
The State Table in X17-1
The card is arranged as check item, time, passing condition, action on failure, owner, resource disposition, and notice. Cash, capacity, version, and entry are hard stops. Reuse records allow one bounded recheck. A pending confirmation ends at 16:00 Monday.
Monday’s stage passes only when h, r, d, object identity, and reusability all pass. Tuesday’s release additionally requires a still-confirmed window, unchanged resources, and a current entry review.
Every action that has not occurred remains conditional. The card reserves no Tuesday slot, does not count the final payment as available cash, and does not assume completion next week.
At 10:20 Friday, the three sign the internal version and send its summary to the other party. At 10:31, the other party acknowledges the stopping rules without changing V3’s external fields.
Near an Exit Line Does Not Mean It Has Been Triggered
If Monday’s h is exactly 4.5, it remains within V3’s range. It triggers the yellow warning, not a stop. At 4.6 it lies outside E0 and stops the round. A difference of only 0.1 does not allow the team to merge the classifications at will.
This does not mean a natural process breaks between 4.5 and 4.6. Chapter 15 already showed that the discrete action comes from the rule. The warning state prompts the executor to verify the record and prepare to inspect again Tuesday.
Proximity to the boundary does not authorize advance consumption of more resources. Fear that tomorrow may cross the line cannot justify using the recovery slot today for unplanned intervention. Every improvement action needs its own cost and authorization.
Conversely, distance from one boundary does not cancel the other stops. With h=4.2, a version mismatch or insufficient cash safeguard still blocks production.
Deviation from a Rule Must Become an Explicit Event
The site may produce a sound new reason for believing the original card does not apply. X17-1 permits a proposed deviation, but the proposal itself immediately triggers a pause. Its reason, affected fields, and additional risks must first be written on a supplement page.
Action may continue only if Gu Ning and the relevant owner confirm a new version before resources are released. If the change also concerns external scope, window, or settlement, the other party must confirm it. Saying orally that “this case is special” changes no authority.
Anyone may stop immediately to protect people, equipment, or existing work without waiting for a supplement. Uncertainty expands stopping authority, not production authority, giving an unsafe case a clear default.
Deviation counts enter review. Frequent exceptions to the same rule indicate a mismatch between design and the site. Requests for exceptions only after unfavorable results may indicate that result preference is rewriting the boundary.
Rehearse the Paper Exit at the Table
At 10:45 Friday, Tang Ke offers three hypothetical scenarios. In the first, h=4.6, r=0.2, and d is unread. Ye Cheng should stop at h rather than continue occupying equipment merely to complete all three fields, leaving d blank as not obtained.
In the second, h=4.4 and r=0.4. Action stops at the reference-state line. A later d that might pass cannot override it. C1’s state must first be handled, and V3 releases nothing that round.
In the third, all three entry values pass, but G2’s first segment lacks a traceable object identifier. The team performs one search of existing records. If it remains absent at the end of the review slot, reuse fails; no identifier is reconstructed from memory.
Each person states the notice, funding state, and disposition of Tuesday’s slot. The rehearsal uses no half-day slot or working-capital unit and generates no actual reading. It verifies that different owners derive the same action from the text.
Completion of an Exit Also Needs a Definition
After a stop triggers, shutting down equipment does not complete the process. Raw readings must be saved, unreleased resources returned to the ledger, the other party given a bounded account, V3’s stage state updated, and the next adjudication point specified.
Ending V3 also requires settlement of the conditional balance and final-payment state. A pause must state what is awaited and until when. Without these actions, a project may stop operationally while occupying management attention indefinitely.
X17-1 gives every exit type a completion field. An executor closes an exit action only after record, resource, notice, and state are all checked.
Exit itself therefore undergoes acceptance rather than becoming an unowned “we stopped for now.”
Review Resources First at 08:40 Monday
At the start of the new week, the seven existing commitments have not increased. Cash remains thirteen, and the eight-unit safeguard is available. V3’s Monday review slot is released under the card.
Tuesday’s slot is still unreleased. The other party’s window remains confirmed, V1’s list index is traceable, C1’s state page is valid, and no version hard stop has appeared.
Ye Cheng prepares Q1 and C1 records, while Tang Ke opens the page for the original G2 first segment. Preparation occurs within Monday’s released slot and does not consume separate capacity.
Passing the resource check means only that entry may begin. It does not predict the readings.
How Monday’s Entry Is Adjudicated
At 09:10, work-record quantity h=4.4, within 4.2 to 4.5. C1’s reference quantity r=0.2, whose absolute value is no greater than 0.3. Under S-3, the current inspection item reads d=1.9, no greater than 2.0.
All three are adjudicated from their first complete records, with no repeat triggered. h lies within E0 but is not at the warning boundary of 4.5. Entry passes.
These results update V3’s Monday stage and create no new object. They also do not prove that h is the sole cause or that Tuesday must pass.
Only after entry passes does Ye Cheng begin the G2 first-segment reuse check, in the order specified by X17-1.
The Reuse Check Is Not Captured by Progress
The object identifier matches V1’s list, the process record is traceable, the Tuesday first-segment page contains the required steps, and the time of exposure to conditions can be aligned with the h log. All four pass.
Gu Ning does not weaken the check because “half is already done,” nor discard the first segment wholesale because Wednesday failed. Current material adjudicates reusability.
Monday’s stage therefore completes. One slot and the one-unit conditional balance are actually used, and G2’s first segment is marked reusable under V3. Cash falls from thirteen to twelve. Its mutually exclusive classification is now eight safeguarded and four originally unallocated; one of the latter remains planned for Tuesday but unreleased.
The week’s ten slots now comprise seven existing commitments, one V3 review slot used, and two uncommitted slots. One remains protected; the other becomes eligible for Tuesday.
Advance Exit Conditions Preserved a Real Exit
All positive conditions pass Monday, so neither stopping nor reduction is executed. The card’s value does not disappear because it was not triggered. The site does not need to renegotiate whether 2.0 is strict, whether to measure again, or whether to occupy Tuesday’s slot in advance.
Had any reading fallen on the other side, the same card would have blocked release. A rule becomes a testable action interface only when it remains consistent across favorable and unfavorable results.
At 10:40, Gu Ning closes Monday’s stage. Tuesday’s slot still requires same-day review before release. The final payment remains absent, while the cash safeguard and recovery slot remain intact.
The next chapter compares the switching costs of remaining on the current C1 path, moving to the Q1 control path, or using the still-unvalidated C2 if working conditions again approach the boundary. Alternative paths exist, but switching among them is not free.