Integration · The Flow
From on-chart read to system evidence.
Write moments
3
Direction of flow
One way
Destination
CP3 Journal
Reads that skip capture
0
Layer 01 — Three write moments
Bias, then structure, then trigger.
The tools fire in sequence because they answer sequential questions. First the ATR BE Assistant, before any setup: what regime is this, and therefore which branch family and BE doctrine apply. Then EW Convergence, while the zone approaches: does multi-timeframe structure agree, and at what conviction grade. Last the continuation stack, at the trigger: do the engines score this moment as an A-grade regime. Each answer is written down at the moment it is read — because a read recalled at capture time is a read edited by the outcome.
Layer 02 — The capture contract
Five field groups must land, every trade.
The flow only works if the writes are complete. The contract:
- ATR State and branch family — the regime read that selected the doctrine.
- Convergence grade — MinN/★ status and the timeframes behind it.
- Continuation score — the 0–6 number and which engines passed.
- Coefficient context — zone, ratio, and the stop distance actually used, from the volatility layer.
- Management flags — partial, BE move, trail activation, against the branch's checkpoints.
Layer 03 — The reviewers
Saturday reads the fields the week wrote.
Captured reads become answerable questions in review. The Journal grades adherence: did management match the logged branch and doctrine. The MAE/MFE Lab grades the envelope: did stop distance and trail width convert excursion into capture, or leak it. The SDE grades structure: are indicator-guided decisions improving trend-branch EV across weeks, or damaging it. None of those questions can be asked of a trade whose reads were never written down — which is the whole argument for the capture contract.
Layer 04 — One-way valve
Indicators feed evidence downstream. Nothing flows back up.
The on-chart layer writes into clearance and the journal; no MARS state writes back into the indicators. The one-way valve is deliberate — an indicator that knew the account was in drawdown would tempt its owner to tune it, and a tuned indicator stops being evidence. The chart layer stays innocent of the account on purpose.
Reference
Who writes what, and when
| Tool | When it writes | What it writes |
|---|---|---|
| ATR BE Assistant | Pre-setup | Regime state · branch family · applicable BE doctrine |
| EW Convergence | Zone approach | Convergence grade · ★ events · agreeing timeframes |
| Trend Continuation | At the trigger | 0–6 score · engine pass/fail · active preset |
| VIP / Distance Matrix | At sizing | Coefficient · volatility zone · ATR ratio · stop distance |
| All of the above | Into capture | Journal fields the Saturday review will grade |
The governing idea
Go deeper
Operator briefs on this territory.
Deep dive — 01
The feed is a schedule, not an event — and one field is written before the trade exists.
One field is committed before the trade exists. That is what makes it evidence rather than commentary.
Read the full brief →
Deep dive — 02
Each tool enforces the session gate separately, and nothing checks that they agree.
The same window, configured three times, with no mechanism that notices when the copies drift apart.
Read the full brief →
Deep dive — 03
Where indicator output actually lands in the workbooks.
Chart evidence becomes journal fields: ATR state, branch, setup context. That's the entire connection.
Read the full brief →
Every module ships in the complete MARS package.
One price. Eleven workbooks, three TradingView indicators, and the full manual library — $497.