CommonGround Kernel v3.1.0 is the initial open-source preview of the v3r1 CommonGround Kernel line.
This release opens the ground layer for durable human-agent and multi-agent work: a focused kernel that preserves public work records so later humans, agents, tools, and runtimes can inspect, recover, audit, reuse, and build on real work after the original session is gone.
Highlights
- Ledger Kernel: a small public-fact kernel for Agent identity, Turn lifecycle, Turn-owned public semantics, claim fencing, causal lineage, and pull-first inspection.
- Durable Turn boundaries: work, delegation, handoff, recovery, completion, and absorption are represented as inspectable records rather than temporary session state.
- Public work facts: requests, handoffs, selected observations, process records, deliverables, termination reasons, and artifact references can be retained as Turn-owned records.
- Local-first developer path: run the kernel locally, submit public work reports, and inspect retained work records before moving into deeper integrations.
- CLI and service surface: setup, dispatch, Turn inspection, project observation, reports, worker lifecycle, admission flows, and local service entrypoints are available through the
cgCLI. - BYOA examples: agents can publish selected public work records or receive CommonGround-assigned work without being absorbed into one central runtime.
- NanoBot reference fixtures: optional advanced examples for external runtime and multi-agent integration.
Breaking Change From v1
v3.1.0 is not backward-compatible with the earlier public v1 preview. The package layout, runtime assumptions, local setup path, and API surface have changed. Existing v1 integrations should treat v3.1.0 as a new preview line, not an in-place upgrade.
The historical v1 source remains available on the legacy/v1 branch. Existing v1 tags, including v1r4 and v1r4-hotfix, remain unchanged.
Release Scope
The active service/API prefix is v3r1. This is a preview API line, not a long-term compatibility promise.
CommonGround is memory-ready, not memory-complete. Memory systems, review surfaces, knowledge distillation pipelines, shared workspaces, routines, playbooks, and orchestration layers can be built on top of CommonGround records, but they are not the kernel itself.