Glossary

One name and one definition per concept (principle 25). 95 concepts, rendered from canon/GLOSSARY.yaml on every build.

Name	Definition	Principle
Absence test	A structure runs correctly for two weeks with its manager away.	18
Agent-run walk	The rung where only exceptions arrive.	21
Ball	Something someone owes: who holds it, since when, to do exactly what.	20
Birth story	Why a concern exists, in its spine.	15
Board	An organ of bounded work in flight.	16
Ceremony	A sitting that convenes several concerns' work, owned at the level that spans them.	17
Clock	A project's date: hard (the world's; deadline-grade) or target (self-set; walk-grade, each move a counted slip).	6
Code	An instance's speakable, never-reused identity, minted at creation.	13
Committee ontology	An ontology grounded in neither a real pain nor real jobs.	11
Concern	Work that keeps running: a pipeline someone commits to manage.	4
Coordination surface	How many people, agents and handoffs must work together; what decides whether structure pays.	3
Corpus	An organ of ground truth kept for recomputing.	16
Court	Where every ball sits, visible at a glance; an organ type.	20
Coverage walk	A periodic walk that maps the territory and accepts on the record what stays unmanaged.	12
Declaration	The file a concern is written in, once.	15
Definition of done	What a project must achieve to close as done, set at birth.	6
Disposition	How a walked item ends: do, delegate, defer, drop or decide.	18
Door	An organ that is the typed way to write.	16
Dossier	The page rendered from a concern's declaration.	15
Enforcement	The loop that keeps the work matching the design.	2
Find before you create	Look up what already holds an ask before making anything new.	4
First walk	A new concern's first inspection, where it is reviewed and sized.	12
Five-step order	Make it less dumb, delete it, simplify it, accelerate it, automate it, in that order.	22
Flip condition	The observable event that reopens a refused build.	26
Floor walk	The walk closest to the work, over the raw open items.	19
Four factors	What a project is born with: its room, the project, its WorkBook and its walk.	6
Garden	The fifth verb: change the design when reality drifts.	2
Gardening	The loop that keeps the design matching reality; the only loop that may change the ontology and the process.	2
Gate	The enforcement role where the agent is the write path.	28
Glossary	This file: every concept's one name and definition.	25
Grade	A job's attention grade: deadline (a miss is a miss) or walk (it ages on a walk).	10
Guard	A check, gate or rule, carrying its incident, one meter, and the reading that would retire it.	22
Hirer	The person, by name, who consumes a job's answer.	10
Holder	The one person or agent holding an issue's next move.	5
Home concern	The one concern a noun lives in; every other concern uses it by reference.	14
Implementation	What owns mechanism, conforming to the spec.	31
Index	An organ derived from others, never kept by hand.	16
Induction	The one-time act that carries a concern's past in: backfill, freeze or bankruptcy.	15
Initiative	A goal above projects: one owner, at most one number from X to Y, an update on its own rhythm.	8
Inspect	The fourth verb: walk the exceptions.	2
Issue	A piece of work that ends, with one holder and a one-line done-when.	4
Job	A hirer's question a concern exists to answer, with its cadence, the decision it changes and its failure cost.	10
JTBD door	The way into structure for something new: enumerate the jobs first.	11
Kind	The role a job's question plays: an obligation, a lookup, an assurance or a recommendation.	10
Lead team	The team that leads a project and walks it on its weekly walk; it can change after birth.	6
Ledger	An organ of append-only receipts.	16
Log	The third verb: every event lands as a record.	2
Loose	A project's answer to what it serves when no concern holds the work yet.	6
Meta-concern	The concern that manages the concerns and holds rulings that span them.	14
Natural key	A declared identity taken from the instance itself instead of a minted code.	13
Notice	The rung where nothing arrives until a threshold breaks; also the enforcement role of a same-day alarm.	21
Observe	The enforcement role that checks records after the fact.	28
OKG Map	The OKG's screen.	30
Ontologize	The first verb: name the nouns.	2
Ontology	The first layer: the nouns, their fields, legal states and identity, and where they live.	2
Operating Knowledge Graph	The OKG: one derived graph of everything a company manages, asked before guessing.	30
Organ	A declared place a concern keeps for one job, typed by that job.	16
Pain door	The way into structure through a recurring pain.	11
Parent issue	An issue split into sub-issues, for the pieces that stand apart.	4
Process	The second layer: the verbs, who does them, on what clock.	2
Processize	The second verb: write the verbs, who does them and on what clock.	2
Project	Work that ends, a feature with several pieces, as in Linear; defined by its definition of done.	4
Pull	The rung that waits to be opened.	21
Push	The rung that arrives on a clock.	21
Qualifier	A word on a name for a mechanism or a variant, never the name itself.	16
Re-homing	Moving a noun's stewardship to another concern; its identity never moves.	14
Reading	How a job's answer is measured, derived from the concern's records and never typed in; one a person records is a claim until checked.	10
Records	The third layer: what happened, written in the ontology's words.	2
Recurring issue	A person's work on a clock, owned by the concern it serves.	7
Register	An organ of identified rows, walked for exceptions.	16
Register walk	The walk above the floor, over what aged past the floor's clock.	19
Resting	A register state that settles a row without closing it: a standing ruling, a recorded receipt.	18
Scribe	The enforcement role where the agent produces the record in shape.	28
Shared team	A team for a shared service with its own work, such as testing; its piece of a project is an issue inside that project, and its piece of a single issue a sub-issue under it.	5
Shift	A recorded change to a project's definition or clock, with its reason.	6
Sign-off	An approval, as a step on an issue.	7
SOP	A process that belongs to one concern alone.	17
Spec	What owns intent: names, legal states, commitments, the why.	31
Speech test	A word anyone reads or says while working must be the standard's; a word only a developer reads in code may stay.	25
Spine	The content of a concern's declaration: scope, birth story, jobs, ontology, processes, organs, decisions, version.	15
Sub-issue	A piece of a parent issue; it may sit on a team other than its parent's, which walks it.	5
Surface	An organ that is a screen people open.	16
Team	An area of work and the people and agents who do it; never a concern, never a reporting line.	5
Terminal	A register state that closes a row.	18
Three seats	Where people's attention goes: setting goals, ruling, and escalations; everything else is the machine's.	1
Top walk	One line derived from the walks below: what escalated, and which walks went quiet.	19
Triage	Where every ask lands first, to be accepted, merged or declined with a reason.	5
Triager	The one who disposes a team's triage.	5
Typed link	A link between two nouns, named by a verb.	15
Walk	Going through one list of exceptions, on one clock, by one walker, until every item has a disposition.	19
Walker	The one who runs a walk, declared once by a person; below the top, by default an agent, whose every disposition is logged.	19
WorkBook	A project's one page, where its decisions live.	6
Workflow	The binding of one verb to one runner; it belongs to its verb's concern.	16
Zone	A company's code in the group's zone registry, carried by codes outside their company.	13
Zone registry	The group's one list of zones, held by the group rather than any one company.	13