Remix and Nested Workflows

Overview#

Composed (remix) workflows charge the sum of sealed child prices plus the root margin and compute. Each called workflow earns 80% of its own margin when it executes, exactly as if run directly.

There is no shared remix revenue pool. Nesting is unlimited with cycle detection at publish and execution. Child prices are locked when you add them in the builder.

How composed pricing works#

When you add a remix node in the builder, it references a published workflow version. The price from that version is pinned at insert time and stored on the node.

The product page and publish preview show the full composed total: root margin plus compute plus each sealed child's pinned price. There are no hidden add-on charges at run time.

At run time#

When you trigger a composed workflow, you are charged the full composed displayed price on success. Each child workflow runs sealed inside the root execution. When a child completes successfully, its creator earns 80% of that child's margin.

The root creator earns 80% of the root margin only, not a cut of child prices.

Nesting and cycles#

A child workflow may itself contain remix nodes. Prices sum recursively up the tree. Edgaze blocks graphs that would loop (for example, A calls B calls A) at publish and at execution.

Special cases#

• Child price drift after publish: You still pay the locked price shown on the sealed node, not the live child listing price.
• Child failure: Child margin is not charged. The root may fail. Root margin release follows the standard failure policy.
• Bundle on root only: Bundle draw applies to the root workflow version. Child charges settle inside the composed total.

What you see in Edgaze#

• Builder: sealed node badge with the composed child price
• Product page: full composed total before run
• Cycle error: clear message when adding a cyclic remix edge

Related policies#

• What You Pay For
• Version Pinning
• Publish and Price
• When Runs Fail