Why Fourteen Units Do Not Mean Six Can Be Spent
At 16:30 Monday, Gu Ning created a margin ledger beside the stage table. The station began Monday with twelve working-capital units, received a first payment of three at 11:35, and spent one on the G1 sample. The visible balance was therefore fourteen.
Tang Ke said that leaving the protected eight untouched meant fourteen minus eight, or six; G2 needed only an estimated two, so the margin seemed ample. The subtraction was correct, but it treated all six as one kind of “spendable balance.” Two were the unexecuted portion of the first payment and had to be returned if G2 did not begin. The other four had no assigned use but did not therefore belong to V2.
A budget does not search a balance for the greatest amount that can be spent. It specifies how much of which resources a defined action may change, which uses remain protected, and how stopping restores state. Equal numbers with different identities and times support different actions.
This chapter continues to use fictional normalized units and does not explain real accounting, contracts, or industry rules. Receipts, refunds, and uses in the case come from the prior chapter's stage terms and serve only to test how action preserves margin.
First Make the General Ledger Reconcile
The first row records the flow relation only: opening twelve, plus three received, minus one actually spent by G1, equals current fourteen. “Current” means the snapshot after 16:20 Monday, not final settlement of V2.
This row prevents counting the first payment twice. If three units increase the balance while G1's one is also treated as fully preserved, the ledger is inflated. If the sample expense is deducted once from the first payment and again from the original four deployable units, it is understated.
The fungibility of money does not make attribution of use unnecessary. The case explicitly places G1's unit under the first payment, leaving two from that payment. The visible balance must still agree with the bank-like total of fourteen, and classifications cannot sum to more than it.
Balance Is a State; Budget Is an Authorization
Balance answers how much is visible at a time. Budget answers how much an action may use, under which conditions. Fourteen is the present state; two is the candidate G2 cost ceiling. The same word “remaining” cannot join them.
Even a high balance may contain refund, use, or timing obligations. Even an approved budget may not have been spent. Deducting a budget in advance can project a future state, but it must be marked estimated or committed rather than actual payment.
Gu Ning adds a state word to every field: received, spent, protected, conditionally restricted, unallocated, estimated use, and released. The extra nouns let a reader reconstruct the layer at which action stands.
Visible Balance Differs from Immediately Usable Amount
Fourteen units are visible in the account, but not all can fund a new purchase at 17:00 Monday. Eight have protected uses and two carry execution-or-refund conditions. Four are unallocated; even they require authorization for a new action.
Immediate availability also depends on payment time. An expense due before the final payment cannot use that future three-unit inflow. A refund due the same day cannot wait for a possible Wednesday receipt. One closing total may hide an intermediate shortage.
Gu Ning therefore does not write a permanent “six available” beside the ledger. She answers by use and time: G2 may currently apply for the two conditional units; another new action may discuss the four unallocated units; each carries different constraints.
Labels Must Not Duplicate a Unit
The two-unit first-payment balance is received, V2-related, refundable on stopping, and usable after G2 release. These are several attributes of the same resource, not four separate two-unit pools.
One primary state determines its place in the sum; other attributes remain conditions on the same row. Its primary state is “conditional balance: two.” It is included in fourteen and in the remainder of the first payment, and is not added again to the four unallocated units.
Likewise, one retained slot belongs both to the ten-slot total and to the minimum margin after G2 release. It cannot appear twice in schedule statistics. Nonexclusive classifications defeat accurate decimals through double counting.
The Protected Eight Are Inside the Fourteen
The eight units are not in an invisible separate box. They are part of the fourteen, with uses protected for existing payments, basic operations, and unexpected rework, and must remain available when needed.
One cannot simply spend six from fourteen and say the remaining eight exactly meet the line. The identity of the six matters. If two must be refunded on stopping, that refund still has to be paid. Intermediate state may also differ from the endpoint when spending precedes later receipts.
Nothing in this chapter changes the eight-unit amount. No existing task has completed and no protected purpose has been released. A future revision needs a source and time and cannot lower the line merely to make G2's budget more comfortable.
Why the First-Payment Balance Is Not Profit
Three units have arrived; one was used for G1 and two remain tied to G2 execution or an exit refund. They are neither imagined future income nor earned net gains available for any use.
If G2 is released, the two can fund formal work under the stage rules. If G2 stops before starting, they must be returned through the original method that day. The paths are mutually exclusive, so the current state is conditional.
Calling them profit may invite unrelated purchasing and later force a refund from the protected eight. Calling them entirely untouchable is also inaccurate, because the parties agreed they may fund G2 after release. “V2 conditionally restricted balance” is the correct state.
The Four Unallocated Units Are Not a Spending List
Of the opening twelve, eight were protected and four set the ceiling for discussable action. Because G1 was covered by the first payment, the original four remain unallocated. They can support a suitable future action but need not be spent this week.
“Deployable” describes an authority boundary, not an expenditure target. If managers evaluate by budget utilization, those four may acquire invented necessities merely to avoid appearing idle, turning margin into waste.
Gu Ning does not append them to G2 as quality insurance. G2 is estimated at two. If a third becomes necessary, the plan reopens cost and stage instead of drawing automatically from four visible units.
The Three-Unit Final Payment Is Not Yet on the Ledger
V2 proposes the other half after item-by-item receipt. Formal work and Wednesday receipt have not occurred, so the final payment is a conditional future inflow.
It may enter a scenario page to compare completed consequences, but not the current fourteen or Tuesday purchasing protection. Writing “the client will pay” as cash erases time from the total.
Even if the team considers payment highly reliable, it can only record the grounds and probability of that judgment separately. Preference or trust does not change receipt state. This chapter makes no numerical prediction for the final payment; it records the trigger and not-received identity.
A Use Still Stands Between Income and Expenditure
An inflow can bring later responsibility. The first payment enables sampling and conditional formal work while requiring treatment of unexecuted balance on exit. More income does not erase liabilities or commitments.
The case does not build formal financial statements, but it preserves cash direction and action use. Total inflow, executed correspondence, refundable balance, and future final payment remain separate so “received three” does not simultaneously mean profit, cash, and authority.
If V2 completes, contribution uses full inflows minus full added costs and checks timing. If it stops, settlement follows actual execution and refund. No final net figure exists yet.
Labor and Cash Cannot Offset Each Other
Monday began with ten half-day slots: six committed, four schedulable. After G1 uses one, three remain uncommitted. More money does not create a fourth remaining slot, and idle labor does not replace a unit of material.
G2 is estimated at two slots. If released, two of the three become committed and at least one remains outside V2. This passes the present capacity count but still requires exact times and review of shared resources.
Six units of possible revenue cannot compensate for having no Tuesday personnel, and one remaining slot cannot compensate for a two-unit refund. Each resource passes its constraint separately before meeting on the action page.
A Used Slot Is Not Remaining Capacity
G1's Monday-afternoon slot has ended and produced a sample record. It cannot reappear in the formal-stage budget because the sample serves G2, or disappear from “used” because the week contains later time.
The labor identity is ten total: six existing commitments, one G1 used, three uncommitted. The four categories sum to ten. G2's two estimated slots remain inside the three uncommitted; they are not a fifth class of capacity.
Adding the two planned slots to the three uncommitted would show five available. A budget page must state inclusion relations, especially when plans and actuals appear together.
Retaining One Slot Does Not Waste a Day
Gu Ning proposes that even after G2 release, at least one half-day slot remain uncommitted by V2. It protects against anomalies in the six existing jobs or necessary recovery without presuming which will occur.
Retention is not permanent locking. Gu Ning can release it when the risk window closes or existing work finishes on time. Before release, it cannot automatically become extra polishing time for V2.
This is a case constraint, not a rule that every project retain ten percent labor. Its quantity comes from the current ten slots, six commitments, and V2 stages. Another subject or period needs a new margin.
Margin Must Cover the Next Step in the Bad Scenario
One slot and four unallocated units do not guarantee recovery from every failure. They provide part of an actual path for identified disruptions to existing work, stage stopping, and rescheduling.
If a failure needs five units or three consecutive slots for recovery, the current margin is insufficient. Recovery demand and retained quantity must be compared in the same unit and time. The word “buffer” cannot pass the plan.
Shared exposure has not yet been checked, so this chapter does not claim the retained resources cover every G2 consequence. The ledger makes actual availability visible; the next chapter asks whether several paths need it at once.
Estimated Use Must Not Become a Sunk Cost Early
G2's two units and two slots appear in the plan but are unreleased and unused. Saying “the budget is already set aside” can make the team feel compelled to start, treating an estimate as an occurred input.
Only actual unrecoverable consumption enters sunk costs. An unsigned purchase, unscheduled labor, and cancellable plan remain present choices. Any preparation cost is recorded as actually incurred rather than replaced by the future total.
This lets Gu Ning reduce or cancel G2 if shared-exposure review finds a problem, without being bound by two figures in a plan. Greater detail in a plan does not make exit less reasonable.
Commitment and Reservation Must Also Remain Separate
“Estimated” means a plan may need a resource. “Reserved” means it refuses other uses for a period. “Committed” means the subject has assumed an execution relation once relevant conditions hold. Their opportunity consequences differ.
G2 presently has estimates only, without reservation or commitment. The jointly confirmed Wednesday receipt window does not lock two internal labor slots; stage confirmation explicitly requires a separate release for formal work.
A later reservation must state its start, end, and cancellation point. The station cannot say externally that work has not begun while internally refusing every other arrangement and then call waiting costless.
Conditions Trigger Budget Release
Gu Ning lists candidate financial release conditions for G2: the stage version remains valid; G1 transfers to the same material and procedure; the two conditional units remain on the ledger; shared-exposure review passes; and the eight-unit protection remains unchanged at start time.
Labor release also requires two specific slots still to be schedulable and at least one slot remaining outside V2 afterward. Passing cash conditions cannot sign for labor, nor the reverse.
Even after the conditions trigger, Gu Ning records release. Automated checks can prompt but a “sufficient balance” formula cannot place an order directly. Authorization stays connected to numerical judgment.
Budget Passing Has Several Levels
Quantity passing means the sum stays within the ceiling. Timing passing means the resource is actually reachable when needed. Use passing means the call does not break protection or refund relations. Authority passing means a responsible person has released it. One green mark cannot replace all four.
G2 appears to pass quantity: two conditional units and two slots within three. Receipt of the conditional balance supports cash timing. Use still needs exit and shared exposure; authority explicitly remains unsigned.
Separating levels prevents “finance says the money exists” from becoming “the project is approved.” Each assent answers only its relation, and the final action card combines them.
Check Minimum Balance Along the Path
Suppose a plan pays four in the morning and receives four at night, with equal opening and closing balances. If a protected obligation is due at noon, the unchanged endpoint does not prove feasibility. Resource lines apply at critical times, not merely endpoints.
V2 is simpler: the first payment arrived before G1; candidate G2 expenditure occurs only after release; final payment can occur only after receipt. Gu Ning records this order and forbids using the final payment to raise Tuesday's balance early.
If the actual payment order changes, the budget recalculates its minimum point. Equal total income and cost can still change process survival, continuing Chapter 3's distinction between final net amount and the cash path.
Write the Overrun Rule Before an Overrun
If G2 execution is expected to exceed two units or slots, Ye Cheng pauses before making another commitment and records actual use, remaining work, and reason. The four unallocated units do not automatically plug the gap, and retained labor does not default to V2.
Gu Ning may reduce scope, renegotiate time, form another stage, or stop. Every choice rechecks the eight-unit protection, refund relation, and existing tasks rather than approving “just a little more.”
If an overrun is discovered after occurrence, the actual loss still enters the ledger. A budget constrains authorization; it cannot remove a past expenditure from reality.
Exhausting a Budget Does Not Prove Stage Completion
Spending two units may leave the checklist incomplete; spending less may produce every required result. A budget is a resource boundary, not a completion indicator.
Using “there is budget left” to add unnecessary work makes the ceiling a target. Using “the budget is gone” to mark an unpassed item complete lets accounting answer for acceptance. Cost and result require separate adjudication.
G1 happens to use exactly one unit because the case stipulates it, not because matching budget and actual is ideal. Savings return to their proper state; overruns reopen. Neither decides quality.
Preserve the Source of Change Between Snapshots
Saturday's resource page showed twelve total, eight protected, four deployable. After receipt at 11:35 Monday it showed fifteen; after G1 expenditure, fourteen. All are correct at different times.
Keeping only fourteen loses the history of payment and sample. Placing fifteen and fourteen together as “current balance” creates contradiction. The margin ledger records the time, source, use, and responsible person for every change.
Labor works the same way. Four slots were schedulable Monday morning and three remain uncommitted after G1. Versioned snapshots let later environmental change return without rewriting a table to appear eternally fixed.
A Budget Revision Must Not Overwrite Old Authority
If material prices change Tuesday, G2's estimate may rise from two to three. A new budget may be proposed but cannot rewrite Monday's “two-unit ceiling” to three and conceal the executor's original authority.
Gu Ning preserves budget version, formation time, source of change, and applicable stage. The old version explains whether earlier action exceeded authority; the new version governs only after taking effect. A smooth result cannot expand old authority retrospectively.
A decrease also needs a version. If one unit proves sufficient, the unreleased difference returns to its former identity. It is neither project profit nor automatic authorization for added work. Revision changes future boundaries, not occurred flows.
Separate Scenario Budgets from the Actual Budget
Gu Ning writes two projections. If G2 is not released and the stages stop, the two-unit balance is returned and the visible balance moves from fourteen to twelve. G1's one-unit cost was covered by the executed portion of the first payment and remains occurred.
If G2 is released and spends its two-unit ceiling, fourteen falls to twelve, containing eight protected and four originally unallocated units. The final payment still waits for item-by-item Wednesday receipt. The projection does not say G2 will complete.
Both are conditional scenarios and cannot be averaged into the current fourteen. A budget can show future paths; the actual column changes only with real events.
Margin Is Not an Isolated Metric to Maximize
Preserving all four slots and four units maximizes immediate margin by performing no new action. G1 reduces margin in exchange for S-3 material; G2 would pursue a suitable commission. Margin serves continued action and is not the sole goal.
Conversely, assigning everything to the most promising present object leaves no capacity to adjust when feedback arrives. A reasonable quantity depends on goals, adverse scenarios, deadlines, and other paths.
Gu Ning therefore evaluates neither a budget by “most remaining” nor execution by “fully spent.” She checks what commitment obtains, what retention protects, and whether both truly coexist at the relevant time.
The Margin Ledger as a Domain Expression of Available Margin
RC names as available margin the space not yet locked and able to support reconvergence. At an operating scale, it appears through cash, labor, authority, and recovery times actually controlled by a subject. The margin ledger is a dimensional bridge from ontological openness to action conditions.
The protected eight, uncommitted slots, and conditional balance are not physical measurements of the ground of possibility. They are secondary constructions through which Chengwan preserves choice at its present scale of observation. Separate fields give “keeping choice present” an executable, feedback-ready, revisable interface.
The D17 Margin Ledger
At 17:00 Monday, Gu Ning saves the cash snapshot: opening twelve, first-payment inflow three, actual G1 expenditure one, current fourteen. Fourteen is mutually exclusively divided into eight protected units, four originally unallocated units, and two units of V2 conditionally restricted balance.
The three-unit final payment is an unreceived conditional inflow. G2's two-unit estimate can move from conditional balance to committed only after release and then to expenditure as actually used; on stopping it is returned. The four unallocated units do not automatically cover an overrun.
Labor snapshot: ten total, six existing commitments, one G1 used, and three currently uncommitted. G2 estimates two of those three; if released, at least one remains outside V2. Estimated, reserved, committed, and used remain separate.
Passing the Budget Check Does Not Mean G2 Passes
At the point estimate, the two conditional units cover G2 and two slots fit into three while leaving one. It passes this chapter's quantity and identity checks.
But the chapter has not answered whether the two slots rely on the same person, material entrance, or time, or whether failure would occupy the retained slot as well. Listing resources individually does not automatically detect common causes among paths.
G2 is therefore updated to “budget check passed; shared exposure pending” and remains unreleased. No purchase, formal production, or labor reservation occurs. Passing one checkpoint closes only one kind of question.
Handing Off to the Exposure Map at 17:20 Monday
At 17:20, the three complete the margin-ledger review. The client has sent no new message; V2 scope, Wednesday window, and stage rules remain; G1's result is unchanged; and G2 still stands before its start.
A budget is not fourteen minus eight equals six followed by a search for uses. It preserves where every unit came from, why and when it is usable or refundable, what has been consumed, and the state to which stopping can return. Labor likewise reconciles total, existing commitment, use, and noncommitment.
The next chapter places G2 and the six existing tasks on one exposure map. Paths with separate budgets may depend on the same person, material gate, equipment, or time window. When a common condition fails, they do not remain independent merely because their project names differ.