Skip to content
← Back to Workflow Overview

Operator brief · 57

The paper bridge: why capture happens twice before it counts once.

The key idea

The gap being bridged

Weekly entry is deliberate — and it creates a memory hazard.

CP3 entry happens once a week by design: batching the transfer keeps the workbook session focused and makes the Saturday close a real event rather than a rolling smear. But the design creates a hazard — by Saturday, a Tuesday trade is four days old, and unrecorded details don't survive four days intact. Which hit flags fired, whether breakeven triggered, what the fees actually were, what the management issue was: memory reconstructs these things confidently and wrongly, and always with a drift toward the flattering version. The capture document exists because the entry schedule is worth keeping and memory is not an acceptable storage medium for evidence.

The three records

Each record has a different job, and none replaces another.

The workflow maintains three parallel records on purpose. The paper capture sheet is the contemporaneous account — filled immediately after execution where possible, completed as outcomes finalize, one sheet per trade, including the context no platform logs: why taken, what was violated, what the emotional state was. TradeZella is the black-box referee — the digital record of what mechanically happened, with exact prices, durations, MAE/MFE, and fees. And the CP3 Journal is the system of record — the single source every downstream calculation trusts. Saturday's job is the reconciliation: each paper sheet transferred into the journal and verified against the digital record, with the compliance transfer marks confirming entered, verified, and included.

FigureThree records, three jobs — and the Saturday reconciliation
Paper capturein the moment· One sheet per trade· Filled at execution + close· Context, adherence, emotion· The honesty recordTradeZellathe referee· Exact fills and durations· MAE / MFE / fees· Screenshots preserved· The mechanical recordCP3 Journalsystem of record· Entered Saturday only· Verified against both· Compliance marks closed· The record that counts

The paper sheet preserves context and honesty in the moment; the digital record preserves mechanical fact; the journal becomes truth only after the first two agree.

What reconciliation catches

The disagreements are the product.

The bridge's value shows up precisely where the records disagree. Paper says the trade followed plan; the chart screenshot says the entry jumped the trigger. Memory says fees were trivial; TradeZella says the swap on the overnight hold was not. The capture sheet says +1R clean; the digital record shows the 1R flag hit but breakeven never armed, which is a different branch behavior with different EV implications. Each mismatch caught on Saturday is an error that never enters the journal — and journal integrity is the whole game, because a wrong row doesn't stay one wrong row. It becomes a wrong hit rate, a wrong branch EV, and eventually a wrong deployment decision that traced back to a Tuesday nobody remembers.

  • Never fix a downstream output by editing a formula — verify the journal row first. Most anomalies are source-row errors.
  • Branch labels must be exact: a misspelled branch is invisible to every rollup that counts by name.
  • Profitable violations get recorded as violations. The system needs clean-evidence flags more than it needs a better-looking adherence rate.

The honesty function

Paper is where the operator tells the truth to a future reviewer.

There's a subtler reason the capture is contemporaneous and physical: the sheet is filled before the outcome has finished editing the story. A note written at execution — 'entered before NY confirmation, session filter violated' — is a fact. The same event recalled on Saturday, after the trade happened to win, becomes 'read the momentum early.' The paper bridge captures the version of events the operator believed when it counted, which is the only version diagnostics can use. In a system whose entire premise is that evidence governs deployment, the capture document is where evidence is born — and the discipline of filling it is the cheapest data-quality investment in the whole stack.

The key idea

Redundancy at capture is efficiency everywhere else.

Every hour spent on paper sheets and Saturday reconciliation is repaid by every downstream module running on inputs that don't need to be doubted. The alternative — trusting memory, backfilling gaps, letting the journal drift from the broker record — doesn't save the work; it relocates it into diagnostic dead-ends and deployment decisions built on quiet fiction. Three records, one reconciliation, one truth. The bridge is short, and everything crosses it.

Connected inside MARS

Every brief documents the same shipped system.

The complete MARS package — eleven workbooks, three TradingView indicators, the full manual library — $497.