Skip to content

The specification

Particles is an open specification, built for independent implementation: the schema, the operations semantics, the conformance contract, and the machine-readable artifacts are published independently of the reference implementation, so a second implementation has something precise to conform to. Today there is one implementation — the reference engine — and the specification is a working draft; we'll call it a standard when someone else has implemented it too.

Status: whitepaper and technical specification v2.2 (draft) · conformance profile 1.1 · reference implementation on PyPI.

The documents

The machine-readable artifacts

Served at the identifiers published data carries, byte-identical to the copies in the repository (a deploy-time check re-verifies this daily):

The three repositories

  • The specification


    The whitepaper, the technical specification, the normative schema and SHACL artifacts, and the conformance fixtures — independent of any one implementation. This site is built from it.

    particles-standard →

  • The engine


    The reference implementation's state-holding half: corpus, extraction pipeline, belief store, the query/lint/review operations, and the API, CLI, MCP and web surfaces.

    particles-engine-py →

  • The client library


    The store-free half: schema models with their confidence invariants, candidate extraction, conformance validation, and the interchange codec. Depend on this to produce or validate particles.

    particles-core-py →

Reference

  • SDK documentation — user, operator, and plugin-author guides, the CLI reference, and the HTTP API contract
  • Security and trust — the reporting policy and the disclosed caveats
  • Contributing — how changes to the specification are proposed and land