Diagram Provenance
This directory contains checked-in standalone HTML architecture diagrams embedded by
docs/architecture.md and copied into the MkDocs site/ build.
1. Current Artifacts
ml-eng-lab-system.htmldescribes the repository context and primary components.ml-eng-lab-runtime-flow.htmldescribes supported runtime entry paths and task-local notebook artifact paths.ml-eng-lab-notebook-sequence.htmltraces notebook execution from parameters through training, ranking, visualization, persistence, and verification.ml-eng-lab-docs-publishing.htmldescribes README, docs, MkDocs, GitHub Pages, wiki, and repository metadata surfaces.
2. Generation Contract
These diagrams were produced as dark, standalone HTML/SVG architecture artifacts using the repository maintenance run's approved architecture-diagram workflow. The checked-in HTML files are the source of truth for the current rendered site; do not hand-edit generated geometry without updating this provenance note in the same change.
When a diagram needs to change:
- Regenerate the affected HTML artifact with the same dark technical style, landscape layout, embedded SVG, and no external runtime JavaScript.
- Confirm
docs/architecture.mdstill embeds and links the artifact. - Run
make docs-buildand compare the generatedsite/diagrams/*.htmlcopies todocs/diagrams/*.html. - Inspect the rendered diagram at normal browser zoom for overlapping labels, boxes, legends, or arrows before committing.
3. Review Rules
- Diagram content must describe the current repository behavior, not aspirational design.
- Arrows and labels should remain readable on desktop and narrow screens.
- New architecture, runtime, notebook-flow, or documentation-publishing changes should update the matching diagram in the same pull request.