Valdris.aiControlled terminology
Each term has one public meaning, a status, and a usage boundary. Status identifies whether the term is standard, emerging, vendor-specific, internal, contested, or uncertain.
standardemergingvendor-specificinternalcontesteduncertainSoftware that installs repository controls, routes work, records external coding-agent activity as evidence, checks required proof, and blocks unsupported completion.
primary_public_categoryThe part that coordinates policy, run state, evidence, gates, and approvals around a defined repository workflow.
qualified_secondary_architectural_roleIntegration design that prioritizes normalized runtime events and artifacts.
internal_design_onlyOperating principle that requires evidence before completion.
operating_principleExternal tool that can inspect a repository and perform implementation work.
external_runtime_roleUnnumbered foundation assurance that precedes production-domain evaluation.
foundation_assuranceProduction-readiness assurance categories derived from the attributed source model.
assurance_taxonomyRequired artifacts, schemas, bindings, and coverage are valid.
Commissioned adapters and thresholds prove the intended behavior.
An independent trusted runner, provider, signer, or authority attests the result with rollback-resistant state.