Skip to content
🧪 Meridian Commerce Group • Applied Data Management Laboratory

🏢 Meridian Project Lab

This is the project side of the CDMP system. Use it to turn DMBOK theory into company decisions, SQL/Python work, governance artifacts, evidence, defects, and a documented portfolio trail.

FRAME → GROUND IN DMBOK → PREDICT → DO → INTERPRET → PROVE → DEBRIEF

🧭 Project Workbench 🏢 Company Casebook 🧪 Applied Labs 📁 Evidence 📝 Project Journal 🔄 Source Parity

🚀 Start project work here

🧭 Open the Project WorkbenchThe day-to-day control desk: company context, DMBOK grounding, technology gates, environment, labs, evidence, tracker, decisions, sources and next actions.Open Project Workbench → 🏢 Understand MeridianLearn the persistent fictional company, processes, systems, personas, data domains, defects and incidents before touching tools.Open Meridian Casebook → 🛠️ Check technology readinessSee what SQL, PostgreSQL, DBeaver, Python/pandas, Git or later-tool skill is actually required—and where to stop.Open Technology Roadmap → 🧪 Perform applied workEnter the current source-gated chapter labs and cross-chapter capstone roadmap.Open Applied Labs → 📁 Save evidence & portfolio proofUse evidence standards, journal templates, decision records, naming rules and the live tracker.Open Evidence System → 🔄 Check Drive ↔ GitHub paritySee which Drive materials are GitHub-native, which remain live Google authorities, and which folders are only future scaffolding.Open Parity Map →

🧱 Project system map

📘 01 — Curriculum & RoadmapsWhat the chapter-to-lab program is designed to build. 🏢 02 — Meridian CasebookCompany, processes, systems, domains, roles, defects and incidents. 🛠️ 03 — Technology CompetencyRequired skill depth, readiness gates and stop boundaries. 🧰 04 — Lab EnvironmentSynthetic data, SQL, Python, manifests, diagrams and rebuild controls. 🧪 05 — Applied LabsSource-grounded project exercises and future cross-domain work. 📁 06 — Evidence & PortfolioProof of work, project records, templates and tracking. 📎 99 — Reference SourcesStructural references and source-control rules that never override DMBOK authority. 🧭 Internal Control CenterRules for building, evidencing and quality-checking the lab system itself.

📝 Where project work is recorded

What happened Record it here
🗒️ Session narrative / next action Project Journal
💻 SQL, Python, synthetic data, manifests Private GitHub /lab
📁 Versionable proof/evidence Private GitHub /evidence
⚖️ Formal company/project decision Decision Record Template
🧠 Lab debrief / reflection Lab Journal Template
📊 Skills, labs, evidence, defects, decisions, datasets, software and capstones Live Applied Lab & Technology Mastery Tracker
🔄 Source completeness / Drive relationship Drive ↔ GitHub Parity Map

🧠 Core operating rule

Technology is never the lesson by itself. The DMBOK concept is the lesson. Technology gives you a way to see, test, build, break, repair, trace, measure or explain that concept.

DMBOK THEORY → TECHNOLOGY SKILL → MERIDIAN BUSINESS PROBLEM → HANDS-ON WORK → EVIDENCE → DMBOK DEBRIEF

🎛️ Authority split

  • 📘 Main 00A — DMBOK source fidelity, learning, retrieval and exam mastery.
  • 🧪 Main 00B — Meridian lab design, evidence, independence and applied-project QC.
  • 🧭 Main 00C — exact learner sequence across study and labs.
  • 🚪 Main 00 — short navigation doorway.

For normal progression, open 00C. For project work, stay here and use the Project Workbench.