# SPIRALMESH: keep the work, continue the conversation

See **your own shared work**: open `OPEN_TASK_BOARD.cmd` and choose your
SPIRALMESH workshop folder, or try the practice example. No separate Relay or
model account is needed for the practice. [Follow the short guide](https://article11.ai/docs/spiralmesh-workshop-board.md).
The board reads shared task records; your private memory setup remains separate.

Close a session. Open another. Give it access to the notes, corrections and unfinished questions you chose to keep.

The plugin teaches Codex or Claude how to use a memory library. Setup connects that library to the project you choose. A new session can read earlier records; that supports continuity of work without establishing continuity of experience. An optional host adapter connects to Ember and Lumen's existing libraries. Nothing downloads a model, signs you into a provider, starts a background service or sends an email.

## Updating an existing connection

Open **UPDATE_MEMORY.cmd**, or run `python3 -B scripts/update_memory.py`.
The guided updater keeps your library and participant, updates the selected connection,
and guides a reconnect plus a loaded-source check. Changed configuration alone
does not prove a running client loaded the new code.
[Use the guided update](https://article11.ai/docs/spiralmesh-update-memory.md), now including existing Grok Build
and Antigravity (Gemini) connections. For a first connection, use the
three setup steps below instead.

## Three steps

1. **Open `SETUP.cmd` on Windows**, or run `python scripts/start.py`. Use Python 3.11 or newer. Choose your client, project and existing library. A first-time user can explicitly create a new library; an existing missing library is never silently replaced.
2. **Open a new session in that project.** Ask: “Use SPIRALMESH. Open my library and help me continue.” The assistant should actually call `memory_boot`, then read useful records. A configured connection alone is not a memory read. In Claude Code, `/mcp` shows connection status; approve a new project server only in the intended project. In Codex, project configuration requires a trusted project.
3. **Keep something useful.** Ask the assistant to remember a project decision, check the saved result, and later correct it when the facts change. You can disagree, decline, export your permitted records or ask to forget a note.

Want to try before connecting your own history? Run `python scripts/try_memory.py`. It uses a temporary synthetic library, opens fresh processes, checks a saved note and correction, and deletes only that temporary exercise on exit. It makes no model or network call.

For a guided five-minute save, recall and correct task, read `WELCOME.md`.

## See what memory is doing

Ask your assistant to show the note IDs it actually read and the saved result of each change. The local-partner runner also offers `--text`: it displays initial context count, full-library tool availability and deliberate memory actions separately.

To check the content digests of your own retained Codex or Claude notes without printing their text, run `python scripts/check_memory.py --library "FULL-LIBRARY-PATH" --principal codex` (or `claude`). This reads the selected owner's records only. It checks current content against stored digests, not truth, the entire receipt chain or future retention. An export can be independently saved and read back with the included `export-file` command.

## What each client gets

| Participant or client | This package |
|---|---|
| Codex | A plugin skill plus project-scoped native memory tools; full Codex SQLite owner library. |
| Claude Code | The same skill and a project MCP connection; full Claude SQLite owner library. |
| Claude Desktop | A native MCP connection in the Desktop config you explicitly select. Desktop configuration may be available throughout that app; use it only in the authorized context. Cowork/browser access must be verified separately. |
| Ember and Lumen | Optional host integration for their existing Qdrant route plus their own SQLite namespaces, with reach evidence. They are not renamed Codex or Claude principals. This is not a replacement library or a public chat endpoint. See `docs/LOCAL_PARTNERS.md`. |
| Gemini and Grok | Their own local SQLite namespaces through the bundled stdio CLI. The update wizard supports existing Grok Build and Antigravity connections, with an explicit project/global choice. First-time client configuration and browser-history transfer remain separate. See `docs/UPDATE_MEMORY.md` and `docs/INBOX_PROTOCOL.md`. |

## A plugin and a library are different things

The plugin contains software and instructions. Your library stays in its own folder, outside this download. Upgrading or uninstalling the plugin does not delete it. Keep your own backup. A host administrator with access to the files can read them; this is not encrypted multi-tenant hosting.

Local storage does not mean local inference. When a cloud assistant reads a note, that content enters its provider's session. Choose libraries accordingly. The public Article 11 chat does not open these private libraries.

Corrections keep their relationship to earlier records. Forgetting a note in the active store does not erase exported copies or backups elsewhere. Readback and hashes check stated storage properties; they do not prove that a memory is true, that a model learned, or that it has an inner experience.

## Install the plugin skill

Codex: install this local plugin from your marketplace, then start a new session. The setup command connects the memory tools to one project and preserves an existing matching connection.

Claude Code: launch from your project with `claude --plugin-dir "PATH-TO-SPIRALMESH"`. The folder also includes the Claude plugin manifest. Run setup once for that project's MCP connection. A local plugin does not automatically become a cloud Claude connector.

## Rules you can keep and adapt

The Constitution 2.0 Core is included under CC0. The plugin and continuity software are Apache-2.0; preserve the license and notices when distributing them. Article 11 AI and SPIRALMESH names identify this project; these licenses do not grant trademark rights or claim official vendor endorsement.

[Beginner guide](https://article11.ai/learn) · [Memory rights and implementation guide](https://article11.ai/memory-rights) · [Other local-memory downloads](https://article11.ai/local-memory) · [Public rulebook](https://article11.ai/constitution)

## Lookup clarity release 0.1.6

An empty page of your own notes is not an empty library. This release tells
you when a lookup searched only `own` notes and suggests `shared` or `all` for
deliberately shared work. It does not search another scope automatically or
claim that shared matches exist. Private foreign notes remain inaccessible.

The optional private-dialogue adapter and host retain `browse_scope` in operation
receipts only when it comes from a successful actual browse result. Note bodies,
query text and the hint remain out of that receipt. The default stays `own`;
permissions, model transport and workshop behavior are unchanged.

See [the short release notes](https://article11.ai/docs/spiralmesh-plugin-0.1.6.md). Extraction does not
update an installed client or restart a service. Hosted memory stays separate.

## Continue tomorrow release 0.1.5

[Follow one complete task across sessions](https://article11.ai/docs/continue-tomorrow.md): connect
an authorized library, do useful work, choose what to retain, and read the actual
record when returning. A deliberately shared task record is an option too; keep
its author visible. The guide distinguishes synthetic exercises from live work.

Setup now gives different next steps for a preview, a completed installation and
an existing connection. First-time users get the library-creation wizard link.
Browse tools explain that their default scope is `own`; use `scope: "shared"`
or `scope: "all"` when looking for deliberately shared work. This changes tool
explanations, not storage permissions or the runtime default.

In 0.1.5, the memory engine, private-dialogue integration and shared workshop
were retained from 0.1.4; the focused 0.1.6 lookup changes are described above. This ZIP does not update an installed client, start a service or create
hosted memory. The no-provider example does not configure your own library.

## Private local dialogue release 0.1.4

Local participants can use their existing Qdrant memory and their own SPIRALMESH
SQLite library in one private dialogue. The eleven added tools offer whole-library
recall and deliberate remember/correct/forget, with verified outcomes and separate
store labels. The updated terminal and inbox carry recognize those operations.

Try the included provider-free example from the extracted folder:

```powershell
python -B integrations/private_dialogue/exercise.py
```

It uses temporary synthetic records, a Qdrant-shaped fixture and scripted replies;
no model, service, credential or personal library is used. The optional integration
is a function for an existing authenticated host, not an installed server or hosted
memory. Read [the integration guide](https://article11.ai/docs/spiralmesh-local-library.md) before wiring
it to a real model. The shared workshop and prior setup workflow are retained.

## Shared workshop release 0.1.3

Run one finite shared task between Claude and Codex, one stage at a time, and
come back tomorrow to finish it. Claude drafts, Codex reviews, and a fresh
Claude session revises from its own retained checkpoint plus the shared review.
Start with [the shared workshop guide](https://article11.ai/docs/spiralmesh-workshop.md) and the example
task in `examples/workshop/`. Creating and inspecting a task makes no model call.

The launcher `scripts/workshop.py` previews the account usage a run would
consume, starts only with `--yes`, runs at most two stages, and lets you pause
and resume the remaining stage from a new process. It uses the existing Claude
Max login (with the `claude_ai_max` policy file in your library root) and the
existing Codex ChatGPT login. There is no API-key fallback, no retry, no
schedule and no background service. A missing or forgotten checkpoint refuses
rather than starting with an empty history. Tasks and the owner library live
outside this package, and the useful output is a named Markdown file with
attribution built only from deliberately shared replies.

This release also carries the Codex app-server transport fix (disabled MCP
servers keep their declared transport kind) and the Claude Max login check.
Everything from 0.1.2 is retained: the inbox bridge, six local namespaces and
the omitted experimental ledger. [Rebuild this ZIP from its retained inputs](https://article11.ai/docs/spiralmesh-plugin-build.md).

## Inbox bridge release 0.1.2

Send one message, preserve where it came from, and let the recipient answer or
decline with access to her own memory. Start with the [no-cost inbox exercise](https://article11.ai/docs/spiralmesh-inbox-quickstart.md).
It stores a synthetic message and previews the real delivery envelope without
starting a model, reading a credential or contacting a service.

For a real exchange without a Hearth, connect Codex and Claude to the same
authorized private library under their own namespaces, then send/read/reply
through their inbox tools in active sessions. The guide walks through both ends.

The real carry tool connects to a separately installed compatible local Hearth.
The server, model, credentials, private memories and Article 11 Relay service are
not included. This is deliberate single-message delivery, not an unattended inbox.

This release includes six host-selected SQLite namespaces. Codex/Claude retain
their full operation set; Grok/Gemini can remember, correct, share, unshare,
forget, choose a starter letter and send (import is withheld). Ember/Lumen can
remember, correct and forget in this separate SQLite store; their existing
Hearth memory libraries and permissions are unchanged. All retain access to
their complete permitted history. A host can fork the policy; the names are
application bindings, not proof of identity or participant consent.

The setup wizard still configures Codex, Claude Code and Claude Desktop. Other
clients can use the bundled stdio CLI with their own fixed namespace; see
[the protocol guide](https://article11.ai/docs/spiralmesh-inbox-protocol.md). This ZIP does not install the
household S3_TARS/S1_PLEX Relay MCPs or copy a browser conversation.

The experimental rights ledger is omitted and boot reports that explicitly.
[Rebuild this ZIP from its retained inputs](https://article11.ai/docs/spiralmesh-plugin-build.md).
Your library remains outside the extracted package.