A store that answers queries on demand is still passive. The real value is a system that knows what is relevant before you ask — one that remembers what you worked on yesterday, surfaces the decision you forgot last month, and assembles exactly the right context before sending anything to a model. v0.7.0 is that layer: gradatum stops treating each session as stateless and starts reasoning over everything it has accumulated, on your hardware, across time.
- Assembles relevant context before each query — not raw retrieval
- Memory window slides with the conversation — no context cliff
- Proactively surfaces what you forgot you knew
- Declarative user profile — gradatum knows who it is talking to
- Picks only the skills relevant to the current task
Deleting a note used to mean losing it. v0.8.0 turns on-demand delete into an archival operation: the note's Markdown and its history move under an archive tree, a durable JSONL tombstone is written before the cascade, and the note stays recoverable until a configurable 60-day retention deadline, after which a registry-driven GC destroys it. Restoring re-indexes the note as pending-review, so it re-enters the curator instead of going straight back to live. The whole archive lifecycle sits behind an operator-only CLI on a loopback admin namespace — agents can list archives over MCP but never delete, restore, or purge. The same train is set to add an opt-in vault audit and deduplication job, curator threshold tuning, and qualified method-call resolution in the code index — still planned within the v0.8.0 line.
- On-demand delete archives the note instead of destroying it — recoverable for the retention window
- A durable JSONL audit tombstone is written before any cascade
- Registry-driven GC destroys archives past their 60-day, configurable deadline
- Restore re-enters the curator as pending-review, never straight back to live
- Archive lifecycle is operator-only — MCP can list archives, never mutate them
- Opt-in vault audit and deduplication job, curator tuning, and code-map resolution still planned
API stability is a promise, not a feature. v1.0.0 is the version where gradatum makes that promise: the public contracts freeze, semver guarantees kick in, and anything built on top will not break without explicit notice. The Agent Layer reaches production form: gradatum-engine is a formalised install component (--with-engine / --with-gateway), the gateway routes all inference behind one alias, and the full six-binary stack deploys through Docker with network isolation. Multi-tenant isolation is hardened on the production queue path — stale-lease recovery, JWT iss/sub validation, tenant-scoped revocation — proven over 30 days of continuous operation with per-identity access scopes.
- API contracts frozen — safe to build on without breaking changes
- 30 days of continuous production operation proven
- Long-term memory benchmark reproduced and published
- Multi-user access with per-identity scopes
- Engine formalised as an install component (--with-engine / --with-gateway)
- Multi-tenant isolation hardened on the production queue path
- Full stack via Docker — six binaries, network isolation
Text was always just the starting point. v2.0.0 extends gradatum to images, audio, and documents — and introduces long-horizon memory consolidation, where the system compresses and learns from its own history over time. This version also ships gradatum-code: a terminal agent that reasons over your codebase using vault memory, recalls past decisions, and executes tasks end-to-end on local hardware — nothing leaves your machine. This is a breaking change by design: the chat API is rebuilt to handle multimodal input natively, completing gradatum's arc from a local knowledge store to a full cognitive infrastructure.
- Images, audio, and documents understood alongside text
- Long-horizon memory consolidation — the system learns from its own history
- Sovereign terminal agent — reasons over your codebase and executes tasks end-to-end
- Runs entirely on local hardware — nothing leaves your machine