The Glossary

One name per concept (the law, Part 4, v4.0.0): every concept the canon owns, its one name, its definition in the canon's own words, the Part that defines it, and the synonyms retired. The canon owns the names; a deployment binds only its mechanism, spoken as a qualifier. Rendered from canon/GLOSSARY.yaml on every build.

Name	Definition	Part	Retired synonyms
Settled	The epistemic stamp of a law with its receipts cited.	header
Provisional	The epistemic stamp of a law ratified with no receipts yet, its first receipt's due condition stated inline; taught, drilled and examinable everywhere except the day-60 certification verdict.	header
The three layers	Every well-managed domain has the same three layers, ontology, SOP and data, and when work feels messy, unnamed and untrackable, one or more of them is missing.	1
Ontology	Layer 1, the nouns: what exists, its fields, its legal states, its identity scheme (how instances are named), and the declared places where it lives.	1
SOP	Layer 2, the verbs: what may be done to the nouns, by whom, on what clock.	1
Data	Layer 3, today's instances, written in the layer-1 vocabulary.	1
Noun	An entity the ontology names, with its fields, its legal states and its declared identity scheme; every noun lives in exactly one home concern and is used elsewhere by typed reference, never by copy.	1
Identity scheme	A noun is not ontologized until its instances carry a declared identity scheme, and two schemes are legal: a minted token, or a natural key where the date or slot already individuates.	1
Code	A minted, human-speakable token where instances must be cited across time, people or surfaces: minted at birth, permanent, never reused, never renumbered, the audit trail's spine; bare inside its zone, qualified at egress.	1
Zone	One code namespace per organization or logical entity in an operator's declared zone registry, homed with the operator; a zone may be reserved for the cost of a row while carrying no deployment.	1
Home	The one concern whose spine declares a noun and whose owner stewards it; every other concern uses the noun by typed reference, never by copy, keeping its own facts in its own register keyed by the home identity.	1
Re-homing	Stewardship moves, identity never does: when a noun's true witness turns out to live elsewhere, an induction-class act, on ruling and with no clock, in two shapes, custodial and jurisdictional.	1
Custodial re-homing	Re-homing that moves stewardship and address; the full six steps bind, and the vacated address becomes a permanent one-hop alias.	1
Jurisdictional re-homing	Re-homing that changes only the governing spine; slug, codes and custody survive, so the alias and handover steps are satisfied vacuously rather than skipped.	1
Meta-concern	The concern whose territory is the concern estate itself: the register of registers, where a ruling spanning concerns lives and the OKG is homed; the last meta level, ever.	1	meta-domain
The two loops	Enforcement and gardening are not layers but feedback loops, closing at different speeds over the three layers, carried by ceremonies like any other process.	1.25
Enforcement	The fast loop: closes the runtime against the design, its machine half authored into layers 1 and 2 as gates and invariants, its human half the Inspect ceremony walking the exception set.	1.25
Gardening	The slow loop: closes the design against reality, asking whether the schema and SOPs still fit the drifted world; the only loop allowed to reopen layers 1 and 2.	1.25
Reification	In a platform that implements this model, the definitions themselves are records: layers 1 and 2 live as rows in meta-registers, so the slow loop runs as ordinary register operations.	1.25
Spec	The organ that owns intent (names, legal states, contracts, clocks-as-commitments, decisions, and why): a dossier, a charter, the canon; implementations conform to it, and a divergence is a bug or an amendment candidate.	1.25
Implementation	The organs (code, tools, configured platforms) that own mechanism, the exact validation, retry logic and plumbing, which the spec never restates; conformance is checked in the consumer's context.	1.25
Config-as-data	Where one definition must exist in both prose and machine form, both consumers compile from one machine-readable source instead of maintaining the pair by hand.	1.25
Declaration	The authored file: a spine's one authored source, from which every surface renders, its version minted at the write path and never typed.	1.25
Spine	The content of a declaration, a concern's governing spec: scope sentence, birth story, jobs, ontology declarations, SOP suite, organ index, decisions and version; the organ-holder, never an organ.	2.5
Dossier	The rendered page of a spine, generated from its declaration and never hand-edited.	1.25
Author	One holding a recorded, scoped grant to define layer-1 nouns and layer-2 verbs, minted by the apprenticeship or by the practicum's day-60 certification.	1.75
Operator	One who runs an inherited stack, writing rows, running ceremonies and walking exceptions, which need no license.	1.75
Coverage walk	A periodic audit ceremony that enumerates the territory, marks which domains are committed, and consciously accepts the unmanaged remainder; nouns are never minted there, and an accepted gap is a decision where a silent one is a risk.	1.75
Authority register	Where an authoring grant lands: who may author, in which concern's scope, granted when, on what receipt.	1.75
Apprenticeship	A reviewed first authoring, where the unlicensed author walks the door with a licensed one same-day and the pass mints permanent self-serve, so the license dissolves itself author by author.	1.75
The three skills	The layers are anatomy, the skill is physiology: diagnosis (seeing an incident as a missing noun), design taste (which ontology, not just an ontology), and the two loops.	2
Job	A question a named hirer brings to a structure on a cadence, whose answer changes a decision, written in the hirer's own words; jobs then structures, never structures then jobs.	2
The jobs admission standard	A job enters the enumeration only by stating four things: who hires it, on what cadence it fires, which decision its answer changes, and its failure cost when unserved.	2
Hirer	Whoever consumes the answer to change a decision; supply never wears the hirer cell, and condition shape is legal only for a genuine machine consumer.	4
The two doors	Ontologize has two doors: the pain door, a live domain entered through recurring pain, and the JTBD door, a greenfield domain entered through job enumeration; the doors also bound the loop.	2
Pain door	The catechism's door into Ontologize: a live domain, entered through recurring pain.	2	incident door
JTBD door	The greenfield door into Ontologize: enumerate the jobs first, then derive the nouns and fields from them.	2	survey door
The done-test	Any ask, from any hirer, classifies by one question, when would this be done: never means a concern, a date or end-state a project, when the number hits X the goal layer, a misleading shape a project with a recurrence flip.	2
Declare	To declare a domain is to author its declaration through a door: the jobs admitted, the nouns ontologized, the verbs processized, the organs indexed, the past inducted.	2
Birth	The day a declaration enters; the spine's birth story records why, and the orphan rule asks at birth.	2
Committed	The state that results from a declaration entering: a domain the estate manages from then on, with a walk, which is to say a concern.	2
Concern	A domain committed to management: one owner, a closed noun and verb vocabulary on one spine page, two or more admitted jobs with different hirers, rulable divergences; the deployments' word, adopted at v4.0.0.	2	committed domain
Domain	Raw territory: a domain of work, uncommitted, which the coverage walk lists and only a door admits; a concern is a domain plus the commitment to manage it.	2
Category	Too big to be a concern: no single owner, no closable noun-set; its spine would be an org chart, and that axis belongs to responsibility, not territory.	2
Outcome	Not a concern: a KPI axis; you do not walk an outcome, you walk the programs that move it, and outcomes belong to the goal layer.	2
The four grain tests	One accountable owner; a closed noun-and-verb vocabulary that fits one spine page; two or more admitted jobs with different named hirers; and a spine divergence that yields a question a human can rule on.	2
The capacity loop	Every concern requires a live, drained walk: a conservation invariant matching concerns to judgment capacity, never rationing codification, steered by two receipts-derived meters, debt aging and disposition drain.	2	capacity guard
The goal layer	Where an outcome refused as a concern lives, above the concerns: objectives as closable battles, linked to concerns only through lead measures whose readings come from the concerns' standing organs.	2
Objective	A closable battle: from X to Y by when, one accountable owner, ending won, missed or abandoned, where a concern is never done.	2
Lead measure	A predictive, influenceable, one-owner bar linking an objective to a concern, whose readings come from that concern's standing organs, never from fresh bookkeeping.	2
The three species	The done-test's answers name three species of managed thing, each with its own anatomy: a concern (an engine, never done), a project (bounded work with a pre-registered definition of done), and an objective (a number by when).	2
Project	Bounded work with a pre-registered definition of done: a noun of the work-management concern, with identity, a scope sentence, one owner, a clock, what it serves, its work on a board, and a close in exactly one of done, abandoned or converted.	2
Work-management concern	The concern that owns the work noun and its register, every project's lifecycle and never a project's substance; a project's one home.	2	work-management domain
Definition of done	The pre-registered end state that separates a project from a concern; done means it was met, never the calendar, and it is frozen once the project closes.	2
Serves	The question asked of a project at declaration, never at capture, with two answers: a concern (the project builds or amends one of its organs, or is its induction) or loose, declared; only silence is forbidden.	2
Loose, declared	Personal or exploratory work, said out loud; its home is the work-management concern by construction, its board that concern's own, its walk that concern's ceremony.	2
Workstream	The grain that says 'for X to do Y': one owner, one purpose, the unit of delegation, where ownership is fixed for a stream of work.	2
Task	The grain that says 'the next move is': one ball, who, what, since when.	2
Hard clock	A project clock the world set and enforces, a filing, an expiry: it moves only when the world's date moves, and missing it is a miss; deadline-grade.	2
Target clock	A project clock of self-set pacing, the appetite: it moves by a recorded shift, and every move is a counted slip; walk-grade.	2
Shift	The only way a project's baseline (its definition of done, its clock and its kind) moves: a recorded change carrying old, new and a reason, never silent.	2
Rest	A project hidden until a date or a condition, then returning, neither open nor terminal to the walk; a rest never outruns a hard clock.	2
The five verbs	The layers projected into what an author-operator does to a concern: ontologize and processize are authoring acts, log, inspect and garden are runtime functions the deployment is audited on.	2.5
Ontologize	Name the nouns: entities, fields, legal states, declared places (layer 1, authoring).	2.5
Processize	Define the verbs: SOPs, ceremonies, cadences, owners, including the two meta-ceremonies (layer 2, authoring).	2.5
Log	Every event lands as a row, as it happens (layer 3, runtime).	2.5
Inspect	Walk the exception set the machine surfaces and disposition every item; the fast loop's human half, and it means exceptions only.	2.5
Garden	Amend the ontology and SOPs as reality pushes back; the slow loop, and the only runtime verb allowed to reopen layers 1 and 2.	2.5
Concern-owned SOP	A process belonging to exactly one concern: authored in that concern's spine, one owner, the ownership invariant strict.	2.5	domain-owned SOP
Ceremony	A cross-concern convenor: it walks segments that several concerns each own, so it is owned at the level that spans what it convenes and never forced into a single concern.	2.5
Scope sentence	What this concern is and when to open it; one sentence, the standfirst every surface leads with.	2.5
Birth story	Why the concern exists and what forced it into being; the why that pinned decisions cannot carry.	2.5
Jobs	The spine's reified jobs, the admission-standard table: each row a hirer's question with its cadence, the decision it changes and its failure cost; never finished at birth.	2.5
Ontology declarations	The spine's nouns, legal states, identity schemes and their typed links: the noun graph, never a noun list, because a concern is a pipeline and pipeline-ness is edges.	2.5
Typed link	An edge of the noun graph, a domain verb in the hirer's vocabulary (a Payslip PAYS a Report); a cross-concern link names the foreign home, and its encoding is a binding.	2.5
SOP suite	The spine's verbs, each named, clocked and owned, with its kind: SOP, ceremony or induction.	2.5
Organ index	The spine's typed pointers to the organs that implement it, mechanism never restated: a free typed entry of name, type, binding and address, never a closed list of engine kinds.	2.5
Decisions	The spine's pinned decisions, rendered by reference per the jurisdiction law: each with its date, its ruling and its status, standing or superseded.	2.5
Version	The spine's version, minted at the write path whenever the declaration changes, never typed.	2.5
Orphan	An organ without a spine home; at build time the question which concern this organ serves is mandatory, and only the silent no-answer is forbidden.	2.5
Workshop	A build explicitly experimental and uncataloged, earning structure by receipt; the third legal answer to the orphan rule's question.	2.5
Induction	The one-time act carrying a concern's unstructured past into the standing process's steady state: an owner and a declared end state, but no clock; a second induction means enforcement failed.	2.5
Backfill	Induction that enriches the past from retained ground truth, statements and archives, so it becomes rows under the new ontology.	2.5
Freeze	Induction by a dated legacy line: the past stays readable but unconverted, and the new capability stays quiet behind the line, which is correct, not a gap.	2.5
Bankruptcy	Induction that declares the past handled as a class without item-level processing; legal only when reversible by construction, archived, never deleted, the corpus retained.	2.5
Exception	What escapes the gates and reaches a human: overdue, blocked, stale ball, no next action, failed assertion; a register's open rows, and a recurring exception is information about the system, not about the work.	2.5
The five dispositions	Every walked item ends in exactly one recorded disposition: do, delegate, defer, drop or decide.	2.5
Walk	The Inspect verb over one exception set, on one clock, by one walker; the register's walk set says what is open, the ladder says who reads it and when.	2.5
The walk ladder	A concern normally has several walks, nested by altitude, and an exception climbs exactly one level at a time, by aging past the lower walk's clock or by recurring; recurrence routes to Garden.	2.5
Floor walk	The walker closest to the work on the fastest clock: it reads the raw open rows and discharges what it can, do and delegate.	2.5
Register walk	One level up on a slower clock: it reads only what the floor could not discharge, a row that aged past the floor walk's clock or recurred.	2.5
Top walk	A line in a ceremony, derived from the registers beneath it and never hand-kept; its exception set is what escalated plus the liveness of the walks below, so the executive walks the walks, never the work.	2.5
Altitude	The clock and the exception set of a walk, never seniority: one person may hold two rungs, and a machine may hold the lowest.	2.5
Dead walk	A register that has not moved for its walk's clock, itself an exception the walk above reads.	2.5
The five presences	A corridor screen, never a gate, for any live register: ontologized, processized, logging, inspected, gardened; five yeses is a screen passed, not a certificate.	2.5
Organ	A declared place: a standing artifact that one concern declares for exactly one job, that the concern's processes operate on their clocks, and that the spine's organ index names.	2.75
Type	The organ's one job for its concern, its role never its mechanism, from the canon's closed set of nine; derived and foreign are qualifiers, never types.	2.75
Binding	The mechanism that implements a type in one deployment, named as a qualifier on the canon's word and recorded in that deployment's own declarations, amended freely on its own clock.	2.75
Kind	A deployment's mechanism word for an organ (a tracker, a dossier-table, a mini-app, a dashboard): a qualifier on the canon's name, never the name; the spelling of a binding.	2.75
Channel	Substrate: a communication container, type-promiscuous by nature, never an organ and never taking a type, though an organ may bind into one.	2.75
Register	The concern's records: identified rows, mutable cells, exceptions walked.	2.75
Ledger	Append-only receipts: proof that events ran, never mutated.	2.75
Court	Where balls sit, visible at a glance.	2.75
Board	A bounded body of work in flight: tasks, definition of done, closable.	2.75
Surface	The screen a human opens; view-only is a qualifier, never a noun.	2.75
Door	The typed write path: Gate-mode enforcement embodied.	2.75
Index	Derived views recomputed on events, never kept by hand.	2.75
Corpus	Retained raw ground truth for recompute and backfill.	2.75
Scoreboard	The goal layer's readings with standings, derived from registers, never testimony.	2.75
The register's walk set	A register declares which of its states are terminal and which are resting; its open rows, neither, are the exceptions its walk exists for, and a register declaring no terminal state shows as a loud gap.	2.75
Terminal	An author-declared bit on a state: the row is closed.	2.75
Resting	An author-declared bit on a state: settled but not closed, a standing ruling, a recorded receipt.	2.75
Open	A row in a state neither terminal nor resting: the exceptions a register's walk exists for.	2.75
Address	Where an organ is, declared in the organ index: a table's slug, a URL, a workflow's name; the index declares where and what, never how the organ is doing.	2.75
Liveness	How an organ is doing, the last receipt, the open rows, a clock gone stale: derived by the consumer from the organ at its address, recomputed on read, never declared.	2.75
Receipt door	The declared liveness of an organ the consumer cannot read, another estate's register or a foreign system; the one exception to derived liveness, at the estate boundary.	2.75
Knowledge routes by role	Knowledge is a role, never a type, a spine component, or a noun; it routes by one question, what decision does it change and does it have an identity, into the types the canon already has.	2.75
Docket	What a ceremony walks in one sitting, derived and bound as an index, never hand-kept; a docket empty for a quarter merges away.	2.75
The catechism	The pain door's six questions, run every time a pain recurs twice; write the answers down, they are the design.	3
Clock	When a verb runs: a cadence with an owner, authored once, in the spine or in the scheduler the spine names, never both; 'sometime' is not a clock.	3
The seven fitness tests	A proposed structure passes review only if every field changes a decision, every instance has a declared identity, compliance is silent and exceptions loud, pull surfaces die, a good ceremony shrinks, and it passes the instruction and absence tests.	4
The instruction test	After the structure exists, can the manager direct a day's work in one line; if not, layer 1 is too coarse.	4
The absence test	Does the structure run correctly for two weeks with the manager on holiday; if not, layer 2 has no real clock or no real owner.	4
Qualifier	A variant is a qualifier on an existing noun, never a new noun, until receipts earn the split.	4
Flip condition	The pre-registered observable event that reopens a rejected or deferred build, with the build then designed for the failing case and sized by its evidence; a deferral without one is a door slammed.	4
The speech test	A word an agent or a human reads or says while working (a tool name, a declaration key, a sentence, a screen label) is a name and must be the canon's; a word only a developer reads in code is mechanism and may stay.	4
Sitting	A ruling session on the canon or on a spine: an author proposes and the owner rules.	4
The four enforcement roles	Four strengths of agents as enforcement, in rising order: observe, notice, gate, scribe; agents enforce shape, humans judge substance.	5
Observe	An agent attends the ceremony or reads the channel and lints outputs against the ontology after the fact; violations still happen but become loud, eventually.	5
Notice	An agent watches the clock and the write path live, a ceremony that did not fire, a row gone illegal, a due date crossed, surfaced the same day, to the owner, once, loudly.	5
Gate	The agent is the write path: work enters through a typed door that stamps the required fields and cannot produce an illegal row.	5
Scribe	The agent produces the artifact natively in the right shape, pre-briefing the standup or filing the register row from the conversation, so compliance becomes moot.	5
Ball	Who owes what, since when, held by whom, verified against ground truth before anyone chases; a decision without a ball is a wish with a witness.	5
Receipt	Proof that an event ran, cited by row code: 'done' plus the code is a verifiable claim, 'done' alone an assertion; structure and laws are earned by receipt, never by scenario.	1
OKG	The Operating Knowledge Graph: a deployment's one derived view of everything it manages, condensed out of the declared spines on every read, never authored, never stored as truth; the meta-concern's index organ.	5
OKG Map	The OKG's human window, a surface; the Park is a lens on it.	5	Map tab, concern map
Lookup door	The OKG's door: a word in, every citable handle out, with its pulse; what makes a negative about the estate a lookup, never a guess.	5
The ten-word mantra	Name it, clock it, write it, guard it, garden it: name, clock and write are the three layers, guard and garden the two loops.	6