Three graphs
Each fact keeps where it came from. Memory points back to the run evidence behind a fact rather than copying it, and a fact supported by more independent sources carries more weight.
How a turn reads memory
- The map. Every root turn’s instructions include a map of the organization’s world graph: what kinds of things it holds and how many.
- Graph reads. Model steps of the root workflow whose output admits calls are offered GraphResolve, GraphExpand and GraphSource. A workflow’s Budget.MemoryProbes caps how many reads a turn makes.
- Nested work reads none. A called workflow, an agent or a debater touches no graph: it is offered no graph reads and writes none.
Settings
Four settings belong to the organization. Workflows do not declare them and people cannot override them. The organization’s owner reads and changes them with GET and PATCH /organization/preferences, under workflow.
Erasure
Deleting a run erases its flow graph. A person’s user graph is deleted with their account. Facts in the world graph stay as long as their own evidence and corrections allow; a deleted run’s contribution to a fact’s weight remains, without the run it came from.