memdsl

memdsl

[English](#english) | [中文](#中文)

English

Agent memory as source code the agent reads itself.

0.9 release line with experimental Edges

Version 0.9.0 adds an opt-in memdsl.workspace.v3 first-class explicit Edge

experiment. It does not rewrite the frozen 0.8 contract: legacy relations and

authority remain compatible, explicit Edge proposals always require a human,

and explicit supersedes is graph-only. Source remains runtime authority;

review/audit is a workflow contract, not a non-bypassable grant ledger. See

[the Phase 6 design and risk matrix](docs/DESIGN_explicit_edges_phase6.md) and

[the release-scope evidence freeze](docs/RELEASE_SCOPE_PHASE6.md).

Stable 0.8 compatibility contract

The 0.8 contract combines the previously unpublished navigation and View work

now shipped by 0.9.0; neither 0.7.0 nor 0.8.0 was released separately. Stable

public contracts include the v1 compatibility/authority surfaces, Catalog v1,

Trace v1, indexed

query/search trace, report diagnostics, public rebuildable CompiledWorkspace

/ compile_workspace, memdsl.workspace.v2, exact use, the generic

dialect_mapping capability, ViewContext/ResolvedView, and the explicit

opt-in v2 read schemas. Map v1 remains supported throughout the 0.8 line and

will not be reconsidered for removal before 1.0.

The software release is 0.9.2, anchored by tag v0.9.2. It adds official

MCP Registry metadata and a UV-based MCPB installer for the default-read-only

memdsl-mcp server. Parser, schema, review, query, authority, and MCP tool

contracts are unchanged from 0.9.1. Neither patch nor package-level release

promotes the opt-in Edge surface to stable or makes automatic Edge generation

authoritative.

The real-world rollout quality of quarantine/strict, dialect-candidate

learning, and host-attested principal integration is still experimental and

opt-in. Their safety invariants are not experimental: authorization happens

before aggregation, incomplete hard-rule evaluation never becomes ALLOW,

non-authoritative edges never gain authority, and repair paths remain open.

CompiledWorkspace is a public rebuildable handle; its cache/index layout,

compiler contract strings, and synthetic timing constants remain implementation

details. Workspace-v3 first-class Edges are experimental. Automatic dialect

learning, automatic Edge candidates, inferred authority, and cold-history/

incremental compilation are not shipped. Host extraction/sanitization and

private schemas/policies/samples remain outside memdsl and are not release

gates.

memdsl started with a retrieval failure. A memory system built on RAG failed

to recall a memory it certainly had; a coding agent pointed at the same raw

memory files traced it down in a few steps. Same model — the difference was

the context contract. The agent knew the memory existed and could keep

reading toward it; the retriever got exactly one similarity guess, and a

miss looked identical to absence.

memdsl turns that difference into the product. Long-term memory lives in

readable, lintable, reviewable .mem source files, and every runtime

surface is built for an agent that reads memory itself:

• A bounded memory Catalog (memdsl catalog, MCP memory_catalog /

memdsl://catalog, Python build_memory_catalog): paged module/type/subject/

status navigation with item and byte budgets, revision-bound cursors, and no

duplicated structured/text representation. It is the recommended

session-start surface for large workspaces.

• A compatible memory map (memdsl map, MCP memory_map /

memdsl://map): the existing v1 full index remains available for older

clients and is not silently changed into Catalog.

• Indexed queries that explain their misses (search_trace in every

serialized pack): deterministic lexical postings preserve the v1

EvidencePack ordering and authority lanes while exposing View/source