Context LatticeBy Private Memory Corp
Guide 1

Installation Guide

Launch Context Lattice in Lite or Full mode with verified health checks and explicit startup commands.

Default launch command

gmake mem-up is the standard stack launch entrypoint

gmake mem-up uses the active COMPOSE_PROFILES value from .env (or core if unset).

  • Force full mode: gmake mem-up-full
  • Force core mode: gmake mem-up-core
  • Lite compose stack: gmake mem-up-lite
Foolproof start

Use gmake quickstart on first install

This command creates missing env wiring, runs secure bootstrap, starts services, and validates health/auth so you do not get stuck on early 401 errors.

gmake quickstart
Auth note

Secure default means some endpoints require API key

Use /health unauthenticated. Use x-api-key for /status, /memory/*, and /telemetry/*.

Storage layout

Hot local code + cold external data (recommended)

Keep active project source local for speed, and map high-growth service data paths to external NVMe before heavy ingest.

# keep source local
~/Documents/projects

# move service data to external SSD
/Volumes/<external-ssd>/memmcp/qdrant
/Volumes/<external-ssd>/memmcp/mongo
/Volumes/<external-ssd>/memmcp/mindsdb
/Volumes/<external-ssd>/memmcp/letta
/Volumes/<external-ssd>/memmcp/orchestrator
  • Why: avoids laptop internal SSD exhaustion during fanout + rehydrate windows.
  • When: set mount paths before first full-mode launch.
  • Check: verify free space before running rehydrate/backfill jobs.
Flexible Launch

Choose your install mode

Lite installation

Runs the core memory services only. Best for laptop-first or resource-constrained local deployments.

  • Services: Orchestrator, Memory Bank MCP, Mongo raw, Qdrant, MCP hub
  • Resource target: 2-4 vCPU, 4-8 GB RAM, 25-60 GB SSD
  • Startup command: gmake mem-up-lite

Full installation

Enables full retrieval fabric and operations stack including analytics, observability, and deeper RAG support.

  • Services: Lite stack plus MindsDB, Letta, and observability profile
  • Resource target: 6-8 vCPU, 16-24 GB RAM, 120-200 GB SSD
  • Startup command: gmake mem-up-full (or gmake mem-mode-full then gmake mem-up)
Prerequisites

Before first launch

  • Docker Desktop with Compose v2
  • gmake, jq, rg, python3, and curl
  • Project root initialized with .env and compose env symlink
cp .env.example .env
ln -svf ../../.env infra/compose/.env

# foolproof first-run bootstrap (generates API key + runs smoke)
BOOTSTRAP=1 scripts/first_run.sh

# helper for authenticated orchestrator endpoints
ORCH_KEY="$(awk -F= '/^MEMMCP_ORCHESTRATOR_API_KEY=/{print substr($0,index($0,"=")+1)}' .env)"
Install path

Lite mode steps

  1. Configure environment from the repository root.
  2. Start the Lite profile.
  3. Check service state and endpoint health.
gmake mem-up-lite
gmake mem-ps-lite
curl -fsS http://127.0.0.1:8075/health | jq
curl -fsS -H "x-api-key: ${ORCH_KEY}" http://127.0.0.1:8075/status | jq
Install path

Full mode steps

  1. Set full profile mode for compose-backed startup.
  2. Bring up the stack and watch logs.
  3. Validate API, queue telemetry, and retention telemetry.
gmake mem-mode-full
gmake mem-up
# or force full directly:
gmake mem-up-full
gmake mem-ps
gmake logs
curl -fsS http://127.0.0.1:8075/health | jq
curl -fsS -H "x-api-key: ${ORCH_KEY}" http://127.0.0.1:8075/telemetry/fanout | jq
curl -fsS -H "x-api-key: ${ORCH_KEY}" http://127.0.0.1:8075/telemetry/retention | jq
Verification

Expected healthy outcomes

  • /health returns ok for orchestrator and connected services.
  • /status (with x-api-key) lists Memory Bank and Qdrant connectivity.
  • /telemetry/fanout (with x-api-key) shows queue depth and retry counters.
  • /telemetry/retention (with x-api-key) reports retention cadence and sweep activity.