Six required fields: the no-gap contract between console and throttle.

The framing

What must match is the contract, not the values.

The workflow manual states the test with unusual clarity: live test values do not need to match during testing — what must match is the data-transfer contract. That is a structural claim rather than a numerical one. The rail is correct when every required input has an identified source, every required output has an identified destination, and no critical field is left without a home. Whether today's gate happens to be Growth or Buffer is irrelevant to whether the rail is wired properly, and conflating the two is how operators end up debugging a number when the problem is a missing connection.

The packet

Six fields, and what each one is for.

The required inbound transfer carries the capital-state router and the tactical evidence around it. Final Gate Used selects the active gate row and pool envelope. Daily All-Blended EV Status supplies realized-evidence status as Green, Yellow, Red, or Insufficient Sample. Cycle P&L Direction classifies the closed cycle across its six states from Strong Positive through Severe Negative to Pending/Open Exposure. Open Carryover Trades counts unresolved positions crossing into the next decision. Active Open Risk % is named the key exposure burden and subtracts directly from the authorized cycle pool. Each has a specific destination cell in the 7-Tier Decision Engine, and each has its own update frequency.

The direction of travel

The console prepares; the throttle decides.

The roles table draws the authority line precisely. The Cycle Command Console is an evidence processor and exposure bridge — it prepares inputs and does not set final risk authority. The Throttle Control Panel's 7-Tier Decision Engine is the primary live deployment authority, producing the final tier, pool, per-trade risk, smart throughput, and directive. The console's Throttle_Feed tab exists solely as the transfer sheet. Neither workbook silently replaces the other, and the console having computed something does not make it a decision.

The return leg

The rail runs in both directions, and the order is specified.

The workflow is coherent in one order: Cycle Command Console, then Throttle Control Panel, then back to the Cycle Command Console, then the Cycle Decision Log. The return leg matters — the throttle's Smart Exposure Cockpit produces an operator-facing outbound packet whose values are copied or linked back into the console, which is what allows the next cycle's evidence processing to account for the authority just granted. A rail operated one-way leaves the console reasoning about capacity it no longer has.

The archive ruling

The Cycle Decision Log is history, not a decision engine.

The manual is explicit that the Cycle Decision Log is the archive and audit trail and is not the first-stage live handoff engine — a clarification added specifically to prevent its being used as a competing decision surface. The temptation is understandable, because the log contains everything: weekly structural backdrop, daily and cycle conditions, exposure state, final tier, override mode, and directive. It is the most complete single view of a cycle decision in the system. It is also a record of a decision already made, and reading a record is not the same as producing one.

• Log records after the decision; it never sources it.
• Its completeness is what makes it tempting and what makes the ruling necessary.
• Override mode is recorded here, which is what prices the exception.

Why the rail exists at all

It was engineered around a weekly CP3 cadence.

The rail's origin explains its shape. CP3 is updated once a week, but concurrent trades happen throughout it — so the operator needs to know, mid-week, how much risk to deploy, at what tier, in which gate, and how to handle open exposure still running from yesterday. The Throttle Control Panel was built to calculate risk allocation by tier and gate; the Cycle Command Console was built to feed it the cycle's concluded P&L, daily EV, and open-trade state. The two exist because the weekly evidence cadence and the daily deployment need run at different speeds, and something had to bridge them without letting the faster one rewrite the slower one's authority.