Orrery publication doc still names the closed calibration-diagnostics#208 as a prerequisite
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- markdown, python
- Domain
- documentation
Research direction
Read docs/orrery-publication.md and compare its prerequisite claims with the current publication flow described in the issue. Explain that builds submit graph files to the collector’s artifact intake, the collector’s graph worker publishes them, and queued uploads remain pending with files preserved until that path is available. Remove the reference to #208; done when the doc describes today’s behavior and replacement flow without naming #208 as a prerequisite.
Written by the indexing model from the issue text.
Description
docs/orrery-publication.md says remote Orrery publication "requires PolicyEngine/calibration-diagnostics#208 deployed", and that the hosted authorization deployment remains a prerequisite after migrating a workstation. #208 was closed unmerged on 2026-10-15, so it will never be deployed.
The collector will publish Orrery graph files itself instead: builds submit them to the collector's artifact intake (PolicyEngine/microcosm-collector#12), and the collector's graph worker builds and publishes them. Until then, uploads that builds queue stay pending in the emitter's local queue with their files preserved, and no attempt can succeed.
The doc should:
- describe what happens today and what replaces the direct upload;
- stop naming #208 as a prerequisite.
- Dominant language
- Python
- Stars
- 0
- Forks
- 6
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 132
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 PolicyEngine/microcosm
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PolicyEngine/microcosm#1220 ·
Maintainers usually reply within 1 day
-
Update two stale comments about the export-mass reviewed-exclusion registerPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
PolicyEngine/microcosm#1108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
PolicyEngine/microcosm#475 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/microcosm#1406 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
PolicyEngine/microcosm#1401 ·
Maintainers usually reply within 1 day
All issues in PolicyEngine/microcosm
Similar issues
-
[oblt-aw][autodoc] Update docs for security org scaffolding and Docs AI menu permission changesPossibly taken @github-actions claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
external integration integration-submission
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
langchain-ai/docs#7077 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
acl-org/acl-anthology#10623 · 1 comment ·
Maintainers usually reply within 1 day
-
Use context to recognize personal initials and lowercase namesPossibly taken @lipikaramaswamy claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
NVIDIA-NeMo/Anonymizer#340 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
btclib-org/btclib-node#2083 ·
Maintainers usually reply within 1 day