![\"ContextLattice](\"docs/readme/contextlattice-editorial-hero.png\")
\n \n\n \n \n \n
\n Open an agent. Already there.\n
\n\n\n The local-first intelligence layer that gives AI agents durable continuity, explainable retrieval, portable context, and verified learning across harnesses.\n
\n\n\n ![\"CLI](\"https://img.shields.io/badge/Interface-CLI%20First-111111?style=for-the-badge\"){kind=icon}
![\"ContextLattice](\"https://img.shields.io/badge/Release-v5.0.2-292929?style=for-the-badge\"){kind=icon}
![\"Local-first](\"https://img.shields.io/badge/Runtime-Local%20First-404040?style=for-the-badge\"){kind=icon}
![\"Apache](\"https://img.shields.io/badge/License-Apache%202.0-575757?style=for-the-badge\"){kind=icon}
\n Quickstart ·\n How it works ·\n Agent setup ·\n Architecture ·\n Docs ·\n Updates\n
\n\n## Stop replaying the brief\n\nModels can reason. Harnesses can act. Neither reliably retains the mission when a chat, model, tool, account, or computer changes.\n\nContextLattice gives that work a durable, inspectable context layer. It reconstructs the active objective, selects the evidence that matters, carries it safely, and records what actually worked—without turning every prompt into a transcript dump or making cloud storage mandatory.\n\n| Capability | What changes |\n| --- | --- |\n| **Durable continuity** | Reopen the objective, decisions, repository state, risks, proof, and next move as one bounded packet. |\n| **Explainable retrieval** | Rank evidence by impact per token and expose source coverage, omissions, opposition, degradation, and receipts. |\n| **Portable context** | Move signed, least-privilege continuation across agents and machines while keeping execution and transport caller-owned. |\n| **Verified skill evolution** | Discover skills without loading every file, evaluate repeated wins on holdouts, and require review before promotion. |\n| **Privacy-bounded Aggregate Signal** | Learn from explicitly opted-in, clipped statistics while raw memory remains local; production activation stays hard-blocked pending independent privacy and utility review. |\n\nThe **CLI is the primary interface**. The dashboard makes behavior and proof visible. HTTP and MCP are companion integration surfaces for applications and harnesses.\n\n## How it works\n\n| Stage | ContextLattice does |\n| --- | --- |\n| **01 · Reopen** | Reconstructs the one active mission from durable checkpoints and current state. |\n| **02 · Select** | Retrieves high-signal evidence into a compact Context Pack with provenance. |\n| **03 · Move** | Carries signed, bounded context through Agent Packets, Passports, and encrypted continuation envelopes. |\n| **04 · Earn** | Records outcomes and promotes reusable behavior only after deterministic proof and human approval. |\n| **05 · Compound** | Improves future retrieval while preserving corrections, contradictions, freshness, and retirement semantics. |\n\nContextLattice does not replace your agent harness, choose goals from retrieved text, or execute imported context. Local tools remain execution surfaces; memory and remote content remain evidence.\n\n## Quickstart\n\nRequirements: macOS, Linux, or Windows through WSL2; a Compose v2-compatible container runtime; and `gmake`, `jq`, `rg`, `python3`, and `curl`. The tested macOS baseline uses OrbStack through its explicit Docker context; see the [container runtime decision](docs/runtime/container-runtime-decision.md).\n\n### 1. Install\n\n```zsh\ngit clone https://github.com/sheawinkler/ContextLattice.git\ncd ContextLattice\ncp .env.example .env\ngmake quickstart\n```\n\n`gmake quickstart` is the prescribed technical install path; installers are bootstrap alternatives. The command prepares environment wiring, asks for a runtime profile, launches the selected local stack, and validates initial readiness.\n\n### 2. Verify the runtime and retrieval path\n\n```zsh\ncurl -fsS http://127.0.0.1:8075/health | jq\ncontextlattice doctor --pretty\ncontextlattice state status --pretty\ncontextlattice context \"verify this ContextLattice installation\" \\\n --project contextlattice \\\n --pretty\n```\n\nHealthy containers are only the first check. The state command verifies the canonical gateway-owned storage inventory; the final command exercises the actual context path and reports source coverage, degradation, evidence, and next actions. Existing installs can use the explicit, reversible procedure in [gateway state migration](docs/runtime/gateway-state-root.md).\n\nFor a fuller lifecycle proof from the repository:\n\n```zsh\nscripts/agent/agent-runtime-proof-pack --pretty\nscripts/agent/agent-adoption-proof-matrix \\\n --skip-provider-smoke \\\n --progress \\\n --pretty\n```\n\n## Connect your agents\n\nRun integration from the repository that should use ContextLattice:\n\n```zsh\ncd /path/to/your/project\n\ncontextlattice_adopt integrate \\\n --repo . \\\n --agents codex,claude-code,opencode,hermes-agent,hermes-ultra,omp,mercury-agent,pi,droid \\\n --pretty\n\ncontextlattice_adopt integrate \\\n --repo . \\\n --agents codex,claude-code,opencode,hermes-agent,hermes-ultra,omp,mercury-agent,pi,droid \\\n --check \\\n --pretty\n```\n\nThe integration command writes bounded managed blocks while preserving existing instruction text. It does **not** install Codex, Claude Code, OpenCode, Hermes, OMP, Mercury, Pi, Droid, or another third-party agent harness.\n\nExternal provider discovery is network-free. Provider execution remains explicit and caller-authorized; see the [external-provider boundary](docs/runtime/external-provider-auth-boundary.md).\n\nIf an agent is performing the installation, it should follow the quickstart directly, avoid cloning a second checkout when already inside one, report the exact failing command and path, and rerun the deterministic check after any repair.\n\n## The daily agent loop\n\n```zsh\n# Confirm readiness when the environment is uncertain.\ncontextlattice doctor --pretty\n\n# Retrieve scoped context before substantial work.\ncontextlattice context \"debug the current release regression\" \\\n --project contextlattice \\\n --pretty\n\n# Save concise, durable progress.\ncontextlattice remember \\\n \"Root cause verified; regression test added; focused checks pass.\" \\\n --project contextlattice \\\n --pretty\n\n# Resume without replaying the transcript.\ncontextlattice resume --project contextlattice --pretty\n\n# Repair stale or wrong recall without silently rewriting history.\ncontextlattice correct \\\n \"The prior deployment record is stale.\" \\\n --category stale \\\n --project contextlattice \\\n --pretty\n\n# Close the loop with the verified outcome.\ncontextlattice finish \\\n \"Regression fixed and verified.\" \\\n --success \\\n --project contextlattice \\\n --pretty\n\n# Project the next bounded move or bind a completed response to durable proof.\ncontextlattice_continuous_cognition status \"prepare the next verified move\" \\\n --project contextlattice --session-id\n \n ![\"ContextLattice](\"docs/public_overview/assets/architecture-service-map.svg\") \n \n | \n \n \n ![\"ContextLattice](\"docs/public_overview/assets/architecture-retrieval-flow.svg\") \n \n | \n