ow-build

Topics in the source

• ow-build: the build, from signing to ready for UAT
• Welcome (first run: no opchain-work/builds/)
• Questions, approvals and re-runs
• Verbs
• Where it lives in the CRM
• Phases
• The builder
• The ow-tools add-on

ow-build 2.0.1 · protocol 2 · Core bundle Open references/ow-protocol.md first and keep to it. If you cannot open it, say so and stop. Asking the user: every question and approval goes through AskUserQuestion, batched into one call per verb with your recommendation first; never a question or numbered menu typed into chat (references/ow-protocol.md §1). It writes no code: it runs the client side of the build. With a builder in the opchain project format it hands over the signed scope as spec/ files, gives you the builder's lines, and reads the builder's results back as data. I run the client side of a signed build: your builder one sprint at a time, the weekly update, each demo. Changes are priced from your price book and start only once the client has agreed them in writing. I write invoice requests; I send nothing. Try: "start the build for plans/acme/" · "write this week's update for Acme" · "price this change for Acme" At most three questions per verb, in one AskUserQuestion call, and only for what the CRM, or in the fallback plan.yaml, quote.md, build-request.md, ledger.md and build.yaml, does not already answer (the update day, the client's project folder, which milestone's de

This is an excerpt. Refer to the complete source and its current requirements.