modify: order list to docs

ltndat · ltndat · commit 64d798a0d164 · 2025-06-15T14:01:43.000+07:00
diff --git a/docs/week-01-c.md b/docs/week-01-c.md
@@ -5,13 +5,13 @@
 > Protocol: Second Mind OS  
 > Format: Verified Thinking Notes + Schema-Driven Capture
 
-## Objective
+## 1. Objective
 
 - **Core Concept(s)**: What is being learned this week?
 - **Outcome**: What am I expected to produce or understand?
 - **Protocol Scope**: This note follows the PACER loop → it serves as a **Check + Reflect** anchor.
 
-## Concept Map / Schema
+## 2. Concept Map & Schema
 
 > Use this section to describe the concept using:
 
@@ -26,48 +26,48 @@ graph TD
   A --> D[Subcomponent 2]
 ```
 
-## Mental Models
+## 3. Mental Models
 
 | Concept         | Model / Metaphor                   | First-principle Breakdown         |
 | --------------- | ---------------------------------- | --------------------------------- |
 | \[e.g. Pointer] | "Memory arrow → points to a box"   | Address vs. value distinction     |
 | \[e.g. Stack]   | Stack = vertical tray, LIFO system | Memory ordering via frame context |
 
-## 📣 ⌬ Insight Claims
+## 4. 📣 ⌬ Insight Claims
 
 List insights that are **non-obvious**, and **must be claimed explicitly**, not just mentioned.
 
-| ⌬ ID | Claim Statement                              | Trigger Point | Verified In               |
-| ---- | -------------------------------------------- | ------------- | ------------------------- |
-| 001  | "A pointer holds an address, not the value"  | Lecture Q\&A  | `logs/YYYY-MM-DD-week-01-c.md`  |
-| 002  | "Refactoring reveals abstraction boundaries" | During pset   | `loop/week-01-c/pacer.yaml` |
+| ⌬ ID | Claim Statement                              | Trigger Point | Verified In                    |
+| ---- | -------------------------------------------- | ------------- | ------------------------------ |
+| 001  | "A pointer holds an address, not the value"  | Lecture Q\&A  | `logs/YYYY-MM-DD-week-01-c.md` |
+| 002  | "Refactoring reveals abstraction boundaries" | During pset   | `loop/week-01-c/pacer.yaml`    |
 
-## 🚧 Blockers / Ambiguities
+## 5. 🚧 Blockers & Ambiguities
 
 > List anything unclear, buggy, unresolved. These can be escalated into logs.
 
 - Why is stack memory auto-freed, but heap not?
 - Pointer vs reference distinction in C vs Rust?
 
-## 🧪 Tests / Self-Checks
+## 7. 🧪 Tests & Self-Checks
 
 > Add one or more test questions to check understanding
 
 1. Draw memory diagram of `int *p = &x;`, label addresses and values
 2. When does segmentation fault occur when using pointers?
 
-## 📃 Trace Log / Learning Path
+## 8. Trace Log & Learning Path
 
 - [x] Watched Lecture 1
 - [x] Read `Pointers in C` (CS50 Notes)
 - [x] Completed `pset1-Mario`
 - [ ] Created public output reflection
 - [ ] Shared ⌬ card with claim `001`
 
-## 🔁 Linked Protocol Loops
+## 9. 🔁 Linked Protocol Loops
 
-| Loop Phase | Linked File                  |
-| ---------- | ---------------------------- |
+| Loop Phase | Linked File                    |
+| ---------- | ------------------------------ |
 | Plan       | `loop/week-01-c/pacer.yaml`    |
 | Reflect    | `logs/YYYY-MM-DD-week-01-c.md` |
 
diff --git a/logs/YYYY-MM-DD-week-01-c.md b/logs/YYYY-MM-DD-week-01-c.md
@@ -1,6 +1,6 @@
 # Log — YYYY-MM-DD-topic-tag
 
-## 1. Focus Unit / Context
+## 1. Focus Unit & Context
 
 **Track:** [track-name]  
 **Week:** 01  
@@ -12,20 +12,20 @@
 - `loop/week-01-c/pacer.yaml`
 - `outputs/week-01-c/output.md`
 
-## 2. 🚧 Blockers / Bugs / Blindspots
+## 2. 🚧 Blockers, Bugs, and Blindspots
 
 - Infinite loop in `mario.c` when `n = 1` → stack overflow suspicion
 - Confusion about how `printf("\n")` interacts with loop count
 - Misunderstood `i--` vs `--i` inside nested loop
 
-## 3. 🛠️ Resolution / Fix Strategy
+## 3. 🛠️ Resolution & Fix Strategy
 
 - Used `printf("i: %d j: %d\n", i, j)` for trace-based debugging
 - Re-read CS50 walkthrough → matched with my code
 - Rewrote condition as: `for (int i = 0; i < height; i++)`  
   → Resolved control flow logic
 
-## 4. 📣 Insights / Claims (`⌬`)
+## 4. 📣 Insights & Claims (`⌬`)
 
 - ⌬ Loop order always reveals mental model: outer = rows, inner = cols
 - ⌬ Debugging = trace over theory → always anchor back to observable I/O
diff --git a/loop/week-01-c/claim.md b/loop/week-01-c/claim.md
@@ -1,6 +1,6 @@
 # ⌬ Claim — Week 01: [Topic]
 
-## 📣 Claim
+## 1. 📣 Claim
 
 - **Fact Lock-in**: (knowledge)  
   Eg: “I understand the difference between stack and heap memory.”
@@ -11,13 +11,13 @@
 - **Insight Shift**: (mindset / abstraction layer upgrade)  
   Eg: “Pointers are not just addresses — they represent indirection, which generalizes to references in high-level langs.”
 
-## Evidence
+## 2. Evidence
 
 - Verified via: [`logs/YYYY-MM-DD-week-01-c.md`](/logs/YYYY-MM-DD-week-01-c.md)
 - Output artifact: [`outputs/week-01-c/output.md`](/outputs/week-01-c/output.md)
 - Source of knowledge: CS50x Lectures + Pset1
 
-## Note
+## 3. Note
 
 This ⌬ **Mindstamp** represents a crystallized loop outcome.
 
diff --git a/loop/week-01-c/reflect.md b/loop/week-01-c/reflect.md
@@ -1,28 +1,28 @@
 # Reflect — Week 01: [Topic]
 
-## What clicked?
+## 1. What clicked?
 
 - <Summarize top insights, conceptual locks, or shifts in model.>
 
-## What was hard?
+## 2. What was hard?
 
 - <List where you struggled: mentally, technically, motivationally.>
 
-## What would you do differently?
+## 3. What would you do differently?
 
 - <What would your 3-days-ago self do better now?>
 
-## 🏛 Meta-level feedback
+## 4. 🏛 Meta-level feedback
 
 - Protocol friction: <Was PACER too heavy or helpful?>
 - System effectiveness: <Did the loop create clarity or chaos?>
 - Tooling: <What was missing? What worked well?>
 
-## Spillover
+## 5. Spillover
 
 - <How will this insight / habit affect other domains, workflows, or life decisions?>
 
-## Quote
+## 6. Quote
 
 > "Insert a quote or reflection sentence that encapsulates this week."
 
diff --git a/outputs/week-01-c/output.md b/outputs/week-01-c/output.md
@@ -1,33 +1,31 @@
 # Output — Week 01: [Topic]
 
-## Task
+## 1. Task
 
 - **Goal**: <Detail, measurable if any – eg. "Build a CLI tool to extract EXIF from images.">
 - **Type**: `code` / `writing` / `design` / `research` / `debug` / `review` / ...
 - **Trigger**: <Link or summary to Pacer/Claim/Mindstamp that initiated this>
 
-## Process Snapshot
+## 2. Process Snapshot
 
-### Problem Definition
+#### 2.1 Problem Definition
 
 <What was the core problem or user story you started with?>
 
-### Approach & Thought Process
+#### 2.2 Approach & Thought Process
 
 - Step-by-step reasoning / decision points
 - Tradeoffs considered
 - Why this method?
 
-### Tooling / Stack
+#### 2.3 Tooling / Stack
 
 - Langs / Libs used
 - Environments (e.g. Replit, VSCode, Colab)
 
----
-
-## Output Artifact
+## 3. Output Artifact
 
-### Deliverable
+#### 3.1 Deliverable
 
 Brief description — what did you make / produce?
 
@@ -36,43 +34,41 @@ Brief description — what did you make / produce?
 
 <Insert image or code snippet>
 
-## 🚫 Breakdown & Bugs
+## 4. 🚫 Breakdown & Bugs
 
-### Stucks / Bugs Hit
+#### 4.1 Stucks / Bugs Hit
 
 - Error messages, logical deadends, constraints hit
 - Root causes
 - Fixes attempted
 
-### Gaps / TODOs
+#### 4.2 Gaps / TODOs
 
 - What’s not done yet / edge cases skipped?
 - What needs refactor or test?
 
-## 🔁 Feedback Loop
+## 5. 🔁 Feedback Loop
 
-### What Changed After Feedback?
+#### 5.1 What Changed After Feedback?
 
 - Internal loop (self-review)
 - External (if feedback was received)
 - What was accepted / rejected / refined
 
-## Learning Summary
+## 6. Learning Summary
 
 - What skill got leveled up?
 - Any concepts clarified?
 - Any reusable insight or code pattern extracted?
 
-## Insight Card
+## 7. Insight Card
 
 - ⌬ Claim: `Memory tracing = 4-layer address mental model`
 - Situation: `While debugging segfault`
 - Impact: `Accelerated understanding of stack/heap`
 - Verified: [`logs/YYYY-MM-DD-week-01-c.md`](/logs/YYYY-MM-DD-week-01-c.md)
 
----
-
-## References
+## 8. References
 
 - Links to doc, forums, other outputs
 
