Schedule data loop (spike): schema, validator, importer, MMED 2025, CI gate (#54) - #25
Closed
WestonVoglesonger wants to merge 1 commit into
Closed
Conversation
…25, CI gate Phase 1 proof-of-concept for #54 (epic #58). The clinic schedule becomes one flat YAML per cohort-year (_data/schedule/<clinic>/<year>.yml), validated by a gating CI check, instead of a live-edited Liquid wall. - schemas/schedule-cohort.schema.json: Tier 0 schema (closed kind enum, quoted date/time asserts, per-kind required fields, instructorKey forbids '|'). - tools/validate_schedule.py: Tier 0 + Tier 1 (people resolution, scoped non-overlap, end>=start, timezone, TODO closure). - tools/import_schedule.py: one-shot Liquid-wall -> cohort YAML; never drops a line (unmappable -> kind: todo, which hard-fails Tier 1 loudly). - _data/schedule/roles.yml + _data/schedule/mmed/2025.yml (migrated, validates green: 0 errors). - .github/workflows/schedule-validate.yml: the PR gate the existing jekyll.yml build cannot provide (a broken schedule still builds green today). Topology-independent per DESIGN.md; final placement of shared machinery is the #56 decision. Companion renderer PR in ICI3D.github.io.
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Schedule data loop (spike / draft POC) — #54
Phase 1 proof-of-concept for #54 (epic #58). Not final architecture; opening for review of the mechanism, per DESIGN.md.
What this is
The clinic schedule becomes one flat YAML per cohort-year at
_data/schedule/<clinic>/<year>.yml, validated by a gating CI check, instead of a live-edited Liquid wall on the deploy branch. Mirrors the_data/team/*.yml->profile.htmlpattern.In this PR
schemas/schedule-cohort.schema.json— Tier 0 schema (closedkindenum with a genericactivity, quoted"HH:MM"/ISO-datetype: stringasserts, per-kind required fields,instructorKeyforbids|).tools/validate_schedule.py— Tier 0 (schema) + Tier 1 (people resolution vs_data/team+roles.yml, scoped per-track non-overlap,end >= start, timezone, TODO closure). Emits::errorannotations.tools/import_schedule.py— one-shot Liquid-wall -> cohort YAML; never drops a line (unmappable rows becomekind: todo, which hard-fails Tier 1 loudly)._data/schedule/roles.yml+_data/schedule/mmed/2025.yml— the migrated MMED 2025 cohort, validates green (0 errors)..github/workflows/schedule-validate.yml— the PR gate the existingjekyll.ymlbuild cannot provide (a broken schedule still builds green today, e.g. an undefined{{ mlect }}renders empty).Proves
Importer runs on the real MMED 2025 source and the result validates
0 error(s), 0 warning(s); unmappable lines survive loudly astodorather than vanishing.Not decided here
Topology-independent per the design. Final placement of the shared machinery (renderer + validator) is the #56 decision (Carl's call). Companion renderer PR in ICI3D/ICI3D.github.io.