🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →
Source: 00C canonical Google Doc. This page preserves the execution-card content while GitHub provides navigation.
Sequence 005 - Understand the evidence and portfolio rule
Program Orientation | Orientation
| WHEN / PURPOSE — Know what counts as proof of learning before labs start. |
|---|
WHAT YOU SHOULD LEARN
- Evidence must show your reasoning, not merely a finished file.
- Raw inputs remain unchanged.
- Decisions, assumptions and before/after states matter.
- Screenshots are supporting evidence, not the whole proof.
WHAT TO READ / STUDY
| Priority | Resource | Open | Use now | Stop point |
|---|---|---|---|---|
| MUST | Applied Lab Execution, Evidence & QC Standard | OPEN | Review required lab sections and evidence standard. | Do not create fake evidence. |
| MUST | Master Tracker | OPEN | Locate evidence-link fields and lab journal areas. | Do not mark status complete prematurely. |
DO THIS IN ORDER
- Identify where lab evidence will live.
- Create a naming pattern for chapter evidence.
- Decide what will be saved as source, working copy, output and explanation.
- Write the rule for screenshots and scripts.
MERIDIAN APPLICATION
Every Meridian lab will leave a small audit trail showing what you observed, decided, changed and learned.
STOP / BOUNDARY: Stay inside the current source/skill boundary. Do not pre-learn later chapters or engineering depth.
CREATE / SAVE
Evidence naming convention.
YOU ARE DONE WHEN: You can distinguish output from evidence from reflection.
NEXT → Sequence 006
🏠 Dashboard · ☑ Progress · 🔎 Finder · 📚 Block · ← Previous · Next →