Skip to content

Vocabulary

These terms carry specific meaning throughout the system and should be treated as design tokens in their own right. One term carries one meaning; where English gives a word several senses, each sense is named separately below and the docs use the qualified form. The style guide states the rule.

The graph

TermMeaning
yidamThe chosen form — this kind of repository, whose git history is the knowledge rather than a record kept about it. See what yidam is
corpusThe living knowledge graph — all domain nodes and their edges
catalogProvenance layer — one node per external data source
nodeA single file; one concept, relation, artifact node, or open question
edgeA markdown link between two nodes — directional
corpus nodeAn authored or generated domain knowledge claim
catalog nodeA source descriptor (dataset, paper, API)
artifact nodeA corpus node describing a thing produced or found in the domain. Distinct from an artifact, which is bytes in a vault
claimA single assertion inside a node, carrying an inline confidence marker
gateThe checks a corpus must pass before a commit counts — graph-check, lint, and the commit-vocabulary rule. What makes an edge a commitment rather than a hyperlink
traversalWalking edges from a starting node to answer a query, as opposed to retrieving by similarity
driftDivergence between the corpus and something derived from it — a stale index, an aged-out catalog source, a regenerated block no longer matching its source
pathsThe typed paths yidam query --paths <from> <to> prints between two nodes, shortest first. Each is a query that returns <to>. Unrelated to cohort --paths, which names repositories

The ontology

TermMeaning
ontologyThe corpus's schema layer: what kinds of things exist in this domain and how they may connect. Declared in .ont.yml files, confirmed during the bootstrap dialogue
classOne kind of thing, defined in <class>.ont.yml. Declares the properties its instances carry and the edges they may bear
instanceOne node of a class, stored at <class>/<instance>.yml
BFOBasic Formal Ontology — foundational alignment organized around the continuant/occurrent axis
UFOUnified Foundational Ontology — foundational alignment organized around kinds, roles, and relators
foundational typeThe BFO or UFO type assigned to an ontology class; encoded in foundational_type: in .ont.yml, carrying ontology:, type:, and an optional iri:
alignment IRIThe iri: inside foundational_type: — the identifier that type has in BFO or gUFO. Optional; export-rdf emits it as skos:exactMatch. Replaces the retired bfo_anchor:

Governance

TermMeaning
agentA participant (human or AI) who commits to the graph
electorA recognized sangha participant; maintains a ma/* branch
sanghaThe collective of all participants; the governance layer
positionOne elector's current understanding, carried on their ma/<elector> branch. Positions are expected to diverge
rigpaClear seeing — a settled collective understanding; a named branch rigpa/<evolution>
maVoice, position — one elector's working branch ma/<name>
proposeA branch propose/<head> of commits yidam propose drafted, awaiting a person. Named in plain English deliberately: unlike ma/ and rigpa/ it carries no standing
evolutionOne settled synthesis of positions, named and carried on a rigpa/<evolution> branch. The unit a position is measured against
resolutionThe act of synthesizing divergent positions into an evolution, under the constitution

Layers and lifecycle

TermMeaning
preludeInherited yidam infrastructure: identity, graph model, constitution, conduct norms
samudayaArising — pre-bootstrap seed material; consumed at genesis
sadhanaThe scaffold template layer; also consumed at genesis
kutenThe form a practice takes — what a corpus's work is for. A profile under .yidam/.vendor/prelude/kuten/, selected with its revision in .yidam/decisions/kuten.yml. Binds nobody
tonpaThe one who shows — a corpus built by another sangha, installed under .yidam/tonpa/ as a dependency. Cited, never edited
genesis commitThe first commit in a derived repo; names domain, seeds ontology
phaseA bounded unit of agent inquiry: Investigation, Extraction, Synthesis, or Assessment
derivationA repository bootstrapped from this template. Its corpus is its own; the prelude is inherited
gatherOne question put to every installed tonpa peer, declared in .yidam/gathers/<name>.toml. The answers land as one cited question node on a propose/* branch. Nothing merges
cohortA set of derivations read together by yidam cohort, to ask how each norm of their inherited prelude fared. A report about the prelude, not about a corpus
accretionHow fast a corpus adds nodes per authored commit. cohort tests RFC-0028's two candidates for measuring it — a trailing window and a decay curve — against every member's history

Cluster runs

TermMeaning
admitThe gate before a cluster run: yidam cluster admit decides whether anything is owed. Its record says admitted either way, and a run with nothing owed submits no step
landerThe one pod that may update a ref, yidam cluster land. It reads the commit's class off the commit, then pushes to the branch or to propose/*. See cluster runs

The domain computer

TermMeaning
connectorAn external-facing async adapter that fetches data into the corpus
calculatorA pure, deterministic domain computation
packA context bundle built to a token budget from a query's answer, reporting what did not fit

Storage and distribution

TermMeaning
artifactBytes too large, too derived, or too licensed to live in git. Held in a vault, referenced by a committed pointer. Distinct from an artifact node
vaultThe store an artifact lives in. Git holds the record of which bytes and which vault; the vault holds the bytes
storeThe backing service a vault is configured against — S3, a local directory, or another supported target
bundleA .yiz archive publishing a corpus for another repository to consume
knowledge artifactA derived repository as a whole — the sense used in "living knowledge artifacts"

Sources

TermMeaning
identifier locationA catalog location of kind: identifier, valued scheme:local-id — doi:10.1167/tvst.8.5.14. It names a source by what it is, not where it is
source packA directory declaring how identifier schemes resolve to addresses, and how to fetch them. Authored in .yidam/sources/ or pinned in prelude_sources. See source packs
transformA .glu file a pack's scheme names, describe or extract. It runs in the calculator arm's closed prelude over the response the scheme resolves to
readingWhat an extract transform, or a PDF's text, takes from an artifact. catalog-extract caches it and records it under the artifact's readings:

Claim confidence markers

Inline tags that annotate epistemic status within a corpus node:

MarkerMeaning
[verified]Supported by a committed primary source
[inference]A reasonable conclusion from verified facts; not directly witnessed
[open]A live question; unknown, contested, or under investigation