ai registry: research_dir points at a folder that no longer exists
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 80/100
Research direction
Start in systems/superintelligence/ai/scripts/build_registry.py at the line that emits research_dir, and compare it with the generator or config the other teams use so you can see the correct superintelligence/<team>/research/<slug>/ shape. Grep the repo for research_dir to find out whether anything actually reads the field before deciding between fixing the path and dropping it. Then rerun the generator to rewrite systems/superintelligence/ai/registry.json and confirm every remaining research_dir resolves to a directory that exists. Done means the regenerated registry passes that check and was not hand-edited.
Written by the indexing model from the issue text.
Description
systems/superintelligence/ai/scripts/build_registry.py writes research_dir as superintelligenceTeam/research/<slug>/ for every ai persona. That folder no longer exists, so each ai entry in systems/superintelligence/ai/registry.json (67 lines) points nowhere. The other teams write superintelligence/<team>/research/<slug>/.
Fix: point the generator at the team's real research folder, or drop the field if nothing reads it. Then regenerate ai/registry.json with the generator. Don't hand-edit it.
Check: after regenerating, every research_dir in the registry either exists or the field is gone.
- Dominant language
- HTML
- Stars
- 347
- Forks
- 12
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 95
Getting set up
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 coco-research/coco
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#539 ·
Maintainers usually reply within 1 day
-
bug P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coco-research/coco#538 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
coco-research/coco#530 ·
Maintainers usually reply within 1 day
-
check-asset-counts: bare 149 tripwire collides with a real active-assets count of 149Possibly taken @aryankalantri claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coco-research/coco#473 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coco-research/coco#470 ·
Maintainers usually reply within 1 day
All issues in coco-research/coco
Similar issues
-
[MCP]: page snapshots in .playwright-mcp/ are not git-ignored (.playwright-cli/ is, since #42318)Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
microsoft/playwright#44289 ·
Maintainers usually reply within 1 day
-
dependencies
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JustBeanie/hass-volcano-hybrid#34 ·
Maintainers usually reply within 1 day
-
documentation good first issue trivial
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
daniel-ospina/tortoise#14235 ·
Maintainers usually reply within 1 day