Expand description
What an edit did to a graph, said before anybody runs it.
revision puts a commit somewhere it can be imported from, snapshot
asks a subprocess what the graph there is called, and findings reads
what comparing two of those answers said. Around them, what a question was:
moves and journal hold it, trials runs it, walk and
data read the store back.
Nothing here holds a graph. A graph is Python, it exists for the length of
the probe’s process, and what crosses back is a snapshot::Snapshot.
Modules§
- bench
- Everything a command needs standing up before it can ask anything.
- data
- What data sits under each version, and what belongs to none of them.
- findings
- What an edit did, read rather than decided.
- journal
- What somebody said about a commit: a verdict, a note, a reason for pruning.
- moves
- The reasoning: questions, hypotheses, attempts, findings and decisions.
- reasoning
- The reasoning, read back: every move with what it stands at, and what folds.
- revision
- A commit, put somewhere it can be imported from.
- snapshot
- What a graph was, at one commit. The probe’s answer, typed.
- trials
- What was run with a version: the trials, their states and their curves.
- walk
- A line of exploration, as data.