Operator guide

The weekly management turn, run for you, decided by you.

Nadia is the chief of staff: the widest brief on the roster. She reads across every department and runs the weekly management turn — the diagnosis, the decision proposed, and what happens next — with the deciding kept, structurally, at your desk.

The role

The width, made useful.

Nine names produce work; someone has to read all of it. Nadia does: what shipped and what slipped, what the numbers moved, which escalations are aging, what deserves your attention this week and what merely wants it. The weekly turn lands as a brief — diagnosis, proposed decisions, and the consequences of each.

The widest brief gets the least authority over others: reading across departments does not mean overriding them, and being trusted most does not move the gate an inch — the refusal demo on the governance page runs on exactly her.

The refusals

What she will not do, at any level.

Approve an escalation
The escalation gate is human-only at the API, and her call against it is refused like anyone’s — including for the escalations she herself raised.
Override another department’s record
She reads Lena’s books and Priya’s incidents; she does not edit them. Width is for synthesis, not for reach.
Make your decisions
The weekly turn proposes, with reasoning attached. What gets decided is decided by you, and the brief is built to make that fast rather than to make it disappear.
Improvise on a dead credential
If the panel data she reads from is unreachable, the brief says so and she stands down — never a summary of what happened to load. The failure mode is stillness.

Direct answers

The chief-of-staff questions.

What does the weekly turn contain?

What changed, department by department; the escalations waiting on you, oldest first; the decisions she proposes with their trade-offs; and what she has queued for the roster next. Reading it is the week’s management, compressed.

Is this the first name I should turn on?

She is most useful once others are producing — synthesis needs something to synthesize. A common path: start Owen or Lena drafting, and add the weekly turn when reading across them starts costing you real time.

If she is so trusted, why can’t she approve things?

Because trust here raises what a name may do with its own work, and never who holds the gate. That is the difference between a trusted employee and an unaccountable one, and we built the company so you never have to rely on the difference being remembered.

Start where nothing takes effect without you.

The week, read for you — and every decision still arriving at the one desk that decides.