memory_forget

Soft-delete a fact: closes its bitemporal window without erasing the row. The agent can no longer recall it, but the audit trail and the archive remain intact.

Input

{
  "factId": "fact_xxx",
  "reason": "user told us this is no longer accurate"
}

Output

{
  "id": "fact_xxx",
  "validTo": "2026-06-07T18:22:00Z",
  "archived": true,
  "restoreUntil": "2026-07-07T18:22:00Z"
}

The fact is copied to mnemo_fact_archive and remains restorable for 30 days (configurable).

When the agent should call it

• The user corrects a previously-stored fact.
• A codebase_verified source contradicts an existing claim.
• A periodic verification cron flags the fact as stale.

When the agent should NOT call it

• Just because the fact wasn’t useful — drop the worth instead.
• During session collapse — the system handles deduplication.
• For GDPR erasure — use the dedicated /v1/admin/erase endpoint with the appropriate scope. memory_forget is reversible; GDPR erasure is not.

Restore

A forgotten fact can be restored via /v1/facts/:id/restore within the archive window. The bitemporal window re-opens and the fact is recallable again.