You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1.3 KiB
1.3 KiB
Decision 0002: Prompt Source Precedence
Status: Accepted Date: 2026-05-03
Context
Generation nodes can have both a node-local prompt and an upstream text connection. The product needs a clear rule for which prompt is used at execution time.
Decision
Connected upstream text wins over node-local prompt.
Prompt precedence:
| Node-local prompt | Upstream text connection | Execution prompt | Composer behavior |
|---|---|---|---|
| empty | none | missing prompt | editable, generate disabled |
| empty | present | upstream text | read-only display of upstream text |
| present | none | node-local prompt | editable |
| present | present | upstream text | read-only display of upstream text, local prompt shown as fallback/overridden |
Rationale
The graph must remain the source of truth for workflow relationships. If a visible prompt node is connected, users should see that the connection controls execution.
This also matches the current executor direction, where connected text is read before stored node prompt during regeneration fallback.
Consequences
- Composer prompt input becomes read-only when upstream text is connected.
- Composer must show a hint explaining that prompt is provided by an upstream text node.
- Tests must cover connected text overriding node-local prompt.