Atoms
An atom is a typed fact extracted from a work-defining document
(contract, SOW, scope, brief, specification, MSA, change order,
requirements document, RFP, anything that defines what's being
delivered) or operational record. The eleven kinds are: clause, fact,
definition, entity, quantity, reference, negotiation, meta_document,
document, obligation, evidence.
Why typed
Plain prose lets too many things mean too many things. By insisting
that every meaningful claim becomes an atom of a specific kind with a
schema-validated payload, Nebula turns the document into a queryable
graph. The Brain tab traverses that graph; the Verify engine relies on
it.
Source quotes
Every atom carries a sourceQuote plus the page and char range where
it came from. Click any atom to see the exact text Nebula used; this
is what makes the engine's reasoning auditable.
Provenance is not garnish
The reason for source quotes is not transparency for its own sake.
It's so a third party (a court, an auditor, a counterparty) can verify
that the atom Nebula is acting on is actually present in the document
both parties signed. Without that, the engines reduce to "trust the
software".
Cross links
/docs/concepts/chain: how atoms become anchored proofs/docs/engines/extract: how atoms get created from documents/docs/concepts/reputation: how anchored events feed reliability