The Decisions log
The Decisions log
Decisions is where the work ends up: the permanent ledger of what your team has committed. When you raise an order or record a decision on a task, it lands here as a timestamped entry that cannot be edited, only added to.
Open Decisions from the left rail.
What each entry records
Every entry captures both sides of the call:
- What you committed: the final quantity, value, or change you decided on.
- What was recommended: the engine’s original figure, kept alongside yours.
Holding both means anyone can see where a human call differed from the recommendation, and by how much. The log records the commercial judgement as well as the outcome.
Finding a decision
Decisions are shown as a timeline, grouped by period with a running count on each heading, newest first. Search by title, product, SKU, or supplier to narrow the list, open any entry for its full detail, or export the record. When nothing matches you’ll see “No decisions match”; a brand-new workspace shows “No decisions recorded yet” until the first decision is committed.
Why it matters
The Decisions log is the audit trail for commercial policy:
- Accountability: who committed what, and when.
- Learning: where recommendations were consistently adjusted, so the guardrails and the engine can be tuned.
- Continuity: a new team member can read the recent record to understand how the team decides.
You cannot change a logged decision. History is fixed; you add to it by raising orders and recording decisions on your tasks.
Recall: asking what was decided, and why
In a workspace with Decision recall turned on, the record can be read back without opening the log. Twelfth keeps the rationale, any reason for going against the recommendation, and the figures as they stood when each decision was committed, and several places read them:
- The assistant. Ask “What did we decide on Maison Aurele last Christmas, and why?” in the chat drawer, or in Teams, Slack or Google Chat. For a named season it reads your trading calendar for the dates first; if there is none, it asks which half-year you mean rather than guessing. The answer is a dated list: what was decided, who recorded it, their rationale quoted in their own words, the lines that went against the recommendation and why, any negotiation outcome, and a link to each entry.
- The supplier record. A Decisions tab beside Activity on each supplier or brand lists the same decisions over the last 12 months, newest first. The season picker switches to a named period from your trading calendar, or to the previous 12 months.
- Your own AI tools. Over MCP,
recall_decisionsis a read-only tool. A workspace key reads the whole business; a person connected with their own sign-in reads their remits, exactly as in the app.
What you can see matches the log: a buyer reads the decisions in their own remits, and an answer scoped that way says “in your remits”, so a short or empty answer never suggests nothing was decided elsewhere. Negotiation outcomes (agreed, or walked away and why) come from supplier negotiation projects you can open.
Recall reads what was decided and why. It does not read outcomes: Twelfth has not yet measured whether a past decision paid off, so no answer says it did, and every answer and the Decisions tab say so. Ask about current trading and you get current trading, labelled as such, not as the result of a decision.
Recall starts at your workspace’s first committed decision. Decisions made before Twelfth, in spreadsheets or elsewhere, are not imported.