SCHEDULE · HAND OFF · VERIFY
Final summary: reconcile the inputs behind the result
Run six local transformations. Watch dependency gates, worker assignments, retries and the exact artifacts produced.
Scroll the dependency board horizontally to inspect every task. The task selector below provides the same states and artifacts as text.
Input and task inspection
Your experiment
Select the report and verification nodes. Check that histogram counts sum to the reported count and that weighted bins sum to the reported total. Empty input has a null mean, not a division error.
Load takes 2s, filtering 4s, joining 3s and verification 5s. Branch durations are adjustable. Default parallel execution with two workers takes 26 modeled seconds; serial execution or one worker takes 34. Use 0.5× for a slower inspection.
Load → filter → sum/histogram → join → verify. The filter retains values at least as large as the chosen threshold. Sum produces count/total; histogram produces actual bins. Verification recomputes count and weighted sum from the bins. A verified result exists only if they agree.
Scheduler events
Offline deterministic dependency scheduler, not an A2A/ADK protocol implementation, Java coroutine runtime, Airflow/Dagster service or LLM agent. All transformations execute locally without arbitrary code, external tools or network calls. Task durations are fixed teaching inputs independent of input length. Ready tasks take free worker slots in the displayed task order. A failed attempt commits no artifact; retries wait the chosen fixed delay. Exhausted failure blocks descendants, or cancels unfinished work under fail-fast. Tasks completing exactly at the deadline succeed before cancellation of unfinished tasks. No scheduling overhead, durable checkpoint, distributed race, compensation, network latency or persistent resume is modeled. Workflow concepts · DAG dependencies.
A final summary must reconcile its inputs
This final-summary exercise produces a numerical report from real local transformations rather than assembling plausible text. Load accepts an integer array, filter retains values at the threshold, sum computes count and total, and histogram computes value-frequency pairs independently. Join creates a candidate report containing both branch artifacts. Verification recomputes count and weighted sum from the histogram and compares them with the sum branch. A joined candidate is not yet a verified answer. Select Join report and Verify output at the same timeline point to inspect this difference. This is a deterministic reconciliation contract, not a language model evaluating whether prose is factually grounded.
Control data and dependencies
The JSON integer array is the actual input, limited to twenty-four integers between minus one thousand and one thousand. Minimum retained value keeps entries greater than or equal to that threshold; duplicates remain distinct observations. Branch dependency either lets histogram and sum start independently after filtering or makes histogram wait for sum. Worker slots limits simultaneous tasks to one or two. Sum duration and Histogram duration specify invented service seconds independent of input size. Load, filter, join and verify take two, four, three and five modeled seconds respectively. These are teaching inputs, not measurements of Java, Dagster or an LLM.
Challenge a report that looks almost correct
At default threshold zero, the input [3,1,-2,3,7,0] retains five values with total fourteen and mean 2.8. Histogram contains zero once, one once, three twice and seven once. Duplicates are observations and must not be discarded. At modeled second twenty-one the join has a candidate, while verification is still running without a committed output. At twenty-six it accepts the report. Inject one extra zero into histogram counts: the weighted sum is still fourteen, but the histogram count becomes six. Verification rejects that mismatch and never publishes an accepted result, even with three attempts. Change the input to an empty array: count and total are zero and mean is null, because an empty set has no arithmetic mean.
Separate attempt failure from workflow failure
Open Failure and retry controls. Injected failure task chooses sum, histogram, join, or no injected failure. Failure behavior chooses the first attempt or every attempt. Maximum attempts includes the original attempt; one means no retry. Retry delay is a fixed wait after a failed attempt, during which its worker is free. Exhausted failure policy either finishes independent work while blocking descendants or cancels unfinished work immediately. Disabled controls have no effect on the current scenario. Inject one extra zero into histogram counts produces inconsistent artifacts: the weighted sum stays unchanged but the count increases, so verification rejects the result. Retries cannot repair that deterministic corruption.
Inspect states, artifacts and time
Play and Pause inspect the generated schedule over sixty viewing seconds. Next event advances to the next scheduler state; Restart rewinds without changing inputs; Speed changes the inspection pace, while Modeled time scrubs the schedule and pauses playback. Editing inputs rebuilds the scenario and starts inspection unless reduced motion is requested. Inspect task selects a node, as does clicking its card. The text below reports dependencies, attempt, worker, error and committed artifact, providing an alternative to the diagram. A running task has no committed output. Final preview describes the eventual outcome even when the board still shows an earlier state.
Use a bounded local contract
Workflow deadline cancels unfinished tasks, but completions exactly at the deadline are processed first. With default inputs a deadline of twenty-six permits verification and twenty-five cancels it. Every transformation is executed locally in memory; there is no persisted checkpoint, distributed worker, remote tool, external side effect or production benchmark. The ready-task order is fixed by the displayed graph. Dependency edges express this fixture policy; they do not implement an ADK agent conversation or the complete Dagster asset system. A verified result proves only that this local histogram and sum agree on count and weighted total.
Keep comparisons and observations
Capture baseline saves the visible result and current inputs as a comparison point. Change a scheduling parameter, then use Replace baseline to record the new outcome or Clear baseline to remove the saved comparison. Baselines do not run another worker or prove an independent result. The notebook stores your observations locally in this browser; Export notes downloads that text as JSON. Expand experiment opens the workspace full screen and Exit full screen returns to the page. On a phone, focus the dependency board and use horizontal scrolling to reach its right-hand tasks, or use Inspect task to read the same state and artifact without interpreting the canvas. Speed settles elapsed time before switching pace; pausing or hiding the tab freezes inspection.