Did my change save?

Every save or apply control in the console ends in one of three visible states. You never have to guess.

The three endings

• Saved, with a View in audit log link. The server accepted the change and wrote it to your book together with an audit line in the same step; the link opens that exact line on Activity › Config. Changes that loosen risk, raise autonomy, widen who can see the book or touch broker credentials also say code verified.
• Not saved, followed by the server's reason. Nothing changed. The dialog stays open with what you typed so you can fix it and press the button again. A red toast repeats it (for a posture: "Posture not changed, still Moderate").
• Nothing was sent, try again. The click never reached the server (a stalled tab, a lost connection at the wrong moment). Nothing changed; press the button again. This is the case that used to be silent.

When settings pull against each other

You make three choices: the posture· Strategy › Profile › Posture, the approval line· Strategy › Profile › Autonomy and your guidance. Limits, the core sleeve share, how often the desk looks and which models run follow from those unless you override one; an overridden value says so, with the posture's value beside it.

Some combinations contradict each other: an Aggressive posture whose own position cap is below the size it calls a starter, a core sleeve larger than the exposure cap, a guidance rule that forbids everything the sleeve would buy, an approval line above the per-order cap, a model choice that is quietly ignored. When that happens:

• Strategy shows a banner, "N settings pull against each other", one line per problem with Fix on … pointing at the one screen that resolves it. Nothing in the banner changed a setting; the desk keeps running on what is stored.
• A save that would create such a contradiction is refused: the dialog stays open and says Not saved: this would make settings pull against each other, with the reason. Change the value, fix it on the screen named, or press Apply anyway, which asks for your authenticator code and is written to the audit log as a forced change.
• The Settings check lists the same findings in its panel Do any settings pull against each other?, each with Fix on … pointing at the screen that resolves it.

The Settings check page

The Settings check page lists every setting on the book you are looking at (risk limits, posture· Strategy › Profile › Posture, the approval line, halts, the never-trade list, the focus list, guidance, cadence and role configuration, the algorithm line-up, scheduled reports, who manages which position, the broker connection, sharing). The settings are grouped (Risk, Strategy, Desk and so on), with a row of section links to jump between the groups.

A row at rest says three things: the setting, today's value, and one state in words.

• In use means every service that needs the setting has read the stored value.
• Not picked up yet by … names who has not read the change yet, for example the trading service or the desk. The trading service re-reads your limits, halts, never-trade list, holds, guidance rules and algorithm line-up about every five seconds and reports what it holds within a minute. The desk reads everything when a session starts. The scheduler reads cadence on its next planning pass.
• Not read yet means nothing has needed the setting so far. Saved means it is stored and no service reports on it.
• Changed outside the console marks a change made from the command line during an incident, where no authenticator code could be checked.

Open a row for the rest: who changed it last and how long ago ("Cameron K changed it 6 minutes ago."), whether the authenticator code was checked, the link See this change in the audit trail, where to change it, and who uses it with when each last read it. The engineering detail (where it is stored, what it derives from, which tests prove it) sits in a closed Technical details fold in the opened row.

Run the check in the panel Run a full check runs the read-back checks on the spot: every stored limit inside its bounds and matching its last audit entry, the declared posture matching the limits· Risk › Limits, flags in a shape their readers understand, every service on the stored version, and no risk-loosening change in the last 30 days that skipped the authenticator code. Each result is one sentence, and the ones that passed fold away behind "N checks passed". Open the page from the link Check that every setting was saved in the title block of Settings, from the Settings check panel on the Health tab of Admin (owner only, with the button Open the settings check; the owner can open the page for any book), or search for "settings check". The Settings check card that used to sit on Settings is gone, and these links replaced it.