Skip to content
Contexta
Feature

Forgetting

Retraction beats deletion. The audit survives the data.

Forget
How it works

Forgetting

Forget is a surgical Synapta call. The first pass marks edges with `retracted_at = now` rather than hard-deleting; the cascade walks `derived_from` edges, not graph topology.

  • GDPR-ready surgical forget with cascade-by-provenance
  • Past-anchor recalls still see retracted facts — bi-temporal stays intact

Primitive

Forget

Retraction beats deletion. The audit survives the data.

In practice

Built for replay, audit, and scale.

Vault drops blobs, revokes pre-signed URLs, and rotates signing keys. The audit ledger keeps a non-destructive receipt.

  • Pre-signed URLs revoked atomically with the retraction
  • Hard-purge job (per retention) replaces retracted edges with tombstones
# Declare a Reflex once, fire on every match.
reflex:
  name: supplier-risk-spike
  watch:
    cx: entity(supplier).risk_score > 0.75
  fire:
    webhook: https://hooks.example.com/supplier-risk
    cooldown: 1h
Related

Pair it with these primitives.

Synapta

Memory Graph

Entities, relationships, embeddings — one unified graph.

Read more →
Packet

Context Packets

The only output shape — provenance assembled in stages.

Read more →
Reflex

Reflexes

Declarative triggers. CX in, webhooks out.

Read more →

Try Forgetting on your stack.

Book a 30-minute walkthrough or wire it up via the API.