Audit Ledger
The append-only record of every Reflex fire, Forget operation, and policy evaluation. A query surface, not a separate forensic log — runs against the same store as recall.
Glossary
Contexta vocabulary
Every term we use across the docs, marketing site, and product — defined in one sentence. Cross-referenced where useful; opinionated where it helps.
A
B
Bi-temporal Model
Separates `asserted_at` (when we learned a fact) from `valid_from / valid_to` (when it is true in reality). Enables time-travel queries and supersession without history loss.
Bookmark
A named, persisted Context Packet reference — pins a recall result for later citation or comparison without re-running the query.
Related
C
Citation
Per-fact attribution carried in a Context Packet: source system, confidence, timestamps, and the per-stage processing metadata that traces the fact back to raw memory.
Composition Tree
A Reflex's AST describing how its Graphlets and StateWatches combine via AND, OR, AND_NOT, and WITHIN operators — allowing arbitrary boolean and temporal nesting.
Related
Context Flux (CX)
The pattern language for graph shapes and state transitions (e.g. `(c:company @status: * -> "bankrupt") -[:supplies]-> (us)`). Shared substrate for Recall queries, Reflex conditions, and Blueprint composition.
Context Graph
The unified graph of entities, relationships, embeddings, and provenance metadata in ArangoDB — the single source of truth every recall, reflex, and watch reads from.
Context Harness
The framing for Contexta's positioning — context is what holds an agent's reasoning together. Lose it and the agent guesses; keep it and the agent reasons.
Related
Context Packet
The structured, provenance-tracked output primitive returned by Recall and emitted by reactive firings — the only contract LLMs consume.
D
DEK / KMS Profile
Data Encryption Key managed by Vault per namespace, rotated in batches. Underpins data-at-rest encryption, BYOK, and compliance audits.
Drift
A scalar reactive event — a property crossing a configured band, triggering a Locus reading append and (if the band is exited) firing the host Reflex.
E
Entity Resolution
The step where embeddings merge into an existing node above the 0.85 cosine threshold rather than creating duplicates — prevents graph fragmentation across ingest sources.
Related
Episode
An ingest-bracketed chain of related events on the Episodic memory layer (90 d retention). Captures session continuity without permanent semantic commitment.
Related
F
Forget Order
A surgical retraction call. Marks edges with `retracted_at = now`, cascades along `derived_from` edges, drops blobs in Vault, and records the act of deletion in the audit ledger.
G
Graphlet
A small canonical induced subgraph (k ≤ 5; 29 distinct shapes) used as an internal indexing substrate. Accelerates Motif lookup and structural scoring. Not user-facing.
I
Ingest
The six-stage flow that forms memories: extract → embed → resolve → persist → orbit → react. Every stage stamps provenance; reactivity is automatic on write.
L
M
Memory Layers
Five tiers — Working (Redis, 1 h), Episodic (90 d), Semantic (vector + graph, permanent), Procedural (triggers), Archival (S3, per policy). Retention and latency follow access pattern.
Related
Motif
A registered, deduplicated pattern entry decomposed from a Reflex's CX. The engine indexes Motifs against the graphlet/orbit substrate; one Motif can serve many Reflexes.
N
Namespace
The logical tenant boundary. Every query, ingest, and trigger is scoped by namespace; per-tenant KMS profiles, rate limits, and isolation all hang off it.
O
Orbit Vector
A node's structural role within its surrounding graphlets, recomputed asynchronously after ingest. Powers motif-coverage scoring during Recall.
Related
P
Policy Bundle
A set of per-tool and per-data rules attached to graph nodes — sensitivity marking, rate limits, PII masking, consent gating — enforced natively via Reflexes.
Related
Provenance Edge
Every edge carries `source_system`, `confidence`, `asserted_at`, `valid_from`, `valid_to`, `retracted_at`, and `verification_status` — the substrate that makes Contexta prove, not just recall.
R
Reading
A typed history entry on a Locus — `entry`, `property`, `lifecycle`, or `temporal`. Loci hold readings so prior values are always available without an auxiliary state store.
Recall
The three-stage flow that surfaces context: retrieval (parallel semantic + graph probes, temporal filter) → enrichment (motif → score → top-K) → assembly (Context Packet).
Reflex
A reactive trigger that owns a CX expression and decomposes it into Motifs; fires once per Locus that satisfies its composition tree. Covers both structural events and scalar drift.
S
Snapshot
A point-in-time projection of the Context Graph derived from a bi-temporal anchor — used internally for time-travel recalls; never a separate stored object.
Synapta
The proprietary graph memory engine that owns the Context Graph, the reactive trigger pipeline, and the Context Packet assembler. Sits on ArangoDB plus Redis.
Related
T
Time Travel Query
A Recall with an `as_of` anchor — the engine applies four bi-temporal predicates so only facts known and valid (and not yet retracted) at the anchor survive.
Trigger Engine
The Synapta component that evaluates Motifs against graph deltas, materialises and vacates Loci, walks composition trees, and fires Reflexes — all within the same request lifecycle.
V
Vault
The security service that holds API keys, secrets, and file metadata in Postgres with S3 for blob storage. Hosts the trust boundary separately from memory data.
Spotted a term we missed?
The glossary grows with the product. Send us your gap — we will write the entry.