Preparing your workspaceloading the brief, studio & editor…

Loadingone moment…

extracttransformloadorchestrate

Scenario

7.Creatorpayoutrun

CreatorPay pays creators for what they post. A creator earns small amounts all day — a share of ad revenue on a video, a tip, a subscription split — and every Friday a payout run sends the money to their bank. The earnings service exports those money events daily; the run has to turn a week of them into one transfer per creator. When the run executes, money leaves the company and cannot be recalled. Design the pipeline behind it.

This pipeline must answer

01What is each creator owed on Friday — and how do you know that number is right?
02The run paid 41,300 creators. Does that match what actually arrived?
03On Monday you find Friday's run overpaid 200 creators. What do you do?

Guardrails

Nothing may be paid twice, and nothing may be silently dropped — a dropped earning is a creator underpaid by an amount nobody will ever notice
You must be able to show, for any amount paid, which earnings it was made of
Include a check before the run executes and a path for earnings you cannot use
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

Earnings arrive every day. The run pays on Friday. So what runs, and when?

The deadline the bank actually imposes, and what starts the thing that moves money.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

What is the last safe moment for the run to be finished?
e.g.
Transfers have to be submitted before the bank's Friday cut-off, so the numbers need to be final well before it — with room to stop, look and start again.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Does anything here need to be faster than that?
e.g.
A creator's dashboard is not this pipeline. This one exists to move money once a week, and paying faster is not a feature anyone asked for.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Run the review to check your architecture against this scenario — a valid DAG, a trigger for the freshness SLA, a transform stage, a quality gate before publish, and a failure path — then defend it in a short interview.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Preparing your workspaceloading the brief, studio & editor…

extracttransformloadorchestrate

Scenario

7.Creatorpayoutrun

This pipeline must answer

01What is each creator owed on Friday — and how do you know that number is right?
02The run paid 41,300 creators. Does that match what actually arrived?
03On Monday you find Friday's run overpaid 200 creators. What do you do?

Guardrails

Nothing may be paid twice, and nothing may be silently dropped — a dropped earning is a creator underpaid by an amount nobody will ever notice
You must be able to show, for any amount paid, which earnings it was made of
Include a check before the run executes and a path for earnings you cannot use
Avoid invalid cycles

Act 1 · Specify — answer all 8 and your spec flows0 / 8 answered

1Trigger & cadence

Earnings arrive every day. The run pays on Friday. So what runs, and when?

The deadline the bank actually imposes, and what starts the thing that moves money.

This choice changes which questions you are asked next — and the pipeline you end up drawing.

◆ What you are committing to on the canvas

What is the last safe moment for the run to be finished?
e.g.
Transfers have to be submitted before the bank's Friday cut-off, so the numbers need to be final well before it — with room to stop, look and start again.
- configTrigger `Runs` = daily / hourly — leaving it unset is what fails the freshness check
Does anything here need to be faster than that?
e.g.
A creator's dashboard is not this pipeline. This one exists to move money once a week, and paying faster is not a feature anyone asked for.
- nodeOrchestration & contracts → Scheduler trigger for a clock; Amazon MWAA, Step Functions, Dagster or Prefect when one step has to wait for another to finish

New to this?Batch vs Streaming vs Micro-batch

Edit your answer here✓ captured

Markdown: **bold** · *italic* · # heading · - bullet

Act 2 · Architect

Practice studio

Ctrl/Cmd + C copyCtrl/Cmd + V pasteCtrl/Cmd + Z undoDelete remove

40%

Design review

The reviewer reads your pipeline.

Desktop only

This scenario runs a full workspace — editor, canvas and results side by side. It needs a laptop or desktop to be usable. Open this page on a bigger screen to start building.

Read the library instead Back to modules

Creator payout run · Pipeline Builder scenario · D8LooP