Learner Runtime Collect records what the answer surface proves.

The five verbs are ask, show, check, run, and create. An unknown verb is rejected.

S1 states the five verbs explicitly and that unknown verbs are rejected; G confirms both.

An enum is a closed value set: the field's allowed values become typed and checkable by the validator rather than being unconstrained prose in a comment. A plain string field with a comment leaves the constraint as documentation only, which the system cannot enforce.

S6 states that referencing an enum makes allowed values typed and checkable rather than prose comments; G confirms enums are closed value sets.

The minimum blocks are: identity, mission, authority lane, domain, maturity, context root, at least one compile target, and a runtime block.

T1 states exactly these eight elements are required for the smallest warning-free VSL system.

The authoritative source wins. Varro is the window, not the wall.

S2 states 'If Varro and a source disagree, the source wins' and that Varro is the window not the wall; G confirms authoritative sources sit above Varro in the authority stack.

draft -> checked -> bound -> hardened

S3 lists the four maturity levels in order; G confirms the same sequence.

Varro is a governed query and control surface, not a chatbot. It is not a free-form assistant: it accepts only five defined verbs, classifies all responses as fact, constraint, or suggestion, and routes all state-changing operations through the command kernel.

S1 states Varro is not a free-form assistant and describes the five-verb constraint and response classification; G labels it explicitly as a governed query and control surface.

VSL is a declarative language for describing systems, views, workflows, actions, and bootstrap descriptors; it is authored, synthesized, refined, validated, and lowered into contracts. The five-verb command grammar is the live query and control interface that callers use at runtime. VSL is explicitly not the same as the command grammar.

S3 defines VSL and explicitly states it is not the same as the live five-verb command grammar; G confirms VSL is declarative and distinct from the command grammar.

`lowers-to` on an action declares the lowering target: the existing Helios contract or bounded runtime artifact into which that action compiles. The bound maturity rung requires explicit lowering targets for every executable construct.

S3 states actions declare a lowering target with `lowers-to` and that bound requires explicit lowering targets for every executable construct.

Preview-by-default means a `run` command builds a typed `kg_command` preview without executing it. `--execute` must be explicitly supplied to cause the command kernel to perform the mutation. This prevents accidental state changes by requiring deliberate opt-in to live execution.

S2 describes preview-by-default behaviour and the role of --execute; G confirms mutation requires explicit execute authority.

A field declaration has the form: `field <name>: <kind> required|optional`. Valid field kinds include string, markdown, uri, integer, number, bool, string[] and other arrays, and named enum references.

S3 gives the field declaration syntax and lists supported kinds; S7 demonstrates real type and field declarations.

`varro check vsl` is read-only validation. It returns a validation result such as valid, error_count, and warning_count, and does not persist or change any state. State-changing operations go through the command kernel, which check does not invoke.

T1 describes the check command returning validation output only; S1 states all state-changing operations go through the command kernel, separating check from mutation paths.