Stronger every day

One memory for the whole company. Every task reads what it knows before it starts, and adds what it learned when it finishes. Another company can never read it.

Every team, one memory

Teams, roles, and tasks are labels on one enterprise memory, not private vaults. Feedback, product knowledge, and every run’s outcome go in, and every team reads it back.

Learns from

  • You / Feedback

    “Lead with the price, not the features.”

  • Docs / Product knowledge

    “Annual plans renew on the 1st.”

  • Runs / Outcomes

    “Short subject lines get the replies.”

Enterprise memory

  • Lead with the price, not the features.
  • Annual plans renew on the 1st.
  • Short subject lines get the replies.

Another enterprise cannot read it.

Every team reads it

  • Support

    Renewal replies

    Uses “Annual plans renew on the 1st.”

  • Marketing

    The launch email

    Uses “Lead with the price.”

  • Sales

    Proposal follow-ups

    Uses “Short subject lines.”

Example: Northstar

One team learns it. Every team knows it.

Ask first, add after

Before work, a task asks what the company already knows. After work, it adds what is worth keeping: a decision, a preference, a verified outcome, or a failure.

RunsPublish the weekly postRun 214

  1. run.running09:00

    Run started

  2. tool.memory.ask09:00

    Asked what the company knows

    Lead with the price, not the features. Send these weekly, not daily. Short subject lines get the replies.

  3. tool.cms.read_draft09:02

    Drafted the post from the notes

  4. gate.approved09:31

    You approved it

  5. tool.cms.publish09:31

    Published

  6. tool.memory.train11:31

    Added what it learned

    Outcome: the post that led with the price got twice the replies.

Example: Northstar

Your part shrinks

On day one a task knows your brief. By day ninety it knows your voice, your product, and your customers.

Task / Draft the weekly newsletter

  1. Day 1

    It knows: Your brief

    You rewrote the draft

  2. Day 7

    It knows: + Your voice

    You edited the intro

  3. Day 30

    It knows: + Your product

    You changed one line

  4. Day 90

    It knows: + Your customers

    You approved it as written

Illustration: Northstar’s weekly newsletter

The more it knows, the less you add.

Teach it, correct it, open it

Every note is on the graph: what it knows, how it knows it, and what it relates to. Open one to see its evidence and who it came from. Correct it by training it again: the correction supersedes the old note, which stays on the record.

MemoryEnterprise

CorrectionIn use

Offer one month free to anyone who asks to cancel.

Replaces Offer 20% off to anyone who asks to cancel.

Evidence
You, training it in chat: a month free keeps more customers than 20% off.
Recorded
Mar 20
Labels
SupportAnswer a billing question

Related

  • Same task: Annual plans renew on the 1st of the month.
  • Same team: Enterprise customers get a named contact.
Example: Northstar memory

Nothing is retired. What it knows evolves as you train it.

Ask and train, anywhere

Ask and train are the same contract in the portal, on the API, and in a run. A cloned task writes into the company that installed it, never the one that built it.

Ask and train, by where they are called from
WhereAskTrain
In the portalAsk on any layerTeach a note in your words
Via a chatAsk a team member what the company knowsTell them in the thread, in your words
On the APIGET /v1/tasks/:taskId/memory/askPOST /v1/tasks/:taskId/memory/train
With MCP callsmemory.askmemory.train
In a runmemory.askmemory.train