Skip to main content
A senior chief of staff doesn’t forget the decisions you’ve made. If you said in May “we’re not hiring until Q3”, you don’t want June’s brief recommending the hire again unless something changed. Decisions is the surface Forepost uses to remember.

​
Two ways a decision gets recorded

​
1. Dismiss-with-reason

When you dismiss any action in the Daily Brief, you can optionally add a reason. Click Dismiss, type one line (“we’re deferring all hires until Q3”), click Dismiss with reason. The reason is captured on the action AND seeded as a decision row so future briefs see it. A vanilla dismissal — without a reason — doesn’t create a decision. It’s just a “not now” with no rationale to remember.

​
2. Manual decisions

Click Decisions in the sidebar (under Memory). The page lists every active decision with the date you decided and an optional revisit date. The New decision card at the top accepts free text plus an optional revisit date — click Add decision and it joins the list. The API is also available directly: 
POST   /decisions                # create — body { text, revisitAt? }
GET    /decisions                # list (active by default; ?includeArchived=1 for full history)
PATCH  /decisions/:id            # update text / revisitAt / archived
DELETE /decisions/:id            # permanently delete

​
How decisions feed the brief

Each Daily Brief gets an ACTIVE DECISIONS block listing the most recent 12 active (non-archived) decisions: 
ACTIVE DECISIONS (memory the leader has set):
• Decided not to: "Hire one more agent". Reason: deferring all hires until Q3 (decided 14d ago)
• Slack auto-replies turned off for billing tier — we lose context (decided 4d ago)
• Pushing AI deflection to 70% before the next hire conversation (decided 21d ago · DUE FOR REVISIT)
The brief is explicitly told to:
  • Respect prior decisions; don’t re-recommend something the leader has already said no to.
  • Make exceptions when the underlying numbers have moved meaningfully since the decision was made — and say so in plain prose (“Your decision to defer the hire was at 12 weeks of runway; you’re now at 6”).
  • Surface decisions whose revisitAt date has passed: name them, ask whether conditions have changed. Never argue with a decision.

​
Revisit dates

Each decision can carry a revisitAt timestamp. When that date passes, the brief tags the decision DUE FOR REVISIT and the model is told to bring it up. Use this for “we’re deferring until Q3” — set revisit_at to early Q3, and the brief surfaces it on its own. Without a revisit date, decisions stay active indefinitely until you archive them.

​
Archiving

Active decisions hang around in the brief’s context block. When a decision is no longer relevant, click Archive on the row — it disappears from the active list and stops feeding the brief prompt, but stays in the database so you can see what was decided historically. Toggle Show archived in the page header to view (and Restore or permanently Delete) archived decisions. The API equivalent: 
PATCH /decisions/:id  { "archived": true }

​
What decisions aren’t

  • Not goals. Goals are targets — “get CSAT to 90%.” Decisions are non-goals — “we’re not doing X right now.” The brief already handles targets via the Watchlist’s per-metric target fields.
  • Not preferences. Voice rules, tone, brief cadence — those live in Settings and the system prompt. Decisions are situational calls that should expire as the situation changes.
  • Not a CRM. Linear/email drafts/Slack drafts are where you do work. Decisions is just what you’ve ruled out.

​
Privacy

Decisions live in your workspace’s D1 scope. The text is fed into the brief’s system prompt at generation time and to Ask Forepost’s tools when relevant. Nothing leaves Forepost; nothing is logged externally.