Skip to content

📦 Full Program GitHub Completion & Upload Checklist

Goal: make the private GitHub repository/site sufficient for day-to-day studying, project work, personal notes, evidence, source review, tracker/reference lookup, and source archival without relying on memory about what still lives only in Google Drive.

✅ Current required-content status

The current required source archive is now complete.

Verified in GitHub commit a36579ee894b28d09ad69a94f8aa4f4c0a65c08d:

  • 17 original DMBOK Chapter 1–17 source PDFs — already local under each chapter's source/original-dmbok-chapter.pdf.
  • 2 DMBOK Mastery governing PDFs — local under 00A-dmbok-mastery/source-pdfs/.
  • 4 DMBOK front/back-matter PDFs — local under 00A-dmbok-mastery/front-back-matter/.
  • 12 current Applied Laboratory formatted source PDFs — local under source-pdfs/.
  • DMBOK Chapters 1–17 substantive study content — GitHub-native Markdown.
  • Meridian/Applied Lab substantive program-control, curriculum, casebook, technology, environment, Chapter 1 lab, capstone, evidence, and reference content — GitHub-native Markdown/working assets.
  • Private Notes system — GitHub-native.
  • Applied Lab & Technology Mastery Tracker — every current tab translated into the GitHub-readable Tracker Mirror.
  • Hidden legacy 100-step tracker tab — preserved as archive/history only; current 00C remains execution authority.

Required current source PDFs still missing: 0.

📎 Current source archive entry points

🔄 Google Sheet translation — current state

Live mutable authority: CDMP Applied Lab & Technology Mastery Tracker
Spreadsheet ID: 1IEysqWHYQfQ9Rhh_owdMo_N1ab-qpmt9oQ1MdbG-l10

GitHub-readable mirror:

docs/00B-meridian-lab/evidence/tracker-mirror/

Mirrored tabs:

  • START HERE
  • TECHNOLOGY SKILLS
  • CHAPTER LABS
  • LAB EVIDENCE
  • DEFECT CATALOG
  • COMPANY DECISIONS
  • DATASET REGISTER
  • SOFTWARE SETUP
  • CROSS-CHAPTER CAPSTONES
  • SOURCES
  • hidden LEGACY 100-STEP EXECUTION as archive/history only

Synchronization rule

The GitHub mirror is a readable snapshot, not automatic two-way synchronization. When the live Sheet changes, re-read the changed tab and refresh the matching GitHub page.

No manual upload of the Sheet is required for translation. A frozen .xlsx export is optional if a binary archive is later desired.

📝 Notes system — complete

The private Notes system includes:

  • quick-capture inbox;
  • Chapter 1–17 personal note pages;
  • Meridian/project notes;
  • technology notes;
  • project questions/decisions;
  • exam confusion and missed-question notes;
  • source-review notes.

Use 📝 My Notes rather than editing authoritative teaching/source pages with personal annotations.

📚 Optional full formatted-original Chapter 1–17 artifact archive

There is still an optional duplicate archive if the goal becomes literal storage of every formatted Chapter 1–17 study artifact PDF.

For each Chapter 1–17, the optional formatted copies are:

  1. Guided Learning
  2. Exam Map
  3. Visual Memory Map / Atlas
  4. Battle Cards
  5. Scenario Lab
  6. Chapter Question Bank
  7. Teach-Back / Recall

That is 7 PDFs × 17 chapters = 119 optional PDFs.

These are not required for learning-content completeness because their substantive content is already GitHub-native. Upload them only if you want every formatted duplicate physically archived too.

🗂️ No upload needed for empty/future scaffolding

Do not create fake completeness by uploading empty placeholder folders. Future Chapter 2–17 Meridian applied-lab containers and other empty Drive work areas become real only when substantive work/files are created.

🧪 Future Applied Lab rule

As Chapters 2–17 Meridian applied labs are authored, add:

  • GitHub-native lab instructions/artifacts;
  • working code/data/evidence where appropriate; and
  • the formatted source PDF if one is created.

Do not mark an applied lab complete merely because the corresponding DMBOK study chapter is complete.

✅ Definition of “GitHub can be used for everything”

For the current program state, the core goal is now met when using GitHub as the daily operating system:

  • study content is readable/searchable;
  • all current required source PDFs are local;
  • tracker/register information is readable through the GitHub mirror;
  • personal notes are writable/versioned;
  • project journal, decisions, evidence, datasets, defects, software status and capstones are discoverable;
  • Google-native artifacts remain external only by deliberate design, not because their location/content was forgotten.

What remains ongoing is program growth, not a migration backlog: future Meridian labs, evidence, notes, decisions, tracker refreshes, and optional formatted duplicates.

🔄 Drive ↔ GitHub Parity Map · 🧭 Project Workbench · 📊 Tracker Mirror · 📝 My Notes