Skip to content
🧭 Meridian project operating desk

🧭 Meridian Project Workbench

Use this page when you want to work on the project rather than browse folders. It connects the DMBOK study system, Meridian company model, technology prerequisites, lab environment, applied labs, evidence, tracker, personal notes, and project documentation in one place.

Operating rule: GitHub is the version-controlled working desk. Google Drive remains a deliberate formatted-original/native-artifact archive where needed. The live Google Sheet remains the mutable tracker authority for now, while GitHub contains a readable mirror.

🚀 Start a work session

🏢Understand the companyOpen Meridian's company profile, processes, systems, domains, personas, defects and incidents.Open Meridian Casebook → 🧠Ground the work in DMBOKUse the controlling chapter before making a DAMA-specific claim, decision, design or interpretation.Open DMBOK Mastery → 🛠️Check technology readinessConfirm the SQL, PostgreSQL, DBeaver, Python/pandas, Git, data-format or later-tool competency required—and where to stop.Open Technology Roadmap → 🧰Open the working environmentUse the reproducible synthetic environment, SQL, Python, raw data, defect map, manifests, diagrams, outputs and rebuild controls.Open Environment Guide → 🧩Perform an applied labFollow predict → perform → interpret → vary/break → repair → independent rebuild → evidence → DMBOK debrief.Open Applied Labs → 📁Capture evidence & portfolio proofSave rerunnable logic, before/after results, decisions, diagrams, explanations and lab journals—not screenshots alone.Open Evidence System → 📝Write my working notesCapture informal observations, open questions, technology notes and decision thinking without mixing them into formal evidence or source pages.Open Meridian Notes → 📊Read the mastery registersBrowse the translated Google Sheet tabs—skills, labs, evidence, defects, decisions, datasets, software, capstones and sources—inside GitHub.Open Tracker Mirror →

📝 Document the project

🗒️ Project JournalSession history, what you tried, what changed and the exact next action. 📝 My Meridian NotesPersonal working notes, questions, technology memory and decision thinking. ⚖️ Decision RecordFormal company/project decision, options, rationale and ownership. 🧠 Lab JournalLab reflection, DMBOK debrief and independent rebuild notes. 📁 Evidence READMEExplain what evidence exists, what it proves and where it came from. 🏷️ Naming & Folder ConventionUse consistent names and placement for versionable evidence. 📊 GitHub Tracker MirrorReadable/searchable translation of every current live tracker tab. 🟢 Live Google TrackerCurrent mutable structured register authority until explicitly changed. 📦 Archive & Completion StatusVerify the required current source archive is complete and review tracker-mirror state, optional archives, and future migrations. 🔄 Drive ↔ GitHub ParityConfirm whether a Drive artifact is GitHub-native, external authority or future scaffold.

🎯 Current project boundary

  • 📘 DMBOK study packages: Chapters 1–17 are complete in Main 00A through current-source Artifacts 01–07.
  • 🧪 Meridian applied labs: Chapter 1 is the current substantively built executable chapter lab. Chapters 2–17 applied-lab folders in Drive are future/source-gated containers, not completed labs.
  • 🏢 Meridian casebook: online as GitHub-native pages and backed by the current Drive casebook source.
  • 🛠️ Technology roadmap: online as GitHub-native competency/readiness pages and backed by the current Drive roadmap/reference.
  • 🧰 Lab environment: working SQL/Python/synthetic-data assets live under repository /lab.
  • 📁 Evidence: versionable project evidence lives under repository /evidence.
  • 📝 Personal notes: live under docs/my-notes/ and are deliberately separate from formal evidence/source material.
  • 📊 Tracker: all live Sheet tabs have a GitHub-readable mirror; Google Sheet remains mutable authority until explicitly changed.
  • 📎 Source archive: the required current Applied-Lab PDF archive is complete; the Completion & Upload Checklist now tracks optional/future additions and deliberate external authorities.

🔄 Project operating loop

FRAME THE BUSINESS PROBLEM → CHECK DMBOK → CHECK TECHNOLOGY GATE → PREDICT → DO THE WORK → INTERPRET → WRITE PERSONAL NOTES IF USEFUL → RECORD FORMAL DECISIONS/DEFECTS → SAVE EVIDENCE → UPDATE TRACKER → DEBRIEF → NEXT ACTION

✅ Before doing work

  1. State the Meridian business problem in plain language.
  2. Identify the controlling DMBOK chapter or cross-domain areas.
  3. Check the relevant technology readiness gate.
  4. Decide what evidence should exist when the work is done.
  5. Predict the expected result before touching the tool.

📌 After doing work

  1. Save rerunnable logic/configuration where practical.
  2. Save results and before/after evidence.
  3. Record any decision, defect, dataset, software/setup change, or source update in the appropriate register/tracker.
  4. Write the DMBOK interpretation—not merely what buttons/commands were used.
  5. Use My Notes for personal understanding/questions; use formal evidence templates for project proof.
  6. Record the exact next action in the Project Journal.

🧭 Key project control documents

🚀 START HERE · 📘 Master Program Guide · ✅ Execution/Evidence/QC · 📚 Curriculum · 🏢 Casebook · 🛠️ Technology · 🧰 Environment · 🧪 Applied Labs · 📁 Evidence · 📊 Tracker Mirror · 📦 Completion Checklist · 📎 References

← 00B Home · 📝 My Notes · 🏠 Program Study Home