Forget reaches derived copies

The idea

When a person forgets a note, the platform also rewrites the copies that work made from it: briefs, plans, findings, logs and outputs. It also cancels approvals and holds outreach that quote the note.

The problem
A forgotten note's words survived in what work made from it.
Why it matters
A Forget reaches every place where a worker could read the note back.
Where it stands
In production as of

A step-by-step replay of this idea is not published yet. The library adds one when a recorded run shows it.

  • Plan source basis and correction holds

    Each plan revision records every source it cited or followed, with its version. A material change sends the plan back once, and consequential actions check their evidence again.

  • Erasure by tombstone, log untouched

    Owner-only calls erase an organization or a person in one transaction; the person becomes a tombstone and audit rows point at it, so the log is never edited.

  • Scoped knowledge grants to partners

    An admin grants a partner org a selector of memories or documents with an audience and expiry; the partner recalls them at read time, labeled as outside data, and revoke or Forget removes them at once.

  • Portable learned state

    An owner exports preferences, rule candidates, checkers, approved examples and procedures as inert archives. An import creates private copies and leaves out other people's data.

  • Append-only, hash-chained audit log

    Every event is appended to a per-org hash chain that a database trigger keeps from change or deletion, with secrets redacted first.

  • Hybrid memory recall

    Recall ranks memories with full-text and trigram search, plus vectors where embeddings exist. It says which arms ran and why vectors are off, and it gives the worker its readable memory as files.

Turn the numbers into shipped work.

Crewshal runs these choices for you: a persistent AI worker with memory and rules, on your Claude and Codex subscriptions.