Vocabulary Overview
A small set of keywords recurs across Aggrega’s entities. Rather than re-explaining them on every entity page, the Vocabulary chapters concentrate the teaching in one place per keyword family. Every entity that accepts one of these keywords does so with the same semantics this chapter set specifies.
The vocabulary falls into four families: the topology triad (provides, inject, uses) that wires explicit topological edges between nodes and carries the injection contract the compiler pipes through; the data pillars (values, infra, parameters, locals) that separate the four data concerns — developer intent, physical sizing, per-environment knobs, and private Recipe state; the inheritance and interface keywords (extends, implements) that compose catalog entities and declare which Component a Recipe implements; and the modifier system (appliesTo, appliesToAnyOf) that governs which nodes a Feature attaches to via label selectors. Conceptual framing for how the pillars separate concerns lives in ../architecture/06-data-taxonomy-and-composition.md; topology resolution mechanics live in ../architecture/07-dependency-resolution.md.
Per-topic reference
- Topology triad:
provides,inject,uses— the injection contract and the explicit topological-edge declarations. Covers compact vs. verbose inject syntax, the.context.inject/.context.usespipe shapes templates read, and the dual-state context that protects Ops from nil-pointer panics. - Data pillars:
values,infra,parameters,locals— the four data pillars and their ownership. Developer-ownedvaluesandparameters, Ops-ownedinfra, Recipe-privatelocals, and the parameter-hoisting pattern for per-environment variation. - Inheritance and interface:
extends,implements— catalog-entity inheritance viaextends(the YAML envelope deep-merge common to Components and Features, the data pillars an extending Component inherits from its base whole, and the JSON Schema 2020-12 composition a Feature’s schema undergoes) and the Recipe-to-Component declarationimplements(exact, versioned-range, unversioned forms), which the Manifest’s mapping is checked against —implementsnever selects a Recipe. - Modifier system:
appliesToand selectors — Feature attachment selectors, the native Go label-matching engine, the string-form selector grammar, and the OR-composingappliesToAnyOfvariant. - Outside the four families: compact-form authoring, cross-document references, labels and annotations, the publishing surface, social contracts, the validation surface, output composition, the URI grammar and version resolution.