Roadmap
Five phases. Each one exits through a test a real coordinator or a real committee can pass, not through a date. Weeks are build effort, not calendar promises.
| Phase | Effort | Delivers | Exits when | Status |
|---|---|---|---|---|
| 0 · Ingest discovery | 3 weeks | Inventory of real exports from two programs (headers and shapes only, never values); Program Data Package schema v1; synthetic program generator; runtime bake-off on a locked-down PC; a written runtime decision | Both builders sign the data contract and the runtime decision | Synthetic pipeline runs in both runtimes (alpha demo); waiting on real export structures |
| 1 · PEC generator, second program | 5 weeks | ACGME, exam and New Innovations adapters behind the package; PEC dashboard from the existing core; verification and sign-off | A coordinator at a second program builds a verified dashboard unaided in under 30 minutes | Not started |
| 2 · Any data source | 3 weeks | Internal-survey and operational adapters; bring-your-own CSV mapping; action plan with APE export | A source nobody planned for is mapped and charted with no code change | Not started |
| 3 · CCC generator | 5 weeks | New Innovations evaluation and milestone adapters; resident and committee views; persistent notes | One real CCC meeting run from it at each of two programs | Not started |
| 4 · Subscription layer and release | 3 weeks | Committee brief export; skills matched to the package schema; IT security note; release process; pricing test | Three programs outside the pilot pay or decline at a stated price | Not started |
| Relative Value | parallel | Per its own plan: program-wide launch and Season 0 | Its own gates | Phases 0 to 3 live |
What is decided and what is open
Fixed now
The pipeline shape. The package contract. The five rules: no custody, no model in the data path, provable source fidelity, the package is the product, requirements before runtime.
Open until Phase 0 ends
How the generator is packaged: a Python executable, a single offline HTML file, or both writing the same package. Decided by what a coordinator at the second pilot site can run unaided.
Open with our partners
The name. Ownership and the institutional path to an entity that can sell. Which program is pilot site two. Which result is the first paper.
Out of scope for version 1
A hosted, multi-program web application. Replacing or writing back to New Innovations, MedHub or ACGME ADS. Resident-facing views of CCC data. Automated milestone ratings or any AI judgement about a resident. The DIO rollup across programs. Scanned-image PDFs.