Builder receives an approved specification, target evidence, project constraints, templates and a selected model. It produces a draft automation, a build summary, assumptions, known gaps and a validation checklist.
#The build contract
The model proposes. The deterministic TaskSultan pipeline validates the result. A developer remains responsible for checking selectors, credentials, retries, exception classification, application state and business acceptance criteria.
#Typical outputs
- a Studio-ready project or package;
- generated workflow structure and target mappings;
- configuration and setup notes;
- test cases and sample data requirements;
- a trace from specification steps to workflow steps;
- warnings for unsupported or ambiguous requirements.
Builder should refuse or pause when the specification is not approved, required target evidence is missing or a step would require a secret that has not been configured by the customer.