type: concept

claim: Varro is a governed query and control surface over Helios authoritative sources, not the owner of truth and not a free-form chatbot.

domain: varro


claim: The Varro authority stack is authoritative sources, then Varro as the presentation window, then callers; if Varro and a source disagree, the source wins.


claim: The Varro command grammar has five verbs: ask, show, check, run, create; unknown verbs are rejected.


claim: VSL is a declarative language for describing systems, views, workflows, actions, and bootstrap descriptors; it is distinct from the live Varro command grammar.


claim: VSL maturity progresses through draft, checked, bound, and hardened; bound and hardened require concrete lowering support to fail closed rather than remain inferred.


claim: A VSL type can declare fields in the form field <name>: <kind> required|optional, including primitive kinds, arrays, and named enums.


claim: Enums represent closed value sets that can be referenced by fields, moving constraints from prose into a typed validation surface.


claim: A VSL action declares inputs, risk/binding posture, and a lowering target; executable constructs need explicit lowering targets at bound maturity.


claim: Varro previews governed action and evidence before mutation; execution requires an explicit execute path rather than default persistence.


claim: VSL lowers into existing Helios contracts and runtime descriptors rather than creating a parallel runtime.


claim: Prose-only constraints create entropy because they can describe allowed values without giving the validator a closed, checkable value set.


type: decision

claim: Source-backed KG promotion is gated until an adapter recomputes source hashes, checks evidence refs, passes review, and receives required approval.


type: task

claim: Full tutor grounding remains a future Build-1 task after the KG seed and output-shape contract are ready; the local shell does not yet integrate a tutor runtime.


claim: Public deployment to varro.mentormind.com.au is a gated milestone-2 task, not part of the current local milestone-1 pass.


claim: S1-S7 are workspace-local external sources. Their manifest hashes verify now, but KG records must remain not_source_backed until a promotion adapter checks the same hashes and review/authority gates pass.


claim: The frozen eval set can be scored through a bridge prompt and structured eval contract, but a Build-1 tutor answer surface is not yet integrated into the local shell.


claim: Public deployment requires a Rust publish-site adapter, release evidence, rollback plan, Claude Code review gate, and Philip approval. This kickoff creates only a release plan.