How the Quant recommends changes, and what it can never do
The Quant turns its nightly measurements into typed cards (blend weights, taking an algorithm off or giving one a weight, display order, the sleeve split, guidance drafts, posture, a single risk knob), each with the expected effect on risk-adjusted return and the exact change; you accept, edit or dismiss; anything that loosens risk asks for your code; on Auto the cards inside your mandate apply themselves and revert unless they hold; every applied card is graded later.
- Who it is for
- Owners & operators
- Reading time
- 9 min read
- Updated
- What it is
- Typed cards from the Quant: one change each, with the expected effect on risk-adjusted return and the exact before → after
- Where you see them
- Strategy › Recommendations (grouped by what they touch, with history and grades) and Inbox › Recommendations
- What Accept does
- Applies that change through the same editor you would use by hand, in one audited step, revertible for 7 days
- What asks for your code
- Anything that loosens risk (you type words that name it: MORE RISK, or the 's name), an enforced rule
- What can run by itself
- Nothing on Recommend. On Auto, the cards inside the mandate derived from your posture and one word of freedom — each with a notice, a grade and a one-click Revert — and they revert themselves after 7 days unless you keep them (Keep on the card acknowledges it; the grades stay for review)
- What it can never do
- Trade, pick a symbol or a size, make or lower a gate, write an , move your , or loosen a threshold — in any mode
The Quant measures; it does not trade. After the close (and whenever you press Run now on Desk › Quant) a deterministic engine replays the out of sample, tests every , asks which risk knobs stopped qualified entries, reads your closed trades for recurring patterns, and compares the book with the posture you declared. Each finding that clears its guard becomes one recommendation card. When nothing clears, the nightly note says so: a run of "no change" findings is a healthy sign at this data scale, not a broken desk.
What a card carries
Every card, whatever it touches, has the same parts:
- What: the kind and the target in plain words ("Blend weights · the blend", "Risk knob · Max resulting position as % of equity", "Guidance · a note on SMCI").
- Why: the engine's own rationale, every figure in it taken from the measurement; the Quant's short note rides beside it, labelled, never as the numbers' source.
- Expected effect: the change in risk-adjusted return (annualised Sharpe) with its 90% interval, the change in worst , and turnover or exposure when they move. Hover the chip for the basis: a replay of the return paths with and without the change (weights, taking an algorithm off, giving one a weight), a measurement on closed trades (gates, guidance), or an estimate at your desk's measured Sharpe (posture, risk knobs: scaling how much risk you take scales return and drawdown, not the ratio, and the card says so). A card whose basis is a replay among several candidates is also checked against picking the luckiest one; a card that fails that check never reads "high confidence".
- Confidence: low, medium or high, from the width of that interval and the length of the record behind it. Never from prose.
- Direction: tightens risk (one click), loosens risk (asks for your code and words that name the action: MORE RISK, or the name of the posture you are moving to), or neither.
- The exact change: before → after per key, red where it loosens, green where it tightens.
- Accept · Edit · Dismiss, then Revert for 7 days once applied; and, once decided, how it turned out at 5, 20 and 60 trading days.
The kinds
| Kind | What it changes | Who applies it, and how |
|---|---|---|
| Blend weights | one bounded step of the blend toward the walk-forward recommender's weighting (no algorithm moves more than 0.10, 0.25 in total, sum preserved), measured out of sample; equal weights are the starting point and a fitted weighting replaces them only when it beats them out of sample by more than its own margin of error | you, one click — or Auto, inside the weekly budget |
| Take an algorithm off the blend | a member whose rolling contribution is negative past the guard goes to weight 0; the PM still sees its vote | you, one click |
| Give an algorithm a weight | a benched algorithm whose trailing year beats the weighted median and whose record clears the guard against picking the luckiest of those tested gets a 0.05 starter weight | you, one click |
| the order the algorithms are listed in on their page, when one algorithm's standalone record clearly leads; it changes no score and no trade, and this kind is being retired | you, one click | |
| Allocation targets | a bounded nudge of the split between sleeves (core ETFs, satellite stocks, cash floor) inside your bands around the posture's split — more cash and less satellite in a risk-off tape, back toward the posture's split when it clears | you — through the Allocation editor's own path; raising invested exposure asks for your code and MORE RISK; or Auto, inside the mandate's band |
| Guidance | a draft note in fixed wording for a recurring loss pattern (a symbol that keeps losing, entries just before earnings, chasing gaps, going against the blend), or retiring a note whose blocked entries then rose | you — it lands on Strategy › Guidance like a note you wrote; an enforced draft asks for your code; retiring an enforced note loosens risk (code + MORE RISK) |
| Posture | one or down, from the tape and from your book's own volatility, drawdown and exposure against the posture you declared | you — through the posture editor's own path: every limit in one transaction, your code and the posture's name (for example MODERATE) if any of them loosens |
| Risk knob | one limit, one notch: looser where it kept stopping qualified entries (inside its bounds and never past the most permissive preset), tighter where the book never comes near it. The two halt thresholds are never loosened | you — through the same bounded, audited write Risk uses; a loosening asks for your code and MORE RISK |
Accept, Edit, Dismiss, Revert
Accept runs the owning editor's own code with you as the actor and the card as provenance, writes the audit rows in the same step, and stamps the card accepted. The direction that decides whether your code is needed is computed from the values the book holds now, not from what the card stored days ago, so a card can never be a way around a ceremony the editor would demand of you by hand, and nothing on a card can move a value outside its bounds.
Edit opens the card's values for the kinds where that makes sense (weights, display order, the wording / strength / lifetime of a guidance draft, the target posture, a knob's value). Your version is validated like the original and judged for direction like the original: turn a tightening into a loosening and it asks for your code. The card is stamped accepted with your edits and keeps both versions.
Dismiss changes nothing, records your optional note for the Quant's next run, and stops the same card from coming back while it would still be live. A run over the same evidence never duplicates an open card either: the same measurement produces the same card, and the open one simply stands.
Revert (7 days) puts back exactly what Accept captured, through the same editor. Undoing a tightening is a loosening, so that revert asks for your code too. A retired guidance note is re-added on Guidance, not reverted from the card.
Viewers and anyone looking at a book read-only see every card and never the buttons.
Auto, and the 7-day self-revert
Tuning· Strategy › Profile › Autonomy › Tuning (Off / Recommend / Auto), the second row of the card on Strategy › Profile, has three positions: Off, Recommend (the default: every card waits for you) and Auto (asks for your code and the word AUTO). On Auto you also pick one word of freedom (Tight, Balanced or Free hand) and the code derives the whole mandate from it and your posture: how many points a week the blend may shift, whether members may come and go, the posture range, how far limits and sleeves may move inside that range, whether soft guidance may be drafted. The card prints it as plain sentences; What the Quant may change on its own has the table. Cards inside the mandate apply themselves at the next session boundary, in either direction, including a step toward more risk when it is inside the range you armed, each with a notice, an entry in the audit log naming the card, and a one-click Revert. Cards outside it wait for you exactly as on Recommend, and say why in one line.
An automatic change then has to be : 7 days after it applied, it reverts itself unless you kept it (Keep on the card, one click, logged; the grades stay on the card for review but never decide the revert). The revert is its own audited change with a notice, never overwrites a value you changed since, happens only outside market hours, and waits while the book is halted. The desk also pauses itself (nothing more applies until you resume with your code) when the book draws down most of the way to its halt, when two automatic changes in a row miss, when its own run fails or the data is stale, or when trading is halted. Pause is always one click for you. What it may recommend· Desk › Quant › Scope (blend, gates, allocation, posture, guidance, risk knobs, parameters) is a set of checkboxes on Desk › Quant; everything but parameters is on by default because a card on its own changes nothing.
Grades and the scoreboard
Every accepted, edited or automatic card gets three grades, at 5, 20 and 60 trading days: the realized change in risk-adjusted return over that window against the interval the card promised: within the interval or not, and whether it moved the expected way. For blend changes the grade replays the blend with and without the change on the returns that arrived since; for posture, knobs and guidance it compares the book before and after (and says that is not a causal estimate). The line "Quant recommendations: n accepted, k within the expected interval" on Performance › Evidence and at the top of Strategy › Recommendations prints a rate only once ten cards have a 20-day grade; before that it says how many it has.
What the Quant can never do
- Place, size or cancel an order, or read news, briefs, chat or transcripts.
- Pick a symbol, set a position size, or write a : names and sizes are the portfolio manager's, inside the budgets the Quant's settings leave it.
- Apply anything itself: its process has no permission to write configuration. Accept and Auto both run in the console's API, under your book, recorded in the audit log with the card's id.
- Make or lower a gate, write or retire an enforced guidance rule, move your approval line, touch credentials or halts, in any mode. On Recommend, loosening a limit or stepping the posture up also waits for your code; on Auto it happens only inside the range you armed with your code.
- Loosen either halt threshold with a knob card; they only ever come in, or move with a posture step you allowed.
- Move a value outside the bounds the code defines, or past the most permissive posture preset.
- Show "high confidence" on a change whose interval is wide, whose record is short, or that looks like the luckiest of many tries.