RFC 0019: may a dialect published without a pack be an entry (a preset)?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- documentation
Research direction
This is a design decision, not a code change: whether a pack-free dialect can be an Exchange entry, as set out in RFC 0019 §3 and the two options in the body. Read RFC 0019 §3 and judgment-pack-spec#166 first, then the open comment thread, which is where the decision is being argued. Done means the decision is recorded on this issue and carried into RFC 0019's next revision.
Written by the indexing model from the issue text.
Description
What this asks
Decide whether a dialect published without a pack can be an Exchange entry. RFC 0019 §3's entry names one pack by digest, and an entry's fixtures are held by that pack's preparations. The Desk's discovery presets (a research recipe that finds records before any pack qualifies them) have no pack, so under the current text they are authoring metadata until paired with a pack, and cannot be exported as conforming entries. The maintainer's review of the Desk's GTM recipe (2026-10-15) asks for the decision to be explicit rather than implied.
Options
- A. A second entry kind,
preset: directioninput, no pack, no preparation fixtures; verified by its document's form, digest and the catalog's scans only; the manifest row says so and a desk importing it pairs it with a pack locally before any run. What such an entry establishes is less, and the text says what. - B. No pack-free entries: a preset stays authoring metadata inside an installation until it is paired, and the Exchange holds only entries a pack's fixtures hold.
The recommendation is A, bounded as described, because the research line's first reusable artifact is the discovery recipe, and a catalog that cannot hold it holds the less useful half. Display metadata and suggested budgets grant no execution permission under either option.
Acceptance
- The decision recorded on this issue and carried by RFC 0019's next revision (with judgment-pack-spec#166's seven sentences).
- Dominant language
- Python
- Stars
- 5
- Forks
- 6
- Avg merge
- 6h 15m
- Merged PRs (30d)
- 69
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
-
RFC 0018 §9.3: the dependencies row still says absent for a local filePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 72/100
Judgment-Pack/judgment-pack-spec#200 ·
Maintainers usually reply within 1 day
-
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
-
RFC 0018: define portable page bindings for multiple discovered endpointsPossibly taken @kikashy claimed this today. Open
Judgment-Pack/judgment-pack-spec#199 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
Judgment-Pack/judgment-pack-spec#174 · 1 comment ·
Maintainers usually reply within 1 day
-
RFC 0018: the research kind's result contract, its binding form and the reconciliation of sourcesOpen
Difficulty 5/5 Over a week Newbie friendliness 8/100
Judgment-Pack/judgment-pack-spec#171 · 2 comments ·
Maintainers usually reply within 1 day
All issues in Judgment-Pack/judgment-pack-spec
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cellrishi-code/claude-skills-atlas#165 ·
Maintainers usually reply within 1 day
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-webui/open-webui#32635 · 1 comment ·
Maintainers usually reply within 1 day
-
Filters: ?field:ne=null matches NULL rows instead of non-NULL onesPossibly taken @rshdhere claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Netflix/metaflow-service#504 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
gke-labs/kube-agents#3394 ·
Maintainers usually reply within 1 day
-
A2A audit timestamps end in +00:00Z (invalid ISO 8601)Possibly taken @O1sumitkumar claimed this today. Openbug good first issue help wanted python
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day