sheawinkler/ContextLattice

Open an agent. Already there.
The local-first intelligence layer that gives AI agents durable continuity, explainable retrieval, portable context, and verified learning across harnesses.
Quickstart ·
How it works ·
Agent setup ·
Architecture ·
Docs ·
Updates
Stop replaying the brief
Models can reason. Harnesses can act. Neither reliably retains the mission when a chat, model, tool, account, or computer changes.
ContextLattice 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.
| Capability | What changes |
| --- | --- |
| **Durable continuity** | Reopen the objective, decisions, repository state, risks, proof, and next move as one bounded packet. |
| **Explainable retrieval** | Rank evidence by impact per token and expose source coverage, omissions, opposition, degradation, and receipts. |
| **Portable context** | Move signed, least-privilege continuation across agents and machines while keeping execution and transport caller-owned. |
| **Verified skill evolution** | Discover skills without loading every file, evaluate repeated wins on holdouts, and require review before promotion. |
| **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. |
The **CLI is the primary interface**. The dashboard makes behavior and proof visible. HTTP and MCP are companion integration surfaces for applications and harnesses.
How it works
| Stage | ContextLattice does |
| --- | --- |
| **01 · Reopen** | Reconstructs the one active mission from durable checkpoints and current state. |
| **02 · Select** | Retrieves high-signal evidence into a compact Context Pack with provenance. |
| **03 · Move** | Carries signed, bounded context through Agent Packets, Passports, and encrypted continuation envelopes. |
| **04 · Earn** | Records outcomes and promotes reusable behavior only after deterministic proof and human approval. |
| **05 · Compound** | Improves future retrieval while preserving corrections, contradictions, freshness, and retirement semantics. |
ContextLattice 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.
Quickstart
Requirements: 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.
1. Install
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.
2. Verify the runtime and retrieval path
Healthy 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.
For a fuller lifecycle proof from the repository:
Connect your agents
Run integration from the repository that should use ContextLattice:
The 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.