# Keywords > The keywords fall into categories by the job they do in a line, and every keyword is uppercase because that is the form the model has seen most in code. Page: PAG · Keywords Canonical: https://banes-lab.com/pag/keywords#keyword-ontology The keywords fall into categories by the job they do in a line, and every keyword is uppercase because that is the form the model has seen most in code. Every keyword outside the prepositions grounds to a record in the ontology's reasoning face, so the vocabulary is derived rather than invented, and the lists below are read from the grammar's own records. ### Semantic operations A document names one of the [semantic operations](https://banes-lab.com/pag/guide/tool-invocation.md) for every external effect. One adapter per harness maps each operation to a tool, and the short tool forms an adapter accepts are its aliases, never the grammar's vocabulary. `DISCOVER_RESOURCES` Find resources by pattern · the adapter maps GLOB to it `DISCOVER_RESOURCES "" INTO ` `READ_RESOURCE` Read one resource · the adapter maps READ to it `READ_RESOURCE INTO ` `SEARCH_CONTENT` Search content for a term · the adapter maps GREP to it `SEARCH_CONTENT FOR INTO ` `ANALYZE_CONTENT` Analyze content against criteria `ANALYZE_CONTENT AGAINST INTO ` `EXTRACT_FACTS` Isolate fields from content, preserving its meaning `EXTRACT_FACTS FROM INTO ` `CALCULATE_METRIC` Derive a measure from facts `CALCULATE_METRIC FROM INTO ` `COMPOSE_ARTIFACT` Compose an artifact from facts using a shape `COMPOSE_ARTIFACT FROM USING ` `VALIDATE_ARTIFACT` Validate an artifact against a schema `VALIDATE_ARTIFACT AGAINST ` `PERSIST_ARTIFACT` Persist an artifact to a destination · the adapter maps WRITE and EDIT to it; a refusal is named before it `PERSIST_ARTIFACT TO ` `EXECUTE_TOOL` Execute a command with a bound · the adapter maps BASH to it `EXECUTE_TOOL WITH timeout: INTO ` `REQUEST_DECISION` Ask a party to decide · the adapter maps ASK_USER to it, and resolves it absent for a bounded reader `REQUEST_DECISION WITH options: [, ] INTO ` `REPORT_RESULT` Report an artifact to the parties whose next work it creates `REPORT_RESULT TO ` ### Node keywords These tokens make up the node form, which is the unit of a document. They cover the header with its four-slot tag, the contract, the substrate stage at which the node's artifact comes to be, and the slots and limits a document declares. `NODE` A node header · the unit of a document, one decision, one gate `# NODE — [ · · · yields: ]` `CONTRACT` A node's contract · input, transform, constraints, output, handoff `CONTRACT:` `YIELDS` The shape a node's decision resolves to `yields: ` `GENESIS` The substrate stage the node's artifact comes to be at · phase order follows it `@genesis: ` `PRESERVES` The distinctions a transform keeps · a lowering names what a later check needs `preserves: , ` `OUTPUT_CONTRACT` The one record the next node reads, as an assignment `# OUTPUT CONTRACT` `LIMIT` A declared limit · stated where a reader would otherwise assume the opposite `LIMIT : ""` `SLOT` A slot's state · resolved, absent or deferred, declared by the adapter `SLOT {.}: RESOLVED | ABSENT | DEFERRED` ### Validation keywords These tokens make up the handoff gate. They cover a check with its evidence and the population it was measured over, the refusal before a write, the standing of the read set, and the three verdicts, with unknown routed to blocked. `ASSERT` Hard assertion `ASSERT condition` `REQUIRE` Prerequisite check `REQUIRE dependency` `HANDOFF` Gate marker · the evidence-bearing gate that closes a node `HANDOFF GATE (evidence-bearing):` `GATE` Checkpoint marker `HANDOFF GATE:` `CHECK` A check in a gate · a claim about the output with the evidence that settles it `[check] (evidence: )` `POPULATION` The set a check ranges over, measured · zero of zero is not evidence `over: measured: / ` `REFUSE` Where a node refuses to continue · named before the irreversible write `refuse: before ` `FRESHNESS` The fingerprints an artifact was derived from · a semantic property, never a timestamp `freshness: + ` `STANDING` Whether the read set moved beneath the verdict · a non-empty moved set withdraws the standing, never the verdict `standing: moved-set ` `UNKNOWN` The third verdict · an unmeasured or unevidenced claim, never a pass `unknown → BLOCKED` `BLOCKED` The closure of an unknown or an unanswered decision · external input is owed `result: ... | unknown → BLOCKED` `PROMOTE` Move a candidate into accepted state · only on a clean verdict, never on production `promote: ON clean verdict` `PUBLISH` Cross the boundary to the external system · the party that crosses it is named `publish: BY ` `RESULT` The result line · the next node on pass, the repair owner on failure, blocked on unknown `result: pass → NODE | → REPAIR (owner: ) | unknown → BLOCKED` `REPAIR` The repair edge · re-enters at the earliest node that can supply the missing evidence `REPAIR (owner: NODE )` `RULE_ID` The gate's identity, the node it closes `rule_id: ""` ### Report keywords A verdict is written as a report so that a later checker can challenge it. The report's fields record what was measured, over what, from which inputs, and whether the three termination conditions coincide. `SUBJECT` The node or stage the report is about `subject: ` `VERDICT` The value returned · pass, fail or unknown `verdict: pass | fail | unknown` `DOMAIN` The population declared and the population measured `domain: declared measured ` `POPULATIONS` The partitions, each measured · their sum is the whole `populations: , ` `INPUTS` The inputs read, by identity and fingerprint `inputs: ` `CODE` The fingerprint of the code that produced the verdict `code: ` `OUTPUT` The artifact written, by identity and fingerprint `output: ` `REFUSALS` How many times the stage refused, and why `refusals: []` `UNRESOLVED` What stays open, and why `unresolved: []` `COMPLETION` Saturated, complete and verified · the three that must coincide `completion: saturated complete verified ` ### Invariant keywords An invariant record states a property in a form that could be false, the set it quantifies over, the parties it binds, and the objector that would disagree if it stopped holding. A record with no objector declares none, and the missing check stands as declared debt. `INVARIANT` The record head · a property the topology relies on, with its set, its parties and its objector `INVARIANT : over: binds: objector: ` `PROPERTY` The property, in a form that could be false `INVARIANT one-writer: a record has exactly one writer ...` `OVER` The set the property quantifies over `over: every record on the surface` `BINDS` The parties the property constrains · who must receive it `binds: every party writing there` `OBJECTOR` What would disagree if the property stopped holding · a check, or none as declared debt `objector: [check] one open fence per record | none` ### Meta keywords The meta block and the node tags state what the document is for, which source grounds which, what it trusts, what it may touch and what it declares outside itself, and how far repair may recurse. `META` Metadata block `%% META %%:` `USE` Template usage `USE TEMPLATE name` `TEMPLATE` Template reference `USE TEMPLATE validation` `CUE` The one-line reminder a reader executes at a node `@cue: ""` `RECURSION_LIMIT` A bound on repair, declared in the meta block `recursion_limit: ` `PURPOSE` What a node decides, in one sentence `@purpose: ""` `AXIS_QUESTION` The question a node's axis asks `@axis_question: ""` `PRIORITY` The authority tiers · which source grounds which, highest first `priority: > >