🔄 Applied Laboratory — Drive ↔ GitHub Parity Map

Drive root audited: CDMP Applied Data Management Laboratory

This page answers: “If I see something in the Applied Laboratory Drive, where is it in GitHub?”

Parity summary

The current substantive Applied Laboratory content is now available in GitHub as version-controlled Markdown/working assets, and the 12 current formatted source PDFs are also archived locally under source-pdfs/.

Three states still matter:

GitHub-native ✅ — substantive content is available directly in the repository/site.
Linked authority 🔗 — a live/native Google artifact remains intentionally external, such as the editable Google Sheet tracker or editable Google Docs.
Drive scaffold 🗂️ — a Drive folder exists as an empty/future working container; there is no substantive file to migrate yet.

Root section map

Drive area	GitHub location	State	Notes
`00 — START HERE`	`start-here.md`	✅ + 🔗	Operating content is GitHub-native; formatted source PDF is local; Google Doc remains a native backup/editable original.
`00A — Applied Lab Internal Program Control & Build Specification`	`control/`	✅ + 🔗	Master Program Guide and Execution/Evidence/QC Standard are GitHub-native; both formatted PDFs are local.
`01 — Program Curriculum & Roadmaps`	`curriculum/`	✅ + 🔗	Curriculum is GitHub-native; formatted curriculum-map PDF is local.
`02 — Meridian Company & Casebook`	`meridian-casebook/`	✅ + 🔗	Casebook is GitHub-native; formatted casebook PDF is local.
`03 — Technology Training & Competency Roadmap`	`technology/`	✅ + 🔗	Competency roadmap/reference are GitHub-native and both PDFs are local.
`04 — Lab Environment, Data & Setup`	`environment/` + `/lab`	✅ + 🔗	Environment guidance and working SQL/Python/data assets are in GitHub; both environment PDFs are local.
`05 — Applied Labs`	`applied-labs/`	✅ + 🔗 + 🗂️	Chapter 1 is the current built applied lab; its PDF and the capstone roadmap PDF are local. Chapters 2–17 remain future/source-gated containers.
`06 — Evidence, Portfolio, Trackers & Templates`	`evidence/` + `/evidence`	✅ + 🔗	Evidence guidance is GitHub-native. The live Google Sheet remains mutable authority, with a GitHub-readable mirror.
`99 — Reference Sources & Borrowed Patterns`	`reference/`	✅ + 🔗	Borrowed-pattern/source notes are GitHub-native and the formatted PDF is local.

Formatted source archive

All 12 current formatted Applied Laboratory PDFs are now locally archived and indexed here:

📎 Open Applied Laboratory Source PDF Archive

The Google-native Docs remain useful as editable originals, but there is no longer a current Applied-Lab PDF source-archive gap.

Drive folders that are scaffolding, not missing migrations

Several Drive folders were checked and found to contain no substantive files. Examples include Meridian company/process/system working subfolders, an empty SQL Foundations learning-area folder, an empty Microsoft Purview working folder, and an empty Evidence/Portfolio/Lab Journal folder.

Do not treat these as missing migrations. They become real GitHub work areas when substantive content is created.

Live tracker — intentionally external mutable authority

The CDMP Applied Lab & Technology Mastery Tracker remains a Google Sheet for structured status/register updates. GitHub now has a readable mirror of every active tab and the hidden legacy sequence.

The mirror is a snapshot, not automatic two-way sync. When the live Sheet changes, refresh the corresponding GitHub mirror page.

Current remaining gaps

There is no current required Applied-Lab source-PDF upload gap.

What remains by design:

Google-native editable Docs/Sheet can stay external when their native format is useful.
Future Chapter 2–17 Meridian applied labs are added only when substantive lab content is actually authored.
Optional formatted duplicates of already-converted Chapter 1–17 study artifacts remain optional, not required for learning-content completeness.

Project-work entry point

For day-to-day work, use the Meridian Project Workbench rather than navigating this parity table.

📦 Full Program Completion Checklist