Reference
Authoritative, as-built descriptions of every interface Valem exposes. One topic, one home — the rest of the docs link here rather than restating any of it.
| Page | The single source of truth for |
|---|---|
| Model spec format | Every ModelSpec field, across six section pages: schema/constants/defaults, derivations & constraints, effects, tests & evolution, views, component catalog. |
| Copy-paste spec examples | Minimal, self-contained ModelSpecs (one derivation, a constraint, an array rollup) with the exact command to create and run each — the fastest correct starting point. |
| API reference | REST endpoints, the WebSocket protocol, and the console JSON protocol — request and response shapes. |
| MCP tools & resources | Every MCP tool, its arguments, result shape and error shapes; the advertised resources; protocol details. |
| LLM prompts | Exactly what is sent to the LLM on generation, repair, evolution, and test-repair calls. |
| View system | ViewDefinition / ComponentSpec component types, the EvaluatedView contract, and the React renderer. |
Related references elsewhere
Two reference-grade documents live with the operational chapter because that’s where they’re used:
- Configuration — every
valem.*property, with defaults. - Security model — auth, origin checks, effect egress, limits.
And two look-ups that stand on their own:
- Glossary — canonical definitions of the core terms.
- Third-party libraries — what Valem is built on and why.
Reference pages describe the shipped system. If you want the reasoning rather than the specification, start with the Model guide.