Vector guide
How the planning model fits together
Trace how vectors advance outcomes, fulfill recipes, and flow through an instance allocation into end space.
Follow the allocation path
Vector → ordinary recipe → commit → instance recipe → derived ends.
Contests add an optional zero-sum allocation layer between recipes and their ingredients.
The many roles of Vectors
Most terms in the model describe a role that a Vector plays in a particular relationship.
| Term | Meaning |
|---|---|
| Vector | A thing you can do, value, pursue, or advance. It is the fundamental node. |
| Component | Another vector this vector directly advances: doing A produces progress toward B. |
| Recipe | Not a separate model. Any vector with ingredients becomes a recipe. |
| Ingredient | A vector that can fulfill a recipe: to accomplish A, allocate work to B. |
| Instance recipe | A protected recipe vector representing the instance's current overall allocation. |
| End | All vectors are projected into end space by a special path aggregator. |
| Subcontest | A specialized ingredient with weight selected by a zero-sum allocator. |