Enterprise format · Growth plan
CUE
Schema definition with validation.
5 / 5GEO score
CUE · Geordyschema.cue
Why it matters
CUE unifies schema definition, validation, and configuration into one language with a sound type system based on the lattice of types and values, which makes it ideal for emitting machine-checked configuration that AI agents can both read and generate without producing invalid YAML/JSON. Its constraint-based model lets you describe data shape and data values in the same file.
Geordy generates this format for every page on your site that warrants it - auto-detected by page type, served from your subdomain, and refreshed on the cadence below.
Sample outputschema.cue
# CUE configuration for Geordy AI Platform
package main
site: {
name: string
domain: string
category: *"GEO / LLMO" | *"AI / ML"
}
site: name: "Geordy AI"
site: domain: "geordy.ai"Get it right
How to make this format work for AI.
DoBest practices
- Define schemas as definitions (#Schema) and unify concrete data with them; never duplicate field names across schema and instance.
- Keep packages small and use `cue export` / `cue eval` to emit JSON or YAML rather than hand-writing those files; let CUE be the source of truth.
- Use disjunctions (`|`) with defaults (`*`) for optional configuration knobs and constrain numeric/string values with bounds (`>=0`, `=~"^[a-z]+$"`).
- Run `cue vet` against your data files in CI to catch schema drift early; pin the cue tool version in your repo.
AvoidCommon pitfalls
- Treating CUE like YAML: order of fields does not matter and duplicate fields are unified (and may conflict), which surprises users coming from override-style config.
- Forgetting that definitions starting with `#` are closed by default - adding fields not in the schema produces a `field not allowed` error.
- Confusing concrete values with constraints: `int` is a type (incomplete), `42` is concrete; `cue export` fails on incomplete values without `-e` or defaults.
Where it shines
Use cases, scored for AI visibility.
Configuration managementGEO 5/5
Data validationGEO 5/5
API definitionGEO 4/5
Used in production by
Real sites already shipping CUE.
Working with it
Tools & resources for CUE.
The trade-offs
Strengths
- Unified language for config + validation + templating
- Strong type safety
- Composability
Limitations
- Steeper learning curve than JSON/YAML
- Smaller ecosystem
Spec sheet
Filename
schema.cue
Refresh cadence
weekly
Released
2018 · CUE Project Contributors
Read byAI validatorsBuild pipelinesSchema-aware code agents
Other enterprise formats