What it is
Every Monday the verdicts engine scores each declared number of every signed commitment over the retail week that closed, Sunday to Saturday on the 4-5-4 calendar, and writes one verdict per number per week. A verdict says what was measured, at what grain over what population, against what was declared, what the gap is worth, where in the window the week sat, and one sentence a person reads. It is the product's memory of a defended week, so a clean week is a reading and not a blank.
How Tightly decides it
The run is dispatched every night and scores on Monday; from Tuesday to Saturday each night fills in only what Monday's pass did not write for the same closed week, and Sunday nights score nothing. A week already written is never rewritten, and a business whose plan is not active is not scored. Only signed commitments are scored: a closed one is a promise nobody is keeping any more. Before the window opens, availability, pace and margin read not applicable yet with the open date named, never a green, while the envelope ladder and the agreed book's coverage still run, because a purchase order placed before the window and delivering inside it already consumes the envelope.
The engine never re-forecasts, never suggests a replacement glidepath, never adjusts a declaration and never touches an order; its only write is the verdict. The run length of consecutive weeks is carried forward from the prior row and never re-measured. A population that moves sharply week on week records not measured with both figures, since on a re-anchored book a change in the number is a change in the book. What reaches a person is budgeted: at most one urgent and three for review per commitment, and five rows on your Monday list across every commitment, ranked by money; the rest is counted and recorded as memory. Rows reach a list only from a commitment on the Proposing rung. A breach whose money comes to less than a thousand dollars is recorded as watch rather than listed.
The words on the face
| Verdict | What it means |
|---|---|
| on track | Measured and inside its declaration |
| watch | A real deviation held below the worklist, or most of the band spent |
| needs review | Outside the declared band this week; a person should look |
| urgent | Three weeks running outside the band, or a breach that is urgent at once, such as an envelope over its limit; a person should act |
| not measured | The measurement could not be taken or trusted; never a green |
| not applicable yet | The window has not opened; the date is named |
The engine's own state sentences, as the platform serves them:
No weekly verdict has run yet.
Scoring last week now.
Last week was scored; some commitments could not be read.
Monday's weekly run did not finish; it retries tonight.
Nothing is declared, so nothing is scored.
The weekly verdicts run on an active plan; this is paused.
Every verdict carries its as-of, the week's end, and the last scored week beside the last complete week, so a stale week is a date and not a silence. On This week the season to date is compared with the same complete weeks last year and the labels say so; the declared pace is the verdict's comparator.
What you can do about it
Nothing here is pressed; a verdict is read. In the room, the next action opens the page that answers a breached or watched number: the buying budget, replenishment or supply, trading or the buy, or pricing. Hindsight reads, once a season closes, whether each declared number was kept or missed. Ask Tightly, opened in the room, answers with that commitment in view.
Glossary line
A weekly verdict is the verdicts engine's Monday reading of one declared number over the retail week that closed, written once and never recomputed, with one sentence a person reads.