Particles documentation

The guides for running and extending the Particles reference implementation. The project's front door, the whitepaper, the technical specification, and the normative schema artifacts live at linkedparticles.org.

Particles stores an AI system's knowledge as a git-like ledger of claims: every belief is sourced, dated, and confidence-scored, nothing is overwritten, and trust and staleness are applied when the store is read, never written into the stored claim. If that framing is new, start with Why Particles?.

Agent memory

One command wires a store into Claude Code as managed memory the agent does not control: harvested into the corpus at session end, pushed back into the context window trust-ranked and contradiction-flagged at session start, and audited on first run against the memory you already have.

particles init claude-code

Claude Code memory walks through the hooks, the MEMORY.md projection, and the first-run audit. By default one store serves every project on the machine; that guide's One store serves every project says what that means and how to narrow it.

Where to go

• User guide: deposit, extract, query, lint, export. Start at getting started.
• Operator guide: running a store long-term (configuration, tuning, review, consolidation, troubleshooting).
• Plugin-author guide: adding an extractor, an exporter, or a benchmark suite.
• CLI: the workflow-oriented command index, with the full command reference beside it.
• API reference: generated from the source docstrings across both distributions, the schema models and extraction from the Client layer, the corpus, store, and operations from the Engine.
• HTTP API: every operation as a typed endpoint, rendered from the committed OpenAPI contract.

The standard

This SDK is the reference implementation of an open, implementation-independent specification. The normative documents and artifacts are published separately, so a second implementation has something to conform to:

• Whitepaper and technical specification
• Vocabulary: every term at the identifier it resolves to
• particle.schema.json, context.jsonld, and the SHACL shapes, served at the identifiers published particles carry
• The standard's repository

The three repositories

Repository	What it is
particles-standard	The standard: spec prose, normative artifacts, conformance fixtures
particles-engine-py	This repository: the Engine and its surfaces (linkedparticles)
particles-core-py	The store-free Client layer (linkedparticles-core)