What is on the Morning Brief?
Five things, in order. What needs attention: exceptions that crossed a threshold overnight, such as a stuck fulfilment backlog or a source that failed. Today's decisions: the proposals worth signing, each with its evidence and its dollar value. What happened overnight: the sync, the orders, the returns, the tickets. What the platform is watching: figures moving toward a threshold. And integration health.
The page is a reading, not a dashboard. It says what the numbers mean today and what to do, and links every claim to the surface it came from. An owner who wants the numbers themselves opens the Dashboard; an owner who wants to act reads the brief and signs.
Where does a decision card come from?
A decision card is built from a computed finding. The inventory analyst finds a line whose days of cover have dropped below its lead time and proposes a reorder; the discount monitor finds a code that gave margin to customers who were already buying and proposes pausing it; the money finder assembles a win-back list of customers past their usual return window. Each is a query result first and a card second.
The AI writes the card's narrative from the figures and drafts the message a manager would send. The number on the card is the backend's number, and the card links to the page where it can be recomputed. This is law one and law two of the commerce engine on one screen.
Why does every decision card have its own Review & Send?
Approving a card opens the Review & Send screen for that action: the email that will go to the store manager, the list that will be pushed to the email tool, the article that will publish. The screen shows exactly what leaves and to whom. Modify edits it before it goes; skip parks it and records it as forgone.
Nothing on the brief acts on its own. Unattended sending is an explicit switch per class of action, off by default, and where an owner turns it on, the sends still appear on the brief the next morning as things that happened, with their Results verdict once measured.
Why ranking by money changes what an owner reads first
Wherever a list in the engine could be sorted by count, it is sorted by money instead. On the brief that means the first decision is the one with the largest amount at stake, computed from the finding's own arithmetic, so an owner with five minutes reads the item that matters most. A pile of small alerts never buries one large one.
The ranking is honest about ranges. Where a finding carries a range, the low end is used for ordering, so a speculative large number does not outrank a certain smaller one. The full range is still shown on the card for the owner to weigh.
What does the Chief of Staff FTE add on ftes.ai?
On ftes.ai the Morning Brief is the page the Chief of Staff FTE owns. It reads what every other e-commerce Digital FTE produced overnight, ranks the findings by money, resolves conflicts between roles with both sides' arithmetic, and writes the page. The engine supplies the computed findings; the role supplies the reading and the ranking.
The owner sets a threshold for how many decisions reach the page, and a quiet morning is reported as a legitimate outcome rather than filled with noise. Items below the threshold wait in the detail pages of the roles that raised them.
How to get your first brief
Connect the store read-only. The history backfills, the sync starts, and the first brief is written from the store's own figures. In the first days it will carry coverage notes where costs are missing, and the fastest way to make it more complete is to load costs and record shipments so the landed-cost engine can date them.
From there, hire the roles whose findings you want on the page first. A store that hires the Cash Officer FTE and the Buyer FTE will see stock cash and reorder decisions on the brief within the first week; the Chief of Staff FTE is usually the second or third hire, once there is enough to rank.