Repository navigation
MESA v0.7.0
MESA v0.7.0 — v4 Full-Cognitive Release Candidate
MESA v0.7.0 introduces the new v4 full-cognitive runtime while preserving the existing v3 lexical-core API for compatibility.
Highlights
- New versioned v4 API, Python SDK, and MCP contracts
- Durable mutation ledger and projection outbox
- Ordered SQLite → vector → graph projection pipeline
- Graph V2 with canonical entities and provenance-rich assertions
- Tenant, workspace, and dataset-level authorization
- Source-aware artifact ownership, rollback, purge, and reconciliation
- True Reciprocal Rank Fusion across vector, BM25, and graph retrieval
- Single-writer combined runtime for SQLite, LanceDB, and Kùzu
- Rotation-safe, principal-bound API keys using salted scrypt hashes
- Pipeline leases, heartbeat renewal, bounded retries, replayable DLQ, and crash recovery
Canonical Data and Graph V2
Entities now use deterministic, tenant-scoped UUID5 identities derived from ontology identifiers or normalized canonical names.
Graph relationships are represented as immutable assertions carrying:
- Predicate and subject/object identity
- Source document, revision, and chunk
- Evidence span and citation
- Jurisdiction and source authority
- Confidence and temporal validity
- Mutation and pipeline-run provenance
- Contradiction and supersession relationships
Different predicates, sources, jurisdictions, and time ranges remain independently queryable.
Durable Ingestion
POST /v4/memory/insert creates a durable mutation and pipeline run before background processing begins.
Mutations progress through an idempotent lifecycle:
RECEIVED → EXTRACTED → VALIDATED → SQL_APPLIED → VECTOR_APPLIED → GRAPH_APPLIED → COMMITTED
Tier-3 validation is now a mandatory gate. Rejected information does not create active SQL, vector, entity, edge, or assertion artifacts.
Artifact Ownership and Rollback
Physical artifacts can be shared by multiple mutations and sources. Rolling back or purging one source removes only its ownership link.
Shared entities and vectors remain active while another valid source still owns them. Artifacts are physically removed only after their final active owner is removed.
Rollback and cleanup operations are durable, restart-safe, and tracked through the outbox.
Security
V4 authorization is resolved server-side through:
Principal → Tenant → Workspace → Dataset → Agent → Session
Agents remain computational or persona context and are not treated as tenant security boundaries.
The release adds:
- Tenant, workspace, and dataset memberships
OWNER,WRITER, andREADERroles- Explicit purge and rollback permissions
- Server-bound session scopes
- Cross-tenant and cross-dataset isolation
- Multiple keys per principal
- API-key rotation and revocation
- Salted scrypt hashes with key-ID lookup
Plaintext API keys are available only when initially created.
Retrieval V2
V4 retrieval combines vector, BM25, and graph rankings using true rank-based Reciprocal Rank Fusion.
Results can be filtered by authorized datasets and reranked using bounded legal and provenance signals, including:
- Jurisdiction
- Effective time
- Source authority
- Citation availability
- Assertion confidence
Deterministic tie-breaking is preserved.
Runtime and Operations
V4 supports one storage-writing combined process that owns SQLite, LanceDB, and Kùzu. Multiple processes must not write to the same storage directory.
Operational improvements include:
- Fenced claims and lease renewal
- Bounded retry policies
- Replayable dead-letter handling
- Ordered projection prerequisites
- Two-way reconciliation
- Shared-owner and orphan metrics
- Rollback and cleanup backlog visibility
- Offline backup, rebuild, parity, and cutover tooling
PageRank is now observation-only telemetry and cannot quarantine or invalidate memory artifacts.
Compatibility
- V4 is a breaking, versioned API.
- Existing v3 endpoints remain unchanged.
- V3 continues as the lexical-core compatibility runtime.
- V3 storage is not migrated in place.
- Legacy data must be backed up and rebuilt into separate v4 storage before cutover.
Release Status
MESA v0.7.0 is a release candidate and remains NO-GO for production until all external release gates are completed, including real-provider validation, production-like crash and concurrency evidence, migration and restore rehearsal, and the required 24-hour soak test.