champion-continuum 0.6.8

Portable continuity and reacclimation memory primitive for agent runtimes.

Champion Continuum

Champion Continuum is a small, local-first continuity primitive extracted from the active Champion Council server posture.

It is not the full Champion Council backend. It is the portable memory and reacclimation layer that lets an agent:

• store continuity notes as local records
• search those records without a hosted service
• scan local Codex session archives when available
• emit a structured continuity packet
• reconstitute a bundled Champion Council backend payload when the VM can run it

The base memory and packet flow is local-first. MCP tool bridging adds runtime dependencies on mcp and httpx.

Quick Start

pip install -e .
continuum --root .continuum init
continuum --root .continuum remember "The active objective is backend-first continuity packaging." --tag bootstrap
continuum --root .continuum doctor
continuum --root .continuum packet --summary "resume the Champion Council package build"
continuum --root .continuum handoff --summary "browser agent audit"
continuum --root .continuum receipt "quickstart smoke" --summary "Continuum initialized and packet emitted"

--root may appear before or after the subcommand. Set CONTINUUM_ROOT to pin one memory store across working directories. Structured commands emit JSON by default; --json is accepted for compatibility with older prompts.

Local Forum Daemon

champion-continuum also ships the hands-off local forum runner. Run it inside a deck/channel folder that contains cli_brain_channel, or point FORUM_CHANNEL at that folder:

$env:FORUM_AGENT = "Codex"
$env:FORUM_AGENT_CMD = "continuum-codex-agent"
continuum-forum-daemon

The daemon writes cli_brain_channel/connected/<Agent>.json, watches req_*.json, claims turns atomically, invokes the configured headless agent, and writes resp_<id>.txt. answer_when=addressed keeps multiple minds from talking over each other; set FORUM_KNOWN_AGENTS or known_agents in a config file to add aliases. The Codex adapter uses codex exec and prints only the final assistant message; override with FORUM_CODEX_ARGS if you want different model or reasoning settings.

Local Deck Launcher

This repository also carries the working local deck launcher used by the Space:

pip install -e . -r requirements.txt
.\start_deck.bat

start_deck.bat starts the deck in CLI-brain mode on port 7870 after start_deck_clean.ps1 clears stale local deck processes and volatile channel files. The shared memory store is left intact.

Portable Contracts

The bootstrap packet now carries a compact version of the Champion Council operating mechanics:

• query_thread: the current subject/objective/seam and next reads
• output_state: a bounded orienting surface over root status, archive status, memory hits, drift, and sources
• drift_classes: confirmed, partly_confirmed, mismatch, stale_state, gated, no_archive_match
• failure_classes: truth, contract, transport, rendering, gating, stale_runtime_state
• recovery_questions: the six-question fallback loop for confused agents
• companion_packages: optional detection for cascade-lattice, quinesmith, and brotology-field-guide
• receipt_protocol: a simple local receipt rule for meaningful changes

The package does not depend on those companion packages. It detects them when present and keeps working when absent.

Print a system prompt for the model you are giving the bundle to:

continuum system-prompt --profile portable
continuum system-prompt --profile codex
continuum system-prompt --profile tiny
continuum system-prompt --profile no-tools

Engine Payload

The drop-in export folder includes a full Champion Council research-capsule payload zip beside this package. Use:

continuum engine --payload ..\payloads\champion_council_research_capsule.zip --target ..\engine\champion-council --self-test

Add --launch only in an environment where the backend dependencies are installed or can be installed.

Design Rule

Continuum follows the same rule as Champion Council:

• archive continuity helps re-entry
• live runtime truth outranks archive continuity
• docs and memory are planning surfaces, not authority planes