Continuity Evidence

Message package preview — 10 October 2026: Core11, remote6, gateway11 and evidence12 add the optional saved-record explanation command. See the current release guide. Existing API/policy/proof behavior stays unchanged; older npm archives remain available.

Source preview.13: MCP client/server/core updated to 2.2.0 for GHSA-6qxp-vccf-f47h. New MCP archives are source-prepared; npm and Registry still select the earlier published tuple.

Previous source preview.12.1: Plain-language messages, completed historical ZK experiments, and retained-receipt reader source. The installable packages now include the optional saved-output explanation command; use the exact tuple in the release guide.

Current developer preview: Exact versions and installation.

Follow an investigation: Follow one protected case through interruption, replacement, a signed completion, new evidence and a persistent challenge. Run the walkthrough.

Continue an existing case: Same case, longer history, preserved permissions and unfinished duties. Start with supported profiles, migration and recovery, or the protected evidence example.

Core 0.3 preview: Build a fresh case, connect approved MCP tools, or run the public tests. The original 0.2.2 evaluation releases remain available.

[it is 2 a.m. do you know what your agent is doing?] [Security. Control. Inheritance. Durable survival of powers and responsibilities. Record durably, locally or on chain. This is your agent’s brain on Continuity.]

Continuity — agents change; responsibility remains

Explore the interactive demo → · Start here · Developer guide · Security and limits

Try your own choices in the playground → No installation or account needed.

Developer preview · Apache 2.0. Release status.

A process supervisor can start Agent B. Continuity records which role B occupies, which powers it has, what happened before, and which unfinished duties survive the change. A replacement receives its explicitly granted powers; an unfinished duty does not silently grant more authority.

The original tutorial follows a security investigation interrupted by an agent replacement. The old request is refused, the investigation stays OPEN, and the successor’s review permission is checked independently.

Choose your path

Run the tutorial

Use Node 22.18+ (22.x), 24.x or 26.x on macOS or Linux. Prefer the latest patch of your chosen release. No global pnpm or Python is needed for this tutorial. Full quickstart, including archive extraction.

Get the public source; no GitHub account is needed:

git clone https://github.com/zerohourzulu/continuity.gitcd continuity

See the result first, without installing dependencies:

node examples/recorded.mjs

Expect ALLOW for reviewing the investigation and DENY for collecting another packet. This inspects a bundled recorded case; it does not execute a new action.

Generate your own evidence:

node tools/setup.mjsnode tutorial/start.mjs

Expect PASS — duty remains OPEN; B has no collection power, then VERIFIED. Setup downloads locked dependencies with scripts disabled. The tutorial then runs locally using synthetic data and public test keys. It prints your new case name and exact follow-up commands. Rerunning creates another case and preserves earlier evidence.

Change one permission:

node tutorial/start.mjs --deny-review

B still inherits the duty, but its review permission becomes DENY. Expected output and explanation · Setup checks and recovery.

Choose your holder of record.

Keep records locally, or choose a chain-backed deployment to make selected history publicly verifiable. Cryptographic commitments can let authorized reviewers check private records without publishing their contents. This tutorial runs locally; each deployment has its own privacy, availability and finality requirements.

Explore and build

Presentation maintainers can find the separate owner-private edition in website maintenance. The public walkthrough needs no account.

Contribute and explore

Read the short development history from Core 0.1 to the current reference implementation. Contributions and public RFCs are welcome; an RFC is useful for changes to protocol behavior or security boundaries.

Scope

Core 0.2.2 is local reference software. It is not a hostile-agent sandbox, production credential system or autonomous cyber defender. The website selects recorded results; the downloaded tutorial executes Core. Real integrations must mediate every consequential operation through a protected executor. Security boundaries.

The source, tutorial, tests, reader and website are included here and in the complete evaluation download. Earlier editions remain available as historical releases; use evaluation.6 for the commands above. Package overview · Presentation provenance.

Release status and licensing · Apache 2.0 license · Third-party notices

Embed the engine

Try the standalone developer package: install the supplied JavaScript SDK tarball in a separate application, create one authorized synthetic packet, and inspect why refused requests create none. Includes TypeScript declarations and an offline consumer check. This is an evaluation interface around unchanged Core0.2.2.

Shared Core integration preview

The shared-package preview connects the cooperating remote tools and MCP evidence tool to one Core dependency. Try native LangChain tools and lost-reply recovery, or the MCP evidence tool.