🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 007 - Inspect the lab environment without installing everything
Program Orientation | Orientation
| WHEN / PURPOSE — Know what already exists before any installation work. |
|---|
WHAT YOU SHOULD LEARN
- Synthetic source data is already available.
- Bootstrap scripts exist.
- Core software may still be uninstalled.
- Later tools are deliberately deferred.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Lab Environment, Data & Setup folder | OPEN | Inspect folder structure, blueprints and existing files. | Do not install software yet. |
| MUST | Master Tracker | OPEN | Check SOFTWARE SETUP and DATASET REGISTER. | Read only; do not mark installed unless true. |
DO THIS IN ORDER
- Confirm synthetic source-data files exist.
- Confirm SQL/Python bootstrap artifacts exist.
- Identify current software status.
- Record any desktop-path decision you will use later.
MERIDIAN APPLICATION
You are establishing a baseline so later installation sequences are deliberate and reproducible.
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Environment baseline checklist.
YOU ARE DONE WHEN: You know what exists, what is missing and what is intentionally deferred.
NEXT → Sequence 008
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →