Managed Build quickstart
Use Dengel Build when you want Dengel to plan and implement a change. You provide the outcome and acceptance checks. A managed worker creates a candidate, an independent verifier checks it, and a named human decides whether it can land.
Access required. Ask your early-access contact to confirm managed Build, repository access, and eligible worker and verifier capacity for your workspace. Confirm that the workspace can fund the quoted work and identify who can approve the plan, spending, and landing. The free Git offer includes no inference credits. See signup and access and pricing and limits.
1. Save a small idea
- In the Dengel panel, open Projects, choose New project, and select Build from an idea if asked.
- Describe one outcome, how you will check it, and what is out of scope. Select Save idea and answer any open questions in the draft.
- For this quickstart, select New project when asked whether to start from an idea or existing code. Select Continue, then Plan and price this idea. Use Existing project only if your workspace has an eligible connected repository and you can confirm the target branch.
For a first run, try asking for a single static page with a specified heading and a check that verifies the heading. Leave accounts, external services, and deployment out of that brief.
2. Review the plan and spending cap
Open Review the plan and price. Check the outcome, scope, target, and acceptance checks. The named technical approver approves the plan. The named sponsor approves the matching Build Quote after reviewing its estimate, hard spending cap, and expiration. The panel may offer Approve plan and price if the same person holds both approvals.
If the plan changes or the quote expires, review the current plan and quote before starting. If the workspace cannot fund the quote, ask the sponsor to resolve it in the panel. Adding credits does not raise an approved cap. New paid work stops at that cap.
3. Start the build and check the candidate
Open the run and select Start building when it is available. Follow the run for progress and decisions. If it is waiting for a runner, leave the run queued and ask your early-access contact if the wait persists.
When a candidate is ready, follow the independent check on the run. Select Start the check if the panel offers it. Review the verdict and the acceptance results for the exact candidate commit. A failed check needs remediation. If a required result is missing or could not finish, treat the verdict as inconclusive and resolve the missing evidence before delivery.
4. Review delivery and confirm landing
Open Delivery and review the target branch, candidate, checks, and any open concerns. Once Dengel marks the exact change ready, the named delivery approver can select Approve and merge. If the approval is unavailable, check the delivery decision and the named approver in the panel.
After landing, open Technical record on Delivery and find the signed Receipt. Compare its canonical commit with a fresh read of the target branch. If the branch has moved again, check that the Receipt commit is in its history.
For agents
Help draft the brief, inspect the evidence, and report the run link, candidate commit, and current verdict. Flag a changed plan, expired quote, or missing check for the named human. Leave approval of the plan, spending, and landing to the authorized people in the panel. If you already have an agent-produced change, follow the Guard quickstart.
Use the CLI reference to inspect a run from the terminal or the workflow reference to interpret its state and Receipt.
