Skip to content

Readme.snapshot

Why Particles

  • The Particles standard defines the particle schema, the source-corpus model, the extraction protocol, and a small set of operations (deposit, extract, query, lint, review, reindex). p-21f11766 (confidence 0.70)
  • The Particles particle store is a derived view that can be rebuilt from the corpus by re-running extractors. p-3f71ca93 (confidence 0.70)
  • Particles claim-granularity particles are natural-language sentences paired with structured metadata for confidence, provenance, and uncertainty. p-80f9b726 (confidence 0.70)
  • Particles can answer queries that require finding relevant claims about a subject and synthesising them with provenance intact. p-a5a42fe0 (confidence 0.70)
  • Most Retrieval-Augmented Generation (RAG) systems re-derive knowledge from scratch on every query. p-ba8cfa2c (confidence 0.70)
  • Particles is a minimal interoperable substrate for claim-granularity agent knowledge — narrower than a formal-ontology knowledge graph (RDF/SPARQL) and more structured than augmented markdown. p-cb10c54c (confidence 0.70)
  • Corpus-entry-level provenance is required at Core in Particles. p-d3fd6c56 (confidence 0.70)
  • The Subject store is the standard's catalogue of real-world entities against which particles are indexed. p-7931228a (confidence 0.66)

Design rationale

  • When APPEND_ONLY falls back to MUTABLE handling, PROVENANCE_STALE is set on particles whose provenance.location falls within the changed regions. p-0296afc0 (confidence 0.70)
  • The Source Corpus is an append-only archive of all materials from which particles have been or may be extracted. p-8476c2ac (confidence 0.70)
  • When as_of is set to a past instant T, Query evaluates the store on the assertion-time axis — what the store believed at T — never world-time validity. p-8767ad66 (confidence 0.70)
  • When two sources or two principals disagree in Particles, the conflict-resolution ladder surfaces an INCONSISTENCY record for review instead of silently overwriting either side. p-9cf41a46 (confidence 0.70)
  • effective_confidence is computed at query time, not stored. p-c3b1cef6 (confidence 0.70)
  • Contestedness MUST be computed at read time and never stored. p-cea0186c (confidence 0.70)
  • Trust weighting, recency decay, and the as-of instant are applied per observer at query time in Particles, never baked into the stored record. p-d0d41702 (confidence 0.70)
  • confidence.value is stored immutably, as calibrated at creation time. p-f1ced6c4 (confidence 0.70)
  • The Lint operation performs periodic health checks for contradictions, stale claims, orphan pages, and missing cross-references. p-f35e1dee (confidence 0.70)

Architecture

  • Core operations: Deposit, Extract, Query, Lint, Reindex, Review (§9). p-a4bdde07 (confidence 0.76)
  • The Core SDK exposes a clean Python API and a CLI. p-3bd3740c (confidence 0.70)
  • A Particles deployment has two distinct storage subsystems: a Source Corpus store and a Particle store. p-5a941962 (confidence 0.70)
  • Corpus entries and snapshot metadata are stored in queryable form, either relational or document store. p-8f670063 (confidence 0.70)
  • The extraction pipeline selects the most specific registered extractor whose applicability specification matches the source; the general extractor is used if and only if no domain-specific extractor applies. p-ac28fba0 (confidence 0.70)
  • The Source Corpus store is an append-only object store (local filesystem, S3-compatible, or content-addressed store). p-cb1cd190 (confidence 0.70)
  • Each of the six operations maps to a CLI subcommand and a POST API endpoint in the reference SDK. p-e5639e78 (confidence 0.70)