Save a condition and attach it as a rule in one call.

Does what builder_add_condition followed by builder_attach_rule does, and checks everything both would check before saving anything: a refused call leaves no definition and no rule behind. Use builder_add_condition, builder_compose and builder_attach_rule instead to reuse one saved definition in several rules or to combine saved definitions.

Roles: entry (requires direction 'long' or 'short'), exit (optional direction and size_frac), gate (blocks entries while false). A stop, target or trailing stop belongs in an exit rule, not an entry or gate.

Entry rules on the SAME side are ANDed on the same bar. Express alternatives inside one any_of condition. Long/short groups are alternatives; simultaneous signals place no entry. Position policy controls repeated entries and reversal while invested.

Start with builder_discover(action='quickstart') for a complete example. overview lists the complete grammar and units; get supplies exact primitive detail. Inline sequence/Boolean children need no separate save/compose calls. The complete machine-readable schema is action='specification'.

Returns definition_id, rule_id, name, source, source_version and description. Use rule_id for builder_detach_rule.