Type
What kind of part this is — code, service, data store or interface.
Components
Typed, versioned building blocks — not scripts
A Devory component is a manifest-defined part with a type, configuration, real inputs and outputs, and a version. Components compose into larger components, and larger components into systems.
Data component
API component
Composed
What every component carries
Configuration
Typed settings a builder sets when placing the component.
Inputs and outputs
The typed contract a component accepts and produces.
Version
A specific, addressable build — not a moving target.
State
Whether the component is untested, tested, or qualified for reuse.
Connections
The real relationships this instance has to other tiles on a canvas.
Foundation library, honestly
Devory defines a foundation library of common component types as structured metadata — the shape every component of that kind should have. This is a schema, not a catalogue: no ready-to-use, shippable component currently exists in it. A usable component catalogue is still being built out.