Expose a public finite registry or safe codec for native effect graphs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
Read the Varcode effect JSON graph schema and compare it with Vaxrank's finite-registry native artifact decoder; the issue points to openvax/vaxrank#750 and openvax/varcode#671. Done means consumers can use a documented finite registry or safe typed graph encoder/decoder without arbitrary class imports, with existing validation, cycle handling, and evidence preserved; tests cover ordinary, phased, and structural graphs and reject unknown class or function metadata.
Written by the indexing model from the issue text.
Description
Varcode 11 consumers now need to persist ordinary realized-candidate graphs. Vaxrank's native artifact decoder intentionally uses a finite class registry and does not import classes named by an input file. Varcode effect JSON has standalone class metadata in graph nodes and uses private _EffectReference and _AssembledAllele records.
Vaxrank's migration can register the reviewed classes explicitly, but this duplicates the codec's class inventory and requires private imports. Please expose a documented finite registry or a safe typed graph decoder/encoder so consumers can reuse the native schema without allowing arbitrary class imports. Preserve existing graph validation, cycle handling, and availability/baseline/hypothesis evidence. Tests should cover ordinary, phased and structural graphs plus rejection of unknown class/function metadata.
Related: openvax/vaxrank#750 and openvax/varcode#671. This API request does not require delaying the bounded candidate-traversal release.
- Dominant language
- Python
- Stars
- 88
- Forks
- 28
- Avg merge
- 3h 17m
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- No 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 openvax/varcode
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fritzprix/libr-agent#2612 ·
Maintainers usually reply within 1 day
-
needs-triage presubmit-gate
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
gke-labs/kube-agents#5001 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
simonw/sqlite-utils#928 ·
Maintainers usually reply within 3 days
-
colorado
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
freelawproject/juriscraper#2405 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
cline/mcp-marketplace#3576 ·