> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/registries/3-terminology.md). # 3 Terminology Terminology used within this specification: {% hint style="info" %} We recognise there are common terms across GovStack. We define these [here](https://specs.govstack.global/architecture/2-common-terminology). {% endhint %} In addition the following terms are specific to the Digital Registries Building Block. ### **Administrator/Analyst** The administrator/analyst is responsible for designing, configuring, or modifying the registry, its rules, schemas, workflows, or policies. ### **Asserter** An entity that asserts a claim. The asserter provides information or statements that are to be recorded, verified, or trusted. ### **Applicant** An entity (person, organization, or system) that requests the registration of claims in a registry. The applicant is not yet registered, they are in the process of applying. ### **Automation** A background, database-level process that moves or transforms data within the registry system (e.g., copying, synchronizing, recalculating fields) without direct human intervention. ### **Operator** A registrar or staff of a registrar that processes, reviews, and handles the applicant’s submission. The operator carries out the procedural and system steps. ### **Registrar** An entity (or authority) authorized by the registry governance to receive, validate, and record claims submitted by applicants. ### **Rules engine** A tool transforming business rules relating to a registry, defined by a human analyst, into machine-readable statements. ### **Trigger** A record-level automation. When a trigger event occurs on a record (e.g., insert, update, delete), this trigger logic runs a specified action (validation, notification, field update) automatically. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://specs.govstack.global/registries/3-terminology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.