Goals, briefs and notes
Make context available to later nodes and annotate the canvas.
A Goal / brief or other design-context node can pass text and mapped values through the workflow. Write a concrete objective, the constraints and the result someone should be able to inspect. The runtime exposes configured context text under fields such as goal, instructions and finalPrompt. For example, map a generation node’s prompt to $.nodes.node_goal.output.finalPrompt, using the actual upstream ID from the editor.
Use a Sticky note for operating instructions, explanations or reminders. The editor excludes canvas notes from the workflow flow and the upstream reference picker.
If a connected capability still receives an empty prompt, open its input mapping, confirm the referenced design node is upstream and inspect the resolved value in the run. Keep model calls and file creation in executable steps.