Five traders who gain most, and they gain different things.

Why the profiles differ

The same architecture solves five different bottlenecks.

The modules do not change between operators; the binding constraint does. A trader losing edge to sizing is buying something quite different from one who cannot tell which of four branches is carrying the account, even though both receive the identical eleven workbooks. This matters commercially and operationally: it determines which module the operator should live in first, which output will feel revelatory, and which parts will initially seem like overhead. A system introduced in the wrong order for the operator's actual bottleneck feels heavy long before it feels useful.

The first two

One has an edge and leaks it; the other cannot see what they have.

The profitable but inconsistent trader holds a genuine edge that sizing, revenge trading, or concentration repeatedly damages — their results are real and their variance is self-inflicted. What they gain is the governance layer: deployment decided by capital state rather than by mood. The analytical trader's problem is the opposite. Their behaviour is fine and their instruments are too shallow — win rate and net P&L cannot answer questions about risk-adjusted efficiency, structural drift, or capture. They gain measurement, and they typically feel the value fastest, because the answers were the thing they were already looking for.

The compounder

The profile the system was actually shaped around.

The aggressive compounder wants growth at a rate that creates a direct conflict between speed and survival, and this is the operator the architecture was built for. Gates, tiers, throttle, cycle pools, exposure adjustment and the terminal lock exist because compounding at pace is a capital-engineering problem rather than a trading one — the arithmetic of recovery makes drawdown depth the binding constraint on growth, and no amount of edge quality substitutes. What they gain is survivability that was engineered rather than hoped for, and the honest version of that gain includes being told, by their own simulation, when their intended pace is not supportable.

The multi-branch operator

Four strategies inside one account, each needing its own verdict.

An operator running several branches faces a specific blindness: the account total averages them, so a strong branch subsidises a failing one indefinitely without either being visible. Per-branch expectancy, attribution, and role verification are what separate them — and the crucial output is not which branch earns most but whether each is performing the role assigned to it. A stability branch producing exciting returns is as much a finding as an accelerator producing none, because the blend's behaviour was designed around each branch doing its own job rather than around the total coming out well.

The developing professional

The functions of a firm, embedded in architecture instead of people.

The last profile is trading toward professional practice and lacks the thing that actually distinguishes a desk from an individual — not capital or information, but functional separation. A firm has a risk committee that is not the trader, a compliance function that audits without being audited, a performance-analysis team, an allocator, and a research sandbox with a promotion process. MARS supplies each of those as machinery rather than as headcount. What this operator gains is the structure; what they must supply is the discipline to treat the machinery's verdicts with the authority a colleague's would carry.

• Identify the binding constraint first — it determines which module to live in early.
• The compounder is the profile the risk architecture was specifically designed around.
• Per-branch value is role verification, not a ranking by return.

The key idea

Fit is a question about your bottleneck, not about your sophistication.

The five profiles are not a skill ladder and nobody is meant to graduate through them. They are five different answers to the question of what is currently costing the most, and the system's value in the first months is almost entirely determined by whether the operator identified theirs correctly. Someone who buys a measurement framework when their real problem was sizing will find the analytics interesting and their results unchanged — and the reverse mistake produces someone drowning in governance for a problem they did not have.