Where indicator output actually lands in the workbooks.

The connection points

Three fields carry everything.

For all the sophistication on the chart, the indicator layer's structured output reduces to a small set of journal entries. ATR state — Normal or Trend — comes from the BE Assistant's regime read and is the most consequential, because it determines management doctrine and becomes a permanent conditional-analysis dimension. Branch, declared before entry, follows from that regime read plus the operator's structural judgment. And setup context — which strategy, what the convergence showed, what timeframes confirmed — enters the notes field, unstructured but auditable. Everything else the indicators display is decision support that never leaves the chart.

Downstream consumption

Those fields become slices, and slices become findings.

Once in the journal, the indicator-derived fields propagate into every analytical layer that slices by context. The EV lab's conditional-context family reads branch, session, timeframe, and ATR state to locate where expectancy actually lives. The MAE/MFE lab's branch integrity flag compares declared branch against observed behavior. The variant attribution layer reads branch to compute per-branch variant ratios. And the weekly scorecard's branch probabilities — the entire EV construction — depend on branch labels being exact. That's the indicator layer's real reach: not into deployment, but into the evidence structure that eventually grades the strategies the indicators serve.

The accuracy stake

A misread regime corrupts more than one trade.

Because these fields feed conditional analysis, errors in them don't stay local. An ATR state logged incorrectly puts the trade in the wrong conditional population, so the Normal-regime EV slice includes a trend-regime trade and both slices become slightly wrong — and the branch-integrity flag exists precisely to surface cases where declared context and observed behavior disagree. The journal-integrity doctrine's rule applies exactly: fix the source row, never the downstream formula, and use exact labels because a misspelled branch is invisible to every rollup that counts by name. The indicators' contribution to the analytical stack is only as good as the fidelity of these three or four entries.

• ATR state and branch are declared before entry and never retrofitted after the outcome.
• Setup notes should be specific enough to reconstruct the read months later — 'EW star, 4 TF, 15m pivot cluster' beats 'good setup.'
• The coefficient and stop distance also cross over, from the volatility layer, and feed their own audit loop.

What never crosses

The deployment chain reads none of it.

Worth stating negatively, because the feed map invites the assumption of a fuller integration: no indicator field enters the gate calculation, the throttle's tier resolution, the pool budget lookup, or the exposure math. Those consume drawdown state, closed-trade evidence, structural diagnostics, and open exposure — none of which any indicator produces. The feed is real and one-directional into the evidence layer, and the authority layer is downstream of evidence only through the slow, aggregated path of weekly and structural verdicts. A convergence signal will influence a deployment decision months later, through its effect on branch EV, or not at all.

The key idea

A narrow feed, faithfully recorded, is worth more than a broad one loosely kept.

The indicator layer could have been wired into more of the system — signal strength as a throttle input, convergence counts as a confidence multiplier — and every one of those connections would have created a path for chart conviction to reach capital. Instead it feeds three or four honest fields into the evidence record, where they do genuine analytical work and where their accuracy is auditable. Narrow, honest, and downstream: the same shape as everything else in the stack that turned out to be load-bearing.