Reference - unoverse

Every field you can write, generated from the schemas the platform validates against. These pages are generated from those schema files, so they cannot describe a field the platform does not accept. They are regenerated whenever a schema changes.

What is here

	You write	Validated by
Design	`components/`, `apps/`, at the root of your org repo	unoverse.schema.json and manifest.schema.json
Nodes	`nodes/<name>/`, at the root of your org repo	the nine schemas at schemas/nodes

Not here yet

	Why
Styles and tokens	Your `styles/` YAML has no schema. Nothing validates a colour or a scale step, so there is no contract to generate from
Workflows	`workflow.schema.json` and `layout.schema.json` describe documents the canvas writes, not files you author
The wire envelope	`stream-1.0` is the transport contract, and matters to someone porting an SDK rather than to someone building on one

Where the guides are

This tab is the field list. The explanations live in Design for components and Nodes for integrations. Reach for a guide to learn the model, and for these pages to check a name.

Next steps

Primitives

The 18 elements a definition composes from.

node.yaml

What a node is, and how it is discovered.