Current Projects
Rollout flow: 🛠️ Drafts / In Progress / Needs Revision → 
Alpha Testing (PR alpha-ready → live alpha build on prod DB) → 
Beta-Version (Ready for Beta → combined build) → 
Production (Completed). Newest stage sits at the top of Current Projects; within a stage, live builds sit above queued ones.
📚 Developer Reference Projects
Onboarding & reference docs (e.g. new-hire machine setup). Flag any completed project into here with "📚 Reference."
Future Builds
Planned build tracks not yet started — Integrations, Facility tools, and other ideas. Claim any to move it into Current Projects. 🔒 PCC Marketplace research ↗ — interactive: 1,373 listings mapped competition vs. partner, with build-vs-buy verdicts and ★ priorities. Passphrase required (ask Greg); source in the private pcc-research repo. Research only, not projects.
↳ Integrations
External systems Togo connects to — planned/queued (not yet in progress; starting soon). Each vendor is broken into small, PR-sized projects with the vendor name as the first word of the title. Claim any to move it into Current Projects.
↳ Facility — facility-staff tools
Unclaimed facility-staff tools · % reflects code already in the branch · claim any to move it into Current Projects
↳ Other
Priority 1–5 ideas · Claim any to move it into Current Projects
ONC §170.315 Certification Requirements
GitHub Issues are the source of truth · Claim, beta-test, and submit criteria for ATL · bars fill automatically as contributing projects advance (α PR-alpha-ready/alpha 50% · β beta 75% · γ gamma 100% of each project's slice) — driven by each issue's status label, never edited by hand. The 100% line covers developer-closable work only; hatched segments past that line are testing/documentation and optional scope. Click any bar for the breakdown.
Production — Completed
Shipped to full production (closed)
Abandoned
Projects that were stopped