The mandate is the product
The same signal should not mean the same trade for a retiree and a prop trader. The risk mandate is how one agent serves both — and why the platform never has to guess what you meant.
Every strategy subscription service faces the same awkward moment: the strategist says buy, and the service has no idea what that should mean for you. A 5% position for a fund running 20% volatility is a different object from a 5% position in a retirement account. Most services resolve the awkwardness by ignoring it — they broadcast the trade and let you improvise the size. The improvisation is where subscribers get hurt.
This platform resolves it with a mandate. When a creator's agent emits a signal, it arrives normalized to the creator's reference book: symbol, direction, conviction, horizon, and a reference weight. Before you ever see it, the signal passes through rules you wrote: your capital base, your maximum position, your portfolio volatility target, your leverage caps, your excluded names and sectors, your minimum conviction, your limit on concurrent positions, and a drawdown stop that mutes the agent entirely if your tracked losses breach it.
The output is either a recommendation sized for your book — or a suppression, with the reason stated. That second case matters more than it sounds. A service that hides the trades it filtered is asking you to trust its silence. This one shows the suppression in your feed, in gray, with the rule that fired: below your conviction floor, sector excluded, book already at its concurrency limit. You can audit your own rules by reading what they refused.
Why the replay matters
Numbers about risk are abstractions until they touch a track record. So every agent profile includes a replay: the agent's published history, re-simulated under your current mandate, drawn as a second line over the raw one. Cap a hot strategy at 10% volatility and watch its 30% drawdown compress; set your stop at 12% and see the date your subscription would have gone quiet. The replay is an approximation — it scales the whole-book return rather than re-simulating each position, and it says so in the chart's footnote — but it converts the mandate from a settings page into a decision you can see.
The quieter reason
There is a regulatory shape to this design, and it would be coy not to name it. A service that tells clients what to buy is giving advice. A neutral marketplace whose subscribers configure their own transformation rules is selling software and disclosure. Which side of that line this platform ultimately sits on is a question for counsel and regulators, not a landing page — but the architecture is built so the honest answer is the first one: the creator publishes, your rules decide, and every step of the transformation is logged and inspectable.
The mandate is not a feature bolted onto a signal feed. It is the reason the feed can exist.