Product context in Builder
Bind Product settings on the flow so compile and later stages use one product description instead of an unbound prompt.
Last updated September 27, 2026
Where Product lives
Product is a Builder setting, not a top-level app. Bind product context on the same Blueprint as Governance, Artifacts, Verification, Connections, and Environments.
Designer is not a general-purpose chat. The flow should name the product the stages are allowed to change.
What to attach
- product name and repository identity you intend to bind
- scope the agents may touch
- links or artifacts that describe current behavior
Compile does not invent a product from a blank canvas. If Product is empty, later stages have no agreed context and review artifacts will be incomplete.
Prefill from Verify
Audit + Validation may offer a prefill. Review it in Product settings before compile. Do not treat the audit next step as an applied control.
After install
Product context in Builder does not rewrite the bound GitHub repo by itself. A new description still needs compile, export, and install before Start Run uses it.