A portable workflow contract for staged research: dependencies, selection, per-record execution, output relationships
Maintainers usually reply within 1 day
@kikashy is already working on this.
Since Oct 15, 2026.
Assessment
This issue has not been assessed yet.
Description
What this would decide
Whether the specification defines a workflow contract for staged research: a portable statement of the dependencies between dialects (a downstream dialect runs for records a previous stage selected), the selection of records between stages, per-record execution, and the relationships between a stage's outputs and the next stage's inputs. A pack decides one case; a dialect prepares one case's inputs; nothing today says how a second dialect runs over the records a first one found and a reviewer selected.
Why
The Desk's research line (judgment-pack-desk#369, #371) chains stages: discover organisations, then research people at the selected organisations, each stage a dialect with its own pack. That chaining is implemented as Desk-private code naming the domain (organisation, person, the identity relation between them), so it is portable to no other installation and publishable to no Exchange. The decision graph the runtime evaluates (judgment-pack-spec RFC 0011 and the runtime's graph) sequences decisions, not research; it does not express "run this dialect for each selected record of that one".
What it would and would not do
- Would: define a workflow document (stages, each naming a dialect and a pack by digest; a dependency from a stage to a previous stage's selected records; the selection rule, by a reviewer or by a disposition; the per-record execution; the output relation recorded in each record's lineage), its canonical form and digest, and what a workflow establishes (that these stages ran over these selections, by their records) and does not.
- Would not: change Core, the dialect format or the graph; orchestrate anything itself (the Runner runs stages; the Desk reviews selections).
Prerequisites and process
- RFC 0018's version 3 implemented in a Runner (judgment-pack-runner: reading version-3 documents and binding at import), so a stage's dialect can be a published one.
- The interim review regime; an RFC under
rfcs/of the standards track, with fixtures recorded from a two-stage workflow.
Acceptance
- An RFC under
rfcs/, with the workflow document's form, what it establishes, and two-stage fixtures. - The maintainer's decision recorded on this issue.
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 8h 14m
- Merged PRs (30d)
- 98
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Judgment-Pack/judgment-pack-spec
-
Cover a rule's or an exception's reference list written without its array, or with a repeated entryOpengood first issue
Difficulty 2/5 Half a day Newbie friendliness 76/100
Judgment-Pack/judgment-pack-spec#158 ·
Maintainers usually reply within 1 day
-
Fingerprint the record shapes the specification defines, with a format-status record per familyOpenenhancement
Judgment-Pack/judgment-pack-spec#256 ·
Maintainers usually reply within 1 day
-
enhancement planning:deferred
Difficulty 5/5 Over a week Newbie friendliness 15/100
Judgment-Pack/judgment-pack-spec#255 ·
Maintainers usually reply within 1 day
-
Define bounded pack-design advisories for coverage, reachability and rule/exception interactionsPossibly taken @kikashy claimed this 1 day ago. Open
Judgment-Pack/judgment-pack-spec#252 · 1 assignee ·
Maintainers usually reply within 1 day
-
Workflow: preserve and credit every contributing rule or forcing exceptionPossibly taken @kikashy claimed this 1 day ago. Open
Judgment-Pack/judgment-pack-spec#251 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
Project submission:Open
Difficulty 1/5 Under an hour Newbie friendliness 72/100
slavakurilyak/awesome-ai-agents#845 ·
Maintainers usually reply within 1 day
-
tests: pin that the atomic writers in utils/paths.py stage the temporary file in the target's directoryPossibly taken A pull request linked to this issue is open or already merged. Opendifficulty:2 enhancement good first issue
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
MakazhanAlpamys/Soup#2178 ·
Maintainers usually reply within 1 day
-
[BUG] dcg.waggr permutation p-values are folded twice, so near-zero scores get the smallest p-valuesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
scverse/rapids-singlecell#854 ·
Maintainers usually reply within 1 day
-
Slang input: int8_t4_packed and uint8_t4_packed are copied into CrossGLPossibly taken @ninglinLiu claimed this today. Openarea:frontend backend:slang bug direction:input
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
random_elements(unique=True) on an OrderedDict: ZeroDivisionError once only zero weights remain, AssertionError with use_weighting=FalsePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 13 days