One red week should never force a trader to choose between preserving trading capital and paying rent. If losing capital threatens a required expense, the position was too large, the account was underfunded for its purpose, or both.
At 10:42 p.m., the resignation email was still sitting in Drafts. Quitting the day job had looked reasonable after several green weeks. Then one red week exposed the calculation underneath: the trading account and next month’s rent were drawing from the same limited reserve.
In April 1970, Apollo 13 faced a far more serious version of the same structural problem. After an oxygen tank exploded on the way to the Moon, astronauts Jim Lovell, Jack Swigert, and Fred Haise had to abandon the planned landing and preserve enough power, water, and breathable air to return home.
The mission had changed. Every remaining resource now had a different job.
When one pool of money has two jobs
Apollo 13’s command module was designed to support the crew during the mission. After the explosion, NASA shut most of it down to preserve its batteries for reentry. The lunar module became a lifeboat, even though it had been built for a different purpose and a shorter period of use.
Then carbon dioxide began building inside the spacecraft. The command module had square lithium hydroxide canisters. The lunar module used round openings. Engineers in Houston had to devise an adapter using materials available aboard the spacecraft.
The uncertainty was real. NASA did not yet know whether every improvised procedure would work or whether the remaining resources would last. Jim Lovell and Jeffrey Kluger document the mission in Lost Moon, later published as Apollo 13.
A part-time trader’s stakes are smaller, but the mechanism is recognizable. Money assigned to rent cannot safely serve as trading risk at the same time. When one pool has two jobs, a routine drawdown can become a personal emergency.
That pressure changes decisions. A trader who needs Friday’s position to cover Monday’s payment may widen a stop, add to a loss, or approve a weak setup. The market did not create the conflict. The account structure did.
Calculate the loss before approving the trade
Suppose an account holds $12,000. The trader plans to risk 1% per position, or $120. Four full losses would remove $480 before fees and slippage.
Those figures are illustrations, not a recommended position size. The useful question is concrete: if the planned loss occurs several times in a row, which obligations become harder to meet?
Write down the answer before placing an order:
- How much money can this position lose at the planned stop?
- What could slippage add if the exit fills at a worse price?
- What would five consecutive losses do to the account?
- Does any part of this capital have another job within the next several months?
- At what drawdown level must position size fall or trading pause?
This is trading capacity, the amount of risk an account can absorb while the trader continues following the plan. It usually shrinks during a drawdown. The arithmetic behind that change is covered in What Happens to Your Trading Capacity During a Drawdown?.
Small differences at entry also matter. A worse fill can turn a fixed dollar-risk plan into a larger exposure unless share or coin quantity changes. The 80 Cents That Turned $25 of Planned Risk Into $65 shows how quickly that gap can open.
An approval gate protects the right to say no
An approval-gated trading assistant can calculate and queue a signal, but the trader still approves or rejects it before execution. That pause matters most when financial pressure is high.
The approval should inspect the assumptions behind the order: entry, stop, quantity, total planned loss, current exposure, and the observation that would invalidate the setup. It should also include one question no chart can answer: is this risk capital still available for risk?
AI can help make the proposed trade visible. It cannot decide whether the account balance is also carrying rent, debt payments, tuition, or an emergency reserve. That boundary belongs to the human.
This is one reason unsupervised automation can fail in practice. A system may follow its trading rules precisely while ignoring a change in the trader’s financial capacity. Mechanical consistency cannot repair a capital boundary that was never defined.
Preserve the resource that keeps the plan alive
Apollo 13 returned safely because the mission stopped pursuing its original objective. NASA preserved the resources required for survival and reentry, then rejected any use that threatened them.
The practical trading equivalent is less dramatic: remove required living expenses from risk capital, define a drawdown response before the next order, and reduce or pause trading when the account crosses that line.
For the trader staring at the draft email at 10:42 p.m., postponing resignation was not a failure of conviction. It preserved income, reduced pressure on the trading account, and protected the ability to reject the next weak signal.
Leave the email in Drafts. Open the trading journal instead. Record the week’s realized loss, the remaining risk capital, and the exact account level that triggers smaller positions or a full stop.
Educational content, not financial advice.
Comments
No comments yet.