The temporal vocabulary every Oto ontology rests on, and the one class every fact cites: Document.
2 classes, 3 relations, 1 rules, 0 actions. oto registry add https://github.com/Cynergis/oto-registry, oto ontology add oto-core, then oto init --ontology oto-core.
| Class | What it is | The question it answers | Why it exists |
|---|---|---|---|
| Document | A source document in the corpus: the file a fact cites, with its own date. | Where is this written down? | Every fact needs a checkable source with its own date, and the source is a file in the corpus. |
| Action | Something that can be done about an entity, described the way an MCP server describes a tool and bound to the graph. Oto lists it; the caller invokes it; the recorded run is evidence. | What can be done about this, and how? | The binding between an entity, the tool that acts on it, its inputs, its credentials by name and its preconditions is otherwise tribal knowledge in an agent's prompt; as a fact it is versioned, reviewed and shared. Oto never invokes it. |
| Relation | From | To | Meaning |
|---|---|---|---|
cites | Document | Document | This document refers to that one, so a fact traced to it can be traced one step further. |
acts_on | Action | The entity a recorded run of this action read or changed. | |
executed_by | Action | Who is accountable for invoking this action: a team, never a person. |
