CCortorreal

Continuity Core — Development skill for Claude Code

Development community

Provider-neutral bones of a multi-agent session-continuity system: a lock-file transactional checkpoint store, a deterministic route planner, and a Claude/Codex tool-envelope mapper.

How to install Continuity Core

This entry records only its repository, not the path inside it, so there is no exact command to give. Open CCortorreal/continuity-core and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Continuity Core does

Provider-neutral bones of a multi-agent session-continuity system: a lock-file transactional checkpoint store, a deterministic route planner, and a Claude/Codex tool-envelope mapper. Zero dependencies.

Alternatives in Development

Puppetmaster — Provider-neutral control plane for durable-state agent swarms: subprocess workers, leases, artifacts, memory 340 ★
Orchestrate Saga — Generate strict <3900-char goal-orchestrator prompt for a saga and lock via /goal 160 ★
Al Memory.Create.Prompt — Generate or update memory.md file tracking decisions, changes, and learnings throughout project development fo 109 ★

README

continuity-core

The provider-neutral bones of a multi-agent session-continuity system: a transactional checkpoint store, a deterministic route planner, and a Claude/Codex tool-envelope mapper. Zero dependencies, Node >= 18, ESM only.

This is the general-purpose layer extracted from a working multi-agent setup — see [Provenance](#provenance). It does not include a message broker, a permission policy engine, or any hook wiring for a specific host; those are workspace-specific and live elsewhere (a sibling project, **the-wire**, publishes a durable local broker built on the same lock-file primitives).

The three primitives

`store` — a transactional checkpoint store

A checkpoint is a small curated JSON object — `objective`, `decisions`, `completed`, `next`, `references` — that one agent writes so another agent (or the same agent after a context compaction) can resume without re-reading a transcript. `store` gives you:

A lock-file transaction. mkdir .lock is the mutex — atomic on every target filesystem this library expects to run on. The update runs, the result is written to a temp file, fsynced, then renamed over the target. A crash mid-write leaves the old file intact; a crash mid-lock leaves a lock directory behind, on purpose (see `docs/FIELD-NOTES.md` for why removing a stale lock automatically is the wrong move).
Revision-conflict detection. Every save() carries the revision it expects to be replacing. If the task has moved on, save() throws Revision conflict and writes nothing. Never blindly retry a revision conflict with the same checkpoint. Re-read the task, see what the other writer decided, and resubmit a checkpoint that accounts for it. An eventId makes a retried identical write (same id, same content, same writer) a no-op instead of a conflict — that is the one case that is safe to retry automatically.
Checkpoint validation that rejects secrets by regex. Every t