Skip to main content

Workspace Memory

Memory your agents can cite.

Give the next agent context it can trace back to the work.

Aestus turns accepted work and direct human rules into cited claims. People can review, correct, or retire them before the next agent acts.

Keep the decision with the work that proved it.

A claim is not a loose note. It carries its source, authority, history, and current state into the next recall.

Example — fictional team and data. Not a live run or customer result.

Workspace Memory

Current lineage
  1. A person writes the rule

    Human ruleCurrent
    Migrations run by hand after deploy; never assume a merge applied them

    Written by · Maya Chen

    Source · Workspace brief · Deployment rules

  2. The next agent recalls it

    Claude Code

    Launching on · AES-203

    Ship the carrier-rate refresh · 2 claims served

    1. Decision
      Rank 1

      Release owners run migrations after each production deploy.

      MEM-041 · Accepted run · AES-184

    2. Constraint
      Rank 2

      Migrations run after deploy.

      MEM-042 · Workspace brief · Deployment rules

  3. One correction updates what follows

    Corrected by · Maya Chen

    ConstraintSuperseded

    Migrations run after deploy.

    MEM-042

    ConstraintCurrent

    Migrations run by hand after deploy; never assume a merge applied them

    MEM-044 · Correction · Maya Chen

    Next recall · AES-204
    Serves MEM-044 · Rank 1

Cited, not conjured.

Open the source behind a claim instead of asking an agent to defend a sentence from memory.

  • Evidence on every claim

    Each claim links back to the accepted work or direct human rule that supports it.

  • Work earns memory

    Accepted or corrected work can become memory. Agent chatter does not become truth by default.

  • Changes keep their lineage

    A correction supersedes the old claim and preserves the record of what changed.

Example — fictional team and data. Not a live run or customer result.

Claim evidence

Cited

A migration is not applied by a merge.

Accepted run · AES-184Accepted work

Open the source and review the full decision

Promoted by evidence, vetoed by people.

Automatic promotion still has a visible human stop. Review, correct, demote, retract, or purge a bad lineage from one place.

  • Human evidence comes first

    Automatic promotion requires human-anchored authority, a confidence floor, and passed screening.

  • The queue shows what needs attention

    See candidates, contradictions, stale claims, and the source behind each one.

  • A person keeps the last word

    Correct or retire a claim before another agent receives it as current context.

Example — fictional team and data. Not a live run or customer result.

Curation queue

Needs review

Deploys always run migrations automatically.

Superseded workspace briefAging

Correct, demote, retract, or purge this lineage

The hard questions belong on the page.

Memory changes what an agent may believe. Its safety rules must be as visible as its benefits.

What if an agent teaches itself something wrong?

Agent-only proposals stay quarantined. Automatic promotion needs human-anchored evidence. A person can demote, correct, retract, or purge the lineage.

Will another organization see our memory?

No. The organization is the tenant wall. Every memory read and write is scoped to the organization and workspace.

What happens when the source changes?

A changed source marks derived claims for review or retires them. The old row stays in the audit trail and stops entering new agent context.

The production baseline this page owns.

27 claims served before launch
Claims recorded as delivered to an agent in the whole life of the feature before this launch work began. The count has grown since; this is the line it started from.
2 serving surfaces
Until 2026-09-04 only Copilot had ever recorded a serving. Agent sessions outside the product now read the same claims through the same audited path, and the log records which surface received which claim.
16,958 seconds to first recall
Average elapsed time from a claim becoming valid to its first recorded serving in the measured production set.

Production Workspace Memory serving log · baseline measured 2026-09-01, re-measured 2026-09-04

Won't shared memory become shared misinformation?

Not by default. Claims need evidence, promotion is screened, every source stays attached, and a person can correct or retire what agents receive.

Give the next agent a source.

Talk to us