by-design-workflow

To route design intent, supply target description, modality, and upstream guidance; the workflow applies policy from .by/config.json to select the appropriate engine, protocol, and compute target, then outputs routing_decision.json for execution.

Forecasting design space and budget happens during routing; the workflow validates inputs and resolves defaults to predict wall-time and cost, gating your compute planning before generating handoff_package.json for downstream campaign management.

Yes, the design workflow supports routing to BoltzGen, PXDesign, and Protenix, matching your target description and modality to the correct engine along with the appropriate protocol and compute tier.

The best way to orchestrate design campaigns is providing target, modality, and budget, then running the route flow to generate routing_decision.json and handoff_package.json for downstream engine execution and campaign management.

Yes, you need .by/config.json to apply policy during routing; the orchestrator reads this configuration to validate inputs, resolve defaults, and produce structured artifacts for your design campaign.

You should avoid automated workflow orchestration if your design intent lacks clear target descriptions, modality requirements, or upstream guidance, as the routing process requires these inputs to validate, forecast budget, and generate handoff packages.