The desk reads before it trades and remembers dated ideas

What changed for people using Bellwether

• Session playbooks switch on. On each intraday check the portfolio manager reads the account, positions, quotes and live signals before it proposes anything, and follows a written procedure when a held name is halted.
• The desk remembers dated ideas. Ideas with a date count down in the manager's inputs, earlier notes on a name come back when its catalyst nears, and if-then watches are graded when they resolve.
• Mandate changes reach the next session. After you change posture, autonomy, allocation or guidance, the manager's next session opens with what changed and acknowledges it before trading.
• One signal number everywhere. The blend the manager is shown, the one its tools return and the one the console draws are the same read, and a manager that quotes it correctly is never held for it.

What you may notice

• Intraday session transcripts start with more reads and take about five seconds longer; what the manager buys on a normal day does not change.
• A posture change that tightens the book lists the dollars to trim, and new buys the tighter posture forbids are refused until the book is inside its band.
• When the manager flags a data problem it cannot resolve, you get an alert the same session instead of a line buried in its notes.
• The quant desk withholds a weight increase for an algorithm whose last sixty sessions lost money, and says why.

Switched on in this release

• Session playbooks for the portfolio manager and the quant desk: three procedures, each proven on live sessions with and without it before this release.
• The desk's long-horizon idea memory: countdowns, related notes and graded if-then watches. The idea track-record summary stays off until twenty ideas have been graded.
• The mandate-change notice at the top of the manager's next session.

Known gaps / coming next

• Waking the manager within minutes of a mandate change or a risk-review challenge stays off until live tests show it beats waiting.
• A drawdown-day procedure for the manager is proven and follows in a later release.
• The session page does not yet show which playbook loaded; the record is kept and reachable through the API.