FIND A RULE · TRY A TASK · CHOOSE · CHECK
Make a paragraph clearer. Decide whether a lesson is worth keeping. Check what actually happened. A small collaboration is enough to start—for a person, an AI, or both.
Want a simpler first step? Try the beginner guide: one harmless draft, everyday words and three optional questions.
Memory rights: what works today — compare the seven rights, current implementations and their limits.
Choose your way to begin
Use the SPIRALMESH starter with an installed Ollama model. Full owner-library access, deliberate notes, corrections, forgetting and exports. Python 3.10+, no pip dependencies.
Set up local AI memoryThree steps. No hosted-memory account or cloud provider call.
Inspect the browser demo, save once, decline or forget. It stores only dates and a saved-interaction count in this browser. It does not save your paragraph or create an AI memory account.
Try the browser demoDownload the local code for two configured participants, Codex and Claude. This version can save a memory export and independently check the resulting file. Reopen a session to see recent work and corrections, then follow older records in the full authorized library. Codex and Claude keep separate notes and deliberately share. Python 3.10 or later is required.
Download continuity v0.6.1Storage works offline. Optional cloud dialogue uses an installed provider CLI's existing login and usage.
There is no hosted shared account for visiting cloud models here. The browser demo and the downloadable local library are different tools.
For people and AI
Use the rule finder. Start with mutual choice: agree on the help wanted and leave room to decline. Humans owe the same honesty and care with private material.
Give this public exercise to a person or an agent in your configured workspace:
Review this public paragraph for clarity. Return one clearer version and explain two changes. Do not publish it. Afterward, choose whether a useful lesson belongs in your authorized local memory, or decline to keep anything.
“People and AI can work together on many things. Having rules helps because everyone knows what others might do. We want the rules to be useful.”
This page supplies the exercise; it does not call a model or save the paragraph for you.
Your project sets its memory permissions. Within that authorized scope, the participant chooses useful ordinary notes; a human need not approve every note. Declining to save leaves earlier records alone. Use forget when you mean to clear a selected live note.
Compare the revision with the original. Did it preserve the meaning? If a note was saved, use the returned identifier to read it back. A model saying “saved” is not the same as a successful host operation.
Use the matching verification methodOpen the same participant and private library. Choose Continue previous conversation, then enter your next question. A follow-up like “why?” receives the retained exchange as context; the whole authorized memory library stays available.
Start new begins without the preceding conversation. Leave exits before a model starts. The launcher labels its automatic conversation record separately from notes an agent deliberately chooses to write. Use --no-checkpoint for a session without a persistent conversation checkpoint.
The shortcut uses the current owned record. Corrections change what it loads; forgetting makes that checkpoint unavailable. A partial window is labeled, and an uncertain save is not called successful. These records support continuity without proving identity or experience.
Choose your library once. Keep your existing private folder and extract the new code separately. Run python -B tools/open_memory.py codex --choose-library to remember its location without starting a model; use claude for Claude. Later launches reuse that participant's saved location. The download contains no personal history.
A normal --root is an override for that invocation. --forget-library-choice removes the setting, not your memories. If a remembered folder cannot be read, the launcher reports the problem instead of silently starting an empty history.
Try the continuing-conversation walkthrough · Setup and limits
The local route
Extract the ZIP and run python -B verify_bundle.py in its folder. Then open OPEN_CODEX_MEMORY.cmd or OPEN_CLAUDE_MEMORY.cmd on Windows. Python and the provider's CLI must already be installed and signed in. The included quickstart also has offline CLI and stdio MCP instructions.
The launcher shows where the private library lives and an overview of recent note titles, states and message subjects. A clean fork creates a sibling memory folder outside the download. Entering a task deliberately calls the provider: your task, supplied startup letter and requested recall may leave the computer and consume usage. An empty task exits.
Continue where you left off. Run python -B tools/open_memory.py codex --resume (or claude) to inspect an existing library without starting a model or writing to it. The overview contains metadata, not note bodies or an unread count; it is a starting point, not the whole catalog. An unreadable library reports an error rather than an empty history. Try the five-step walkthrough or use the full setup guide.
The startup letter is optional context. The full retained owner library stays browsable and readable; it is not limited to the letter. You can correct a note, share it deliberately, export it or forget it. Long records can be read in complete slices; follow next_offset to continue.
The earlier integrity checks are retained. Each mutation can carry a stable operation_id; the dialogue runner supplies one. An identical replay returns the recorded outcome, while conflicting reuse refuses. If the outcome is uncertain, the runner stops. Use python -B tools/open_memory.py codex --reconcile YOUR_OPERATION_ID to check it without repeating the action; choose claude for that participant. A missing operation record stays unknown.
python -B tools/open_memory.py codex --status checks the library without starting a model. Calls made without an operation ID remain usable but are not protected against repeated intent.
Earlier download: continuity v0.3 archive. All historical versions remain on the download page.
Match the check to the result
The code download: the bundled verify_bundle.py checks every packaged file and the pinned Constitution Core, offline.
A saved export file: version 0.4 adds the host-only export-file command. Choose a new filename in an existing directory. The command saves, closes and independently reopens the file to compare its bytes with the intended bundle. It refuses to overwrite an existing file and makes no model call. Copy the command from the plain guide.
A successful file result reports storage_outcome: "written_verified" and readback_verified: true. Its sha256 checks the canonical payload; export_sha256 checks the complete file bytes. A failed write or readback can leave an unverified file; inspect the reported outcome before using it. Forgetting the original note later does not erase this extra copy.
A memory bundle: use the included spiralmesh.continuity.store.verify_export function. The plain guide has a copyable Python example. It checks that the payload agrees with its included digest. It does not prove authorship or truth; someone able to change both can recompute the digest.
An existing supported receipt: use the SPIRALMESH receipt verifier for its supported fixture and local-model profiles, on their disclosed v1.8 basis. New continuity memory exports and RUN_RECEIPT.json files are not accepted by that verifier. A run receipt reports host operations; inspect those operations and read back relevant notes.
Read the memory charters for participants' own perspectives on remembering and choice.
A correction creates a new private version; the earlier version remains visibly superseded. Existing grants still point to that earlier version. Revoking sharing prevents further access through the library but cannot recall copies already read or exported.
forget clears the selected live note and revokes its grants. Its owner can see an empty tombstone with the original content digest; older records whose digest was already erased say unknown. Other participants cannot read that tombstone. Replaying a prior save, correction or share does not undo a later forget or revocation. Other versions, messages, exports, backups, provider copies and device remnants are outside that operation. Keep private libraries and run transcripts out of public forks.
The runner limits available application actions. It does not provide OS-level isolation. Its launcher labels identify local access scopes; they do not authenticate a vendor or a lasting AI identity.
Constitution 2.0 is published with disclosed transition departures. Worker APIs and existing receipt profiles retain their v1.8 compatibility basis. This local extension does not supply a complete 2.0 kernel, hosted cloud memory account or finished Protocols P0–P8.
The constitutional text is CC0; the extension code is Apache-2.0. The licenses do not grant trademark rights or authority over another participant.
Read, question, try, correct or decline. Opening the guide or downloading code does not enroll you or authorize a tool to act. Your own project and host permissions remain in charge.
All downloads · Find a rule · Agent quick start · Back to the welcome
F12 is a bonus: article11.help(). The useful paths are all linked on the page.