README.md

Developer Documentation

This section is for developers working on Memory Layer itself: architecture, internal workflows, packaging, plans, and skill-facing material.

Table of Contents

• Quickstart
• Architecture
• Implementation Material
• Related Docs

Quickstart

Run a fully isolated dev copy of Memory Layer alongside any packaged install on the same machine:

cargo run --bin memory -- init
cargo run --bin memory -- dev --copy-from-global
cargo run --bin memory -- service run            # 4250 HTTP
cargo run --bin memory -- tui                    # header reads [dev]

The dev stack is detected automatically when the binary path lives under target/{debug,release}/ and reads its config from the user-local project config.toml plus a user-local project config.dev.toml overlay — never from the installed global config.

For the full isolation contract, default ports, override flags, and troubleshooting, see Dev Stack vs Installed Stack.

Architecture

• Architecture Decision Records
• Dev Stack vs Installed Stack
• Architecture Overview
• Protocol-Neutral Federation Spike Contract
• Authentication And Authorization
• Code Map
• Built-In MCP Server
• Memory Types Reference
• How Memory Layer Works
• Embeddings and Search
• Hidden Memory Daemon
• Error Messaging And Diagnostics
• Automated Evaluation
• Memory Improvement Benchmark
• GitHub Actions
• Release Readiness

Implementation Material

• Implementation Plans
• Skills And Agent Material
• How Skills Work
• Examples
• Federation Protocol Spike

Related Docs

• User Documentation
• Project README