ReferenceDraft ยท not yet verified
Glossary
The words these docs use, each with one meaning.
| Term | Meaning |
|---|---|
| Adjustment | A later record linked to an earlier one that was right and has since changed. See adjustments. |
| Agent | The AI system that calls the tools. |
| Agent profile | A named set of lanes a call may read and write: a home lane, and others. The caller names it on a call; a call that names none runs under the engine's default agent profile. See agent profiles. |
| Authority | The level a record was labelled with when written. From highest to lowest: human correction, human confirmation, documentary, conversational, system inference. The engine does not rank by it. See authority. |
| Archive | The durable copy of everything the engine knows, kept in S3-compatible object storage when it is turned on. The database can be rebuilt from it. See the archive. |
| Correction | A statement of the truth, pinned to a record that was wrong. See corrections. |
| Edge property | A label:value pair on a record, such as org:Acme. Records that share one are joined by it: one N-ary edge touching every record that carries it. See edge properties. |
| Edge Property Graph (EPG) | The graph that records and their edge properties form, held in PostgreSQL with no separate graph store. See the EPG. |
| eMemory | Short for Everything Memory. |
| Engine | One running instance of Everything Memory. |
| Exchange | The runtime activity of a mesh: what crosses between peered engines, and how each applies it. See the exchange. |
| Folder Intake | The service, in its own compose file, that watches a folder and writes each file and each part of its text as records. See documents and files. |
| Label | The first half of a property: the person in person:Sarah. |
| Lane | The partitioning mechanism: every record lives in exactly one lane, and access and vocabulary are decided per lane; a lane's records cross the mesh with its policy, when that policy is shared and accepted. Swim lane is the familiar picture. See lanes. |
| MCP | Model Context Protocol, the protocol agents use to call the tools. |
| Mesh | Engines connected to one another. Peering sets it up; exchange is what crosses while it runs. See the mesh. |
| Peer | Another engine this one is peered with. |
| Peering | The setup of a mesh: pairing two engines and deciding what each offers and takes. See the mesh. |
| Policy | The document that declares lanes, source types, labels and agent profiles. See policies. |
| Source record | The unit stored: any content a caller writes, kept word for word with its edge properties, lane, source type, authority and provenance. Called a record after first use, and SR in tool text. See source records. |
| Source type | The declared kind of a record, on a lane in a policy. It sets the record's authority and limits its labels, label values and content shape. See source types. |
| Tag | A word or value an extractor plugin returned for a record, kept in the record's tag index and read by retrieval. A tag is not an edge property: e_read and e_property do not list it, and it is not exchanged with peers or written to the archive. See the pipeline and its plugins. |
| Tombstone | A kept marker of a deletion on this engine. It is never sent to peers; an undelete lifts it. See deleting a record. |
| Update | A new version of a record's own content or properties. Earlier versions are kept in that record's ledger. |
| Value | The second half of a property: the Sarah in person:Sarah. |