docs: dev note for workflow chaining#775
Draft
andreatgretel wants to merge 1 commit into
Draft
Conversation
Contributor
|
Fern preview: https://nvidia-preview-pr-775.docs.buildwithfern.com/nemo/datadesigner
|
andreatgretel
changed the title
nabinchha
reviewed
Jun 26, 2026
| The new part is the boundary. Because the boundary has a name, you can stop there, inspect the selected output, replace it with an approved artifact, and resume downstream without rerunning the trusted upstream work. | ||
|
|
||
| ```python | ||
| from data_designer.interface import ResumeMode |
Contributor
There was a problem hiding this comment.
this makes me wonder if ResumeMode should be moved to config so we can just do dd.ResumeMode ....
nabinchha
reviewed
Jun 26, 2026
|
|
||
| In that shape, `quality_gate` is both a normal stage and a contract. Upstream work promises a schema. Downstream work consumes that schema. A reviewer, evaluator, dashboard, or cleanup script only has to preserve the contract. | ||
|
|
||
|  |
Contributor
There was a problem hiding this comment.
Something seems off here....
nabinchha
reviewed
Jun 26, 2026
Comment on lines
+83
to
+85
| The demo task is document field extraction: generate synthetic invoices and forms, propose boxes around the fields to extract, and turn those boxes into structured rows. A weak detector proposes boxes on each page and assigns uncertainty. The workflow pauses at `review_candidates`, where all rows are still present but only the uncertain rows are marked for review. | ||
|
|
||
| The reviewer corrects the proposed boxes for that uncertain slice. They do not relabel the whole dataset, and they do not change the workflow shape. They write a replacement artifact with the same row count and schema, then the downstream stages use human-corrected boxes where they exist and calibrated detector boxes everywhere else. |
Contributor
There was a problem hiding this comment.
I believe conditional generation could achieve the same goal within a same DD stage? Just calling it out. Might be interesting to offer as an alternative?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📋 Summary
Adds a dev note and runnable recipe for workflow chaining as a pause/inspect/resume control surface. The post focuses on what named stage boundaries enable, including human review, reusable intermediate artifacts, downstream resume, and future workflow shapes.
🔗 Related Issue
N/A
🔄 Changes
review_candidates, writes a reviewed artifact, and resumes downstream from that artifact.🧪 Testing
.venv/bin/ruff check ..venv/bin/ruff format --check ..venv/bin/pytest packages/data-designer/tests/docs/test_document_review_gate_recipe.pyenv npm_config_cache=/private/tmp/npm-cache-datadesigner make check-fern-docs(0 errors, 1 existing Fern warning)✅ Checklist