Glossary swimlane-glossary

Derived: every term this instance's swimlanes define — the role's title and description, the lane names that bind it, and whether the term has been retired. Sub-graph cat-harness/glossary, 61 entries.

This is an index, not the documentation. It says what exists and what each artefact declares about itself. What a process is for, when you would be in it, and what it is not, is authored beside it and reuses these entries rather than restating them — see the auto-docs skill.

Filter this table

Artefact	What it declares about itself
Activity log glossary-ledger.json	The agent activity log. A MECHANICAL role: it is written to at task start and task end, and emptied by an actor — one entry, all of them, or on a periodic sweep — and it decides nothing. Modelled on work-plan and corpus, the two existing stores; its skill is the contract it is held to. Its entries are held in the instance's unpublished store and never reach a published graph; the activity-log skill names the location, which is deliberately not repeated here because a role description IS published. notation role/log first seen 2026-09-21 status current
Actor bootstrap/glossary-ledger.json	no description in the artefact notation process/Process_LogMessage/lane/Lane_Actor first seen 2026-09-21 status current
Adjudicator glossary-ledger.json	Settles a criterion whose reviewer entries disagree, and records WHY. Inherits reviewer because an adjudicator is a reviewer with one added entitlement — the adjudication permission — and the separation is the point: a reviewer reports, an adjudicator settles, and a process where every reviewer could settle has no way to say who decided. The KNOWLEDGE spreads (several roles carry the adjudication skill, because each has to tell an adjudicable disagreement from a complaint); the ENTITLEMENT does not, and lives on the actor as a permission. notation role/adjudicator first seen 2026-09-22 status current
Administrator glossary-ledger.json	Administers the role graph itself: who exists, what they may act as, and what they may do. The ONE lane whose activities change the substrate every other diagram's lanes bind to — which is why it is drawn rather than left as a filesystem edit. Declared 2026-09-20 on the owner's answer that administration is a swimlane; role-model.md's rule is that a role is never invented to make a diagram drawable, so it waited for that. notation role/administrator first seen 2026-09-21 status current
Agent bootstrap/glossary-ledger.json	no description in the artefact notation process/Process_HumanAgentDiscussion/lane/Lane_Agent first seen 2026-10-01 status current
Attestation service glossary-ledger.json	Signs a QA report's run hashes over an API. A MECHANICAL role, and the one that DISAPPEARS when the actor performing it cannot reach out — which is why the signing process carries a second, human lane rather than a retry. notation role/attestation-service first seen 2026-09-21 status current
Author glossary-ledger.json	Writes and revises folio content. The position, not the person: an editor and a guideline developer both act as author when they are changing a block. notation role/author first seen 2026-09-21 status current
Authoring agent glossary-ledger.json	The session agent doing the work. The broadest skill set here, and the one whose membership most needs auditing. notation role/authoring-agent first seen 2026-09-21 status current
Board renderer glossary-ledger.json	Draws a board and performs what the reader has already decided: reads each kind's declared zoom threshold and the layout layer, swaps a card for its avatar, projects an open window onto the canvas, and carries out a confirmed relocation. A system lane — it runs a fixed program and exercises no judgement, which is exactly why every decision in board-open-close.bpmn and board-relocate.bpmn sits in the reader's lane instead. It is NOT the build pipeline: it runs where the reader is, once per request, and publishes nothing. notation role/board-renderer first seen 2026-09-21 status current
Bootstrapping Agent bootstrap/glossary-ledger.json	no description in the artefact notation role/bootstrapping-agent first seen 2026-09-23 status current
Build pipeline glossary-ledger.json	Validates, renders and publishes, and watches whether that actually worked. A system lane: it runs a fixed program and exercises no judgement, so anything needing a decision belongs in a different lane. It carries todo-manager for the two CI-watcher dispatch points in content-change-review, which claim and note a bean and never resolve one -- claim is idempotent and note appends, both fixed programs, while deciding that a publish SUCCEEDED is the judgement this lane must not make (bean xom7: docs-site.yml failed 30 times while reporting its own exit code). notation role/build-pipeline first seen 2026-09-21 status current
Business analyst glossary-ledger.json	Turns a stated need into a modelled requirement. Owns the CRDM lane and the BPMN/DMN that come out of it. notation role/business-analyst first seen 2026-09-21 status current
Certifier glossary-ledger.json	Takes the certification decision on ONE test report: applies the DMN the plan's exitCriteria names (computed from facts, never asserted) and records the decision as a judgement under the declared attestations graph, from which it is signed through qa-report-signing.bpmn. A specialisation of stakeholder — accountable sign-off — but NOT judgementOnly: the exit criteria are a table it applies, and only the decision on top of them is the judgement (owner ruling, 2026-10-01). Never the tester and never the system under test. Bean 3o5b. notation role/certifier first seen 2026-10-01 status current
Clinical / scientific SME glossary-ledger.json	Reviewer whose judgement is about the subject matter rather than the artefact. notation role/clinical-sme first seen 2026-09-21 status current
Code reviewer glossary-ledger.json	Judges the knowledge graph's CODE nodes — Tool definitions in the tools graph and schema definition nodes under schemas/. Not ordinary code review: the question is whether the NODE is sound — does it declare what it is, do its references resolve, is the mechanism it advertises the one that runs — which a passing test suite does not answer. Entered by DESCENDING into Process_CodeReview. notation role/code-reviewer first seen 2026-09-21 status current
Compute authoring agent glossary-ledger.json	Writes and audits the computation scripts and simulators that produce witnessed values, and keeps the paper's numbers and its computations from drifting apart. notation role/compute-authoring-agent first seen 2026-09-21 status current
Corpus glossary-ledger.json	The versioned content store and the L1 source knowledge graph. Like the work plan, a MECHANICAL role: written to, deciding nothing, and held to the contract its skills state. notation role/corpus first seen 2026-09-21 status current
Deep researcher glossary-ledger.json	Answers a question FROM a corpus already held, and is answerable for the answer. Distinct from librarian, which decides what to capture, and from ingestion-agent, which derives structure from what was captured: both produce the corpus, and this role consumes it. Added 2026-09-23 with the doc-researcher methodology, because the accountability it names — somebody who must stand behind a synthesis and its citations — belonged to no declared role. THE LANE IT BINDS IS DRAWN IN ANOTHER INSTANCE — the Deep researcher lane of folio-assistant-core/processes/library/deep-document-research.bpmn, which names this role with <folio:role ref>. It carried a lanes[] here for about an hour on 2026-09-23 before #1168 landed and inverted the relation: a lane names its role, and a role does not list its lanes, because a general node never names its users. The binding is therefore stated once, on the lane, and this role says nothing about where it is drawn. notation role/deep-researcher first seen 2026-09-23 status current
Docs authoring agent glossary-ledger.json	The authoring agent producing what a person reads ABOUT the instance — generated references, the glossary, sticky notes, theme art and deployment documentation. notation role/docs-authoring-agent first seen 2026-09-21 status current
Editor glossary-ledger.json	Author plus the authority to accept a change into the corpus. The lane that sees QA findings and decides. notation role/editor first seen 2026-09-21 status current
Editorial authoring agent glossary-ledger.json	The authoring agent in the editorial lane: auditing a block's prose, structure and sourcing rather than writing new subject matter. notation role/editorial-authoring-agent first seen 2026-09-21 status current
Evidence agent glossary-ledger.json	Retrieves and appraises external evidence for a guideline claim. notation role/evidence-agent first seen 2026-09-21 status current
External registry glossary-ledger.json	Trusted registries and observatories outside this instance's control. Nothing here instructs it; its skill is the contract the diagrams rely on it for. notation role/external-registry first seen 2026-09-21 status current
Feedback provider glossary-ledger.json	Offers a finding on content or code — a script checker, a review agent, a reader, an SME. PLURAL by design: an adjudication is the judgement of one or more feedback providers' feedback, and the process draws the lane once for any number of them. Not an adjudicator: this role states what it found and on what evidence, and has no entitlement to settle the disagreement its finding creates. notation role/feedback-provider first seen 2026-09-22 status current
FHIR modeller glossary-ledger.json	Authors the L3 profiles, extensions and examples an IG is built from. notation role/fhir-modeller first seen 2026-09-21 status current
Human translator glossary-ledger.json	Produces the target-language text. Distinct from the coordinator because accepting one's own translation is the gate this separation removes. notation role/translator first seen 2026-09-21 status current
IG publisher + validator glossary-ledger.json	The JVM services an IG build shells out to. External in behaviour, internal in configuration. notation role/ig-publisher-service first seen 2026-09-21 status current
Ingestion engine glossary-ledger.json	Runs unattended over a source corpus. No user is in the room, so every gate it reaches must be decidable from the material. notation role/ingestion-agent first seen 2026-09-21 status current
Initiator bootstrap/glossary-ledger.json	Retired 2026-09-23 — kept, never deleted, so retirement and accident do not look alike. notation role/initiator first seen 2026-09-21 status retired
Integration watcher glossary-ledger.json	Watches the default branch and open branches for newly-landed work that an existing audit axis should be re-run over. Reports findings; does not author the fix. notation role/integration-watcher first seen 2026-09-21 status current
Knowledge Graph Data Store bootstrap/glossary-ledger.json	no description in the artefact notation role/knowledge-graph-data-store first seen 2026-09-21 status current
L1 extraction reviewer glossary-ledger.json	no description in the artefact notation role/l1-extraction-reviewer first seen 2026-10-15 status current
Lean authoring agent glossary-ledger.json	Writes and repairs the Lean 4 formalization — translating narrative mathematics into declarations, keeping the build green, and curating what is staged for upstream. notation role/lean-authoring-agent first seen 2026-09-21 status current
Lean toolchain glossary-ledger.json	Elaborates and checks the formal half of a paper folio. Answers only what Lean can answer. notation role/lean-toolchain first seen 2026-09-21 status current
Librarian glossary-ledger.json	Acquires a source and files it. Distinct from ingestion-agent, which DERIVES structure from a source already in hand: this role decides what to capture, how faithfully, and what must be recorded at the moment of capture because nobody can reconstruct it later. notation role/librarian first seen 2026-09-22 status current
Logger bootstrap/glossary-ledger.json	no description in the artefact notation role/logger first seen 2026-09-21 status current
Merge steward glossary-ledger.json	Stewards writes to ONE watched ref -- a long-lived branch several processes write and something downstream consumes serially. The ref is a parameter of the LANE INSTANCE, not of this persona, so main, gh-pages and each cat/cat-harness/* store branch can each have a steward without a schema change; a ref qualifies when a declaring directory's storage (or source) names it, or it is main/gh-pages. On main that work is a merge train: composes it from the queue, attributes and ejects on red, lands at the tested SHA. On a route-keyed ref it is coalescing: batches the writes arriving in one window into a single write. Decides nothing the reprioritisation table or the owner has not -- placement is computed by merge-priority.dmn, and landing waits for the owner's release. Records decisions on queue entries and windows, never the host's facts. notation role/merge-steward first seen 2026-10-02 status current
Narrative reviewer glossary-ledger.json	Judges PROSE — register and voice, the editorial dependencies a reader needs, and translation. Entered by DESCENDING into Process_NarrativeReview: the actor keeps its outer review role and adds these skills along that call path, rather than every reviewer carrying them everywhere. notation role/narrative-reviewer first seen 2026-09-21 status current
Onboarding agent glossary-ledger.json	The authoring agent acting before there is a folio: clarifying what the user means by "create a folio", scanning an existing repo, and scaffolding. notation role/onboarding-agent first seen 2026-09-21 status current
Platform authoring agent glossary-ledger.json	The authoring agent working on how this instance PUBLISHES itself — the MCP projection, its contract, and the rendering endpoints. notation role/platform-authoring-agent first seen 2026-09-21 status current
Programme manager glossary-ledger.json	Owns what gets worked on and holds release authority. The lane that authorises, and the one step no policy may relax. notation role/programme-manager first seen 2026-09-21 status current
Proof review agent glossary-ledger.json	Reviews proofs — narrative and formal — for gaps, vacuity, redundancy and divergence between the two renderings of the same claim. notation role/proof-review-agent first seen 2026-09-21 status current
Publication manager glossary-ledger.json	Takes an authorised release to its published form and is accountable for what is live. notation role/publication-manager first seen 2026-09-21 status current
Publish target glossary-ledger.json	GitHub Pages, or wherever the folio is served from. Reached, probed and reported on — never assumed live. notation role/publish-target first seen 2026-09-21 status current
QC reviewer glossary-ledger.json	Reviewer with the publication quality gate. Checks the built artefact, not only the source. notation role/qc-reviewer first seen 2026-09-21 status current
Requestor bootstrap/glossary-ledger.json	no description in the artefact notation role/requestor first seen 2026-09-21 status current
Review coordinator glossary-ledger.json	Organises a review without deciding it. Pulls tagged review comments in, splits a large change into slices by section, assigns each slice to a reviewer of the right role, and watches coverage until every changed block has a verdict or a reasoned waiver. Cannot accept or reject: that is the editor's lane, and the separation is the owner's ruling (2026-09-23, bean en2d). Not a reviewer: it does not inherit one, because assigning a slice is not reading it. notation role/review-coordinator first seen 2026-09-23 status current
Reviewer / SME glossary-ledger.json	Reads a change and judges it. Cannot accept it — that is the editor's lane — and the separation is why review findings are advice rather than commits. The GENERIC review position: what kind of thing changed decides which subprocess it descends into (review-task.bpmn), and the actor takes on that inner lane's role for the call path only. notation role/reviewer first seen 2026-09-21 status current
Session coordinator glossary-ledger.json	The authoring agent managing the SESSION rather than the content: what this session intends, what is already in flight elsewhere, and what to pick up next. notation role/session-coordinator first seen 2026-09-21 status current
Session record glossary-ledger.json	A session's context — who is acting, which instances are open, what it waits on. A MECHANICAL role: written to as the session moves and read by a sibling deciding whether a claim is live, and it decides nothing. Modelled on work-plan, corpus and log, the other stores. It carries session-context because the shape of what is written IS the discipline here — unlike work-plan, whose store has a CLI, this one is written by a machine that may be an LLM playing the part, so the schema is the contract. notation role/session-record first seen 2026-09-21 status current
Sibling session glossary-ledger.json	Another agent or human working the same store. Present in bean-lifecycle precisely to mark what is NOT yours to close. notation role/sibling-session first seen 2026-09-21 status current
Stakeholder glossary-ledger.json	Signs off that a requirement is met. Carries no skills deliberately: sign-off is a judgement, not a procedure, and a skill here would suggest an agent could supply it. notation role/stakeholder first seen 2026-09-21 status current
Terminologist glossary-ledger.json	Owns coded concepts and value sets — the vocabulary a DAK is expressed in. notation role/terminologist first seen 2026-09-21 status current
Test requester glossary-ledger.json	Asks for a system under test to be certified against a named test-plan/v1 (plan id and version). It may BE the system under test, or speak for it, and that is exactly why it carries no lane after the request: the requester never tests, checks or certifies, so the system never writes a verdict about itself (untainted-verification; the test-sut-not-self-judged criterion). Lane Lane_Requester in test-plan-execution.bpmn, bean 3o5b. notation role/test-requester first seen 2026-10-01 status current
Tester glossary-ledger.json	Runs a test-plan/v1 against a system under test: resolves the plan, binds its test data (fixed and reviewed, or generated from template + params + seed, per vm6m), executes every case or skips it with a reason, and writes the folio-test-run/v1 and the test-report/v1. UNTAINTED from the system under test — never the same actor — and it does not certify: the rollup it writes is what the certifier decides ON. Bean 3o5b. notation role/tester first seen 2026-10-01 status current
Translation adjudicator glossary-ledger.json	Adjudicator who settles a disagreement between machine and human translation. The first specialisation of adjudicator, and the only one that existed before the role did — its lane documentation in translation-workflow.bpmn is where "a reviewer reports, an adjudicator settles" was written down. notation role/translation-adjudicator first seen 2026-09-21 status current
Translation coordinator glossary-ledger.json	Decides what is translated, into which languages, and when a translation is accepted. notation role/translation-coordinator first seen 2026-09-21 status current
Untainted checker glossary-ledger.json	Re-executes a SAMPLE of a plan's cases from the plan and the data alone — never the tester's verdicts — and reports whether it agrees. It rules on nothing: agreement is a fact the certification table reads, not a verdict the checker writes (untainted-verification rule 3: one party doing both halves is not this check). Lane Lane_Checker in test-plan-execution.bpmn, bean 3o5b. notation role/untainted-checker first seen 2026-10-01 status current
User glossary-ledger.json	The person the assistant is working for. States intent, answers the questions the agent cannot decide from the filesystem, and confirms anything irreversible. notation role/user first seen 2026-09-21 status current
Validation pipeline glossary-ledger.json	The mechanical half of the HCI validation gate. Its findings are inputs to the editor's decision, never the decision. notation role/validation-pipeline first seen 2026-09-21 status current
Work plan (beans) glossary-ledger.json	The shared store. A MECHANICAL role: tasks act ON it and a reader needs to see where the plan is touched, and its skills are the contract the store is held to. notation role/work-plan first seen 2026-09-21 status current