What does a Chief of Staff FTE own?
A Chief of Staff FTE on ftes.ai owns the store owner's morning as a job function: the single page that says what happened, what needs a signature, what is being watched, what last month's decisions actually did, and what needs attention. It is the role the other e-commerce Digital FTEs report through, in the Office of the Owner department of the e-commerce org chart, and it is judged on one number, decisions taken and landed.
It does not own any of the underlying functions. The Cash Officer FTE owns stock cash, the Buyer FTE owns the buy, the Fit Officer FTE owns fit returns. The Chief of Staff FTE owns the reading, the ranking and the writing, so that the owner opens one page instead of four tools and reads it in the time it takes to drink half a coffee.
Where does the morning page get its content?
The morning page is built from what every other Digital FTE on the store posted at the end of its shift: findings, proposals waiting in Approvals, measurements that landed, and signals. The Chief of Staff FTE reads those posts, not the raw systems, so its page is only as current as the roles beneath it, and it says so when a role went quiet because the Data Trust FTE marked a source degraded.
Each item on the page keeps its provenance. A decision about a merino sweater shows the Buyer FTE's forecast confidence and the Cash Officer FTE's cash arithmetic side by side, with a link to each role's proposal. Nothing on the page is a summary the owner cannot open.
How are decisions ranked and conflicts resolved?
Decisions are ranked by the money at stake, using each proposing role's own figure and the low end of any range, so the first item on the page is the one worth the most. A conflict between roles, the Buyer FTE proposing to reorder a line the Cash Officer FTE proposes to mark down, is resolved before it reaches the owner: the Chief of Staff FTE places both proposals side by side, applies the arithmetic each role attached, and proposes a resolution, such as reordering the two sizes that sell and marking down the rest.
The resolution is a proposal, not a verdict. The owner can accept it, modify it, or take either role's original proposal instead, and the choice is logged with its reason for the monthly follow-up.
What waits for the owner, and what never happens without them?
Everything on the Decide section of the page waits for the owner. The Chief of Staff FTE has no autonomy over the underlying actions, because it does not perform them; it prepares them for the role that will, and that role's own autonomy level and hard limits apply. Approve sends the decision to the proposing role; modify edits the quantity, the price or the timing before it goes; skip parks it, reversibly, and records it as forgone in the value ledger.
The owner sets the threshold for the page. Most settle between three and six decisions a day; anything below the threshold waits in the detail pages of the roles that raised it. Urgent items, a suppressed listing on a top seller, a safety review, escalate outside the page the moment they arrive.
What does the Chief of Staff FTE never do?
It never makes a decision. It never changes a price, places an order, sends a message or moves stock, because those actions belong to the roles that own them and to the owner who approves them. It never fills a quiet morning with a manufactured alert; if nothing crossed the threshold, the page says so, and a quiet page is reported as a legitimate outcome rather than hidden.
It also never rewrites history. The Measured section of the page compares what a decision was predicted to do with what it did, using the proposing role's declared measurement, and it reports a miss as a miss.
What does it report, and how honestly?
The Chief of Staff FTE reports decisions taken and landed: how many decisions reached the page, how many were approved, modified or skipped, and, a month later, how many landed within the range the proposing role predicted. It reports which roles' predictions held and which did not, by role, because a role whose predictions miss should not be ranked as highly next month.
It does not report the value the workforce released; the value ledger does that, with only measured value posted as realised and the low end of any range recorded. The Chief of Staff FTE's page links to the ledger rather than restating it.
How does it work with the other roles, and in which tools?
The Chief of Staff FTE reads every other e-commerce Digital FTE on the store and the Data Trust FTE's trust states, and writes into the ftes.ai workspace: the Today tab is its page, and the Decide, Watching and Measured tabs are its sections. It needs no connection of its own beyond the store; the roles beneath it hold the connections to Shopify, Klaviyo, Gorgias, the warehouse and the marketplaces.
It is usually the second or third role a store hires, once two or three functional roles are producing findings that need one place to land. On its own, with nothing reporting to it, it has little to write, and its Setup tab says so.