fix: name id & docs formatting & CLI tool;

Author: ltndat

README.md

@@ -27,15 +27,17 @@ This is the **official template** for constructing trackable learning systems fr
 
 ## Folder Structure
 
-| Folder       | Emoji | Role                                                  |
-| ------------ | ----- | ----------------------------------------------------- |
-| `docs/`      | 🗂️    | Schemas, maps, notes, distilled knowledge             |
-| `logs/`      | 📃    | Daily logs, blockers (`🚧`), insight pings            |
-| `loop/`      | 🔁    | P.A.C.E.R. loops: Plan → Act → Check → Edit → Reflect |
-| `outputs/`   | 🚀    | Public-facing artifacts: blog, repo, showcase         |
-| `track.json` |       | (Optional) Track metadata for integration             |
-| `LICENSE`    |       | MIT License                                           |
-| `README.md`  |       | This Document                                         |
+| Folder       | Symbol | Role                                                  |
+| ------------ | ------ | ----------------------------------------------------- |
+| `docs/`      | 🗂️     | Schemas, maps, notes, distilled knowledge             |
+| `logs/`      | 📃     | Daily logs, blockers (`🚧`), insight pings            |
+| `loop/`      | 🔁     | P.A.C.E.R. loops: Plan → Act → Check → Edit → Reflect |
+| `outputs/`   | 🚀     | Public-facing artifacts: blog, repo, showcase         |
+| `track.json` |        | (Optional) Track metadata for integration             |
+| `LICENSE`    |        | MIT License                                           |
+| `README.md`  |        | This Document                                         |
+
+> All symbols in this repo follow SMOS's [Naming Protocol Emoji](https://github.com/secondmindlab/secondmindlab/blob/19a71aa799d875c2b5dc4b7acda42394bb10f589/meta/naming-protocol-emoji.md). You can either keep this convention or adopt your own style.
 
 ## Protocol Flow
 
@@ -63,7 +65,7 @@ Each learning unit runs through the **P.A.C.E.R. loop** — a minimal feedback p
 | `Edit`    | Refactor, simplify, correct blindspots  |
 | `Reflect` | Meta-log insights, blockers, claims     |
 
-Each folder in `loop/Week-X/` should contain a `pacer.yaml` or markdown journal documenting this cycle.
+Each folder in `loop/week-xx-x/` should contain a `pacer.yaml` or markdown journal documenting this cycle.
 
 ## Usage Instructions
 
@@ -77,19 +79,19 @@ Each folder in `loop/Week-X/` should contain a `pacer.yaml` or markdown journal
    - New loop via CLI (Recommend) `python scripts/smos.py week-01-c --topic="Memory & Pointers"`
    - Drop notes into `docs/`
    - Write blockers / insight logs in `logs/`
-   - Launch a loop via `loop/week-01/pacer.yaml`, `loop/week-01/claim.md`, `loop/week-01/reflect.md`
+   - Launch a loop via `loop/week-01-c/pacer.yaml`, `loop/week-01-c/claim.md`, `loop/week-01-c/reflect.md`
    - Push deliverables to `outputs/`
 
 #### Example:
 
 ```bash
 track-cs50x/
-├── docs/week-01.md                  # Schema of memory model
-├── logs/YYYY-MM-DD-week-01.md       # Blocker resolution
-├── loop/week-01/pacer.yaml          # P.A.C.E.R. config
-├── loop/week-01/claim.md            # Distilled knowledge lock
-├── loop/week-01/reflect.md          # Meta-log & feedback
-├── outputs/week-01-output.md        # Artifact: reflection + code
+├── docs/week-01-c.md                  # Schema of memory model
+├── logs/YYYY-MM-DD-week-01-c.md       # Blocker resolution
+├── loop/week-01-c/pacer.yaml          # P.A.C.E.R. config
+├── loop/week-01-c/claim.md            # Distilled knowledge lock
+├── loop/week-01-c/reflect.md          # Meta-log & feedback
+├── outputs/week-01-c/output.md        # Artifact: reflection + code
 ```
 
 #### Naming Convention (Optional):

docs/week-01.md docs/week-01-c.mddocs/week-01.md renamed to docs/week-01-c.md

@@ -39,8 +39,8 @@ List insights that are **non-obvious**, and **must be claimed explicitly**, not
 
 | ⌬ ID | Claim Statement                              | Trigger Point | Verified In               |
 | ---- | -------------------------------------------- | ------------- | ------------------------- |
-| 001  | "A pointer holds an address, not the value"  | Lecture Q\&A  | `logs/2025-05-16-log.md`  |
-| 002  | "Refactoring reveals abstraction boundaries" | During pset   | `loop/week-01/pacer.yaml` |
+| 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
 
@@ -68,8 +68,8 @@ List insights that are **non-obvious**, and **must be claimed explicitly**, not
 
 | Loop Phase | Linked File                  |
 | ---------- | ---------------------------- |
-| Plan       | `loop/week-01/pacer.yaml`    |
-| Reflect    | `logs/YYYY-MM-DD-week-01.md` |
+| Plan       | `loop/week-01-c/pacer.yaml`    |
+| Reflect    | `logs/YYYY-MM-DD-week-01-c.md` |
 
 ---
 

logs/YYYY-MM-DD-week-01.md logs/YYYY-MM-DD-week-01-c.mdlogs/YYYY-MM-DD-week-01.md renamed to logs/YYYY-MM-DD-week-01-c.md

@@ -8,9 +8,9 @@
 **Current Phase:** Debug + Reflection  
 **Related files:**
 
-- `docs/week-01.md`
-- `loop/week-01/pacer.yaml`
-- `outputs/week-01-output.md`
+- `docs/week-01-c.md`
+- `loop/week-01-c/pacer.yaml`
+- `outputs/week-01-c/output.md`
 
 ## 2. 🚧 Blockers / Bugs / Blindspots
 
@@ -41,7 +41,7 @@
 
 ## 6. Next Steps
 
-- Update `outputs/week-01-output.md` with fixed version + ⌬ claims
+- Update `outputs/week-01-c/output.md` with fixed version + ⌬ claims
 - Start new PACER loop for Week-02
 - Share selected insight card to LinkedIn ("⌬ Debug = trace > theory")
 

loop/week-01/claim.md loop/week-01-c/claim.mdloop/week-01/claim.md renamed to loop/week-01-c/claim.md

@@ -13,8 +13,8 @@
 
 ## Evidence
 
-- Verified via: [`logs/YYYY-MM-DD-week-01.md`](../../logs/YYYY-MM-DD-week-01.md)
-- Output artifact: [`outputs/week-01-output.md`](../../outputs/week-01-output.md)
+- 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

loop/week-01/pacer.yaml loop/week-01-c/pacer.yamlloop/week-01/pacer.yaml renamed to loop/week-01-c/pacer.yaml

@@ -1,6 +1,6 @@
-# loop/week-01/pacer.yaml
+# loop/week-01-c/pacer.yaml
 
-loop_id: week-01
+loop_id: week-01-c
 title: '[PROJECT / PS]: <Name of Project, Problem Set, or Concept>'
 date_started: 2025-05-18
 date_finished: null

loop/week-01/reflect.md loop/week-01-c/reflect.mdloop/week-01/reflect.md renamed to loop/week-01-c/reflect.md

@@ -68,15 +68,15 @@ Brief description — what did you make / produce?
 - ⌬ 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.md`](../logs/YYYY-MM-DD-week-01.md)
+- Verified: [`logs/YYYY-MM-DD-week-01-c.md`](../logs/YYYY-MM-DD-week-01-c.md)
 
 ---
 
 ## References
 
 - Links to doc, forums, other outputs
 
-> 📏 **Protocol Tag**: `Verified: logs/YYYY-MM-DD-week-01.md`  
+> 📏 **Protocol Tag**: `Verified: logs/YYYY-MM-DD-week-01-c.md`  
 > 📣 ⌬ Claim Origin: `"Pointer tracing = mental model of memory layers"`
 
 ---

outputs/week-01-output.md outputs/week-01-c/output.mdoutputs/week-01-output.md renamed to outputs/week-01-c/output.md

@@ -81,7 +81,7 @@ def init_loop(loop_id, topic):
         TEMPLATE_REFLECT.format(loop_id=loop_id, topic=topic),
     )
     create_file(
-        f"outputs/{loop_id}/{loop_id}-output.md",
+        f"outputs/{loop_id}/output.md",
         TEMPLATE_OUTPUT.format(loop_id=loop_id, topic=topic, today=today),
     )
 
@@ -90,7 +90,7 @@ def init_loop(loop_id, topic):
     parser = argparse.ArgumentParser(
         description="Initialize a new SMOS learning loop."
     )
-    parser.add_argument("loop_id", type=str, help="Loop ID (e.g. week-01)")
+    parser.add_argument("loop_id", type=str, help="Loop ID (e.g. week-01-c)")
     parser.add_argument(
         "--topic", type=str, required=True, help="Topic or focus of the loop"
     )