Skip to content

Commit ab5eab6

Browse files
ltndatltndat
committed
publish: track template protocol v1.0;
1 parent 82c727f commit ab5eab6

File tree

9 files changed

+552
-1
lines changed

9 files changed

+552
-1
lines changed

‎.github/workflows/export-track-manifest.yml‎

Whitespace-only changes.

‎README.md‎

Lines changed: 130 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,130 @@
1-
# track-template
1+
# Track Template by Second Mind OS (SMOS)
2+
3+
> Track your thinking. Loop your learning. Build public artifacts. Powered by SMOS.
4+
5+
**Canonical template** for learning tracks, project-based skill loops, and knowledge pipelines in the 🧱 Second Mind OS Lab.
6+
7+
## Purpose
8+
9+
**`Learning = self-directed systems + protocol discipline + public artifacts`**
10+
11+
> Maximize your leverage. Build your cognitive stack. Ship high-signal work.
12+
13+
This is not a note-taking system.
14+
This is not a journaling habit.
15+
This is a **feedback loop protocol** — to think clearer, track deeper, and verify what you actually know.
16+
17+
This is the **official template** for constructing trackable learning systems from any course, project, or domain. Use this to:
18+
19+
- Structure your learning as **iteration cycles**, not passive consumption, verification (via P.A.C.E.R. protocol)
20+
- Produce **trackable insights**, not fleeting thoughts, log-traceable progression
21+
- Ship **public artifacts**, not private illusions
22+
- Crystallize ⌬ **Mindstamps** — reusable thinking units, based on Second Mind OS OVL Protocol
23+
24+
> Fork this repo to convert any study path into a systemized execution protocol.
25+
26+
---
27+
28+
## Folder Structure
29+
30+
| Folder | Emoji | Role |
31+
| ------------ | ----- | ----------------------------------------------------- |
32+
| `docs/` | 🗂️ | Schemas, maps, notes, distilled knowledge |
33+
| `logs/` | 📃 | Daily logs, blockers (`🚧`), insight pings |
34+
| `loop/` | 🔁 | P.A.C.E.R. loops: Plan → Act → Check → Edit → Reflect |
35+
| `outputs/` | 🚀 | Public-facing artifacts: blog, repo, showcase |
36+
| `track.json` | | (Optional) Track metadata for integration |
37+
| `LICENSE` | | MIT License |
38+
| `README.md` | | This Document |
39+
40+
## Protocol Flow
41+
42+
```mermaid
43+
graph TD
44+
A[Engage with Content] --> B[Build Project / Problem]
45+
B --> C[P.A.C.E.R. Loop]
46+
C --> D[Write Logs + Loop Claim]
47+
D --> E[Claim ⌬ Symbol]
48+
E --> F[Public Output in outputs/]
49+
F --> G[Emit JSON to Personal Site]
50+
```
51+
52+
#### 🔁 P.A.C.E.R. Loop Protocol
53+
54+
Each learning unit runs through the **P.A.C.E.R. loop** — a minimal feedback protocol for deliberate skill formation:
55+
56+
| Stage | Function |
57+
| --------- | --------------------------------------- |
58+
| `Plan` | Define objective, scope, and constraint |
59+
| `Act` | Execute, build, engage with material |
60+
| `Check` | Self-test, validate via examples/tests |
61+
| `Edit` | Refactor, simplify, correct blindspots |
62+
| `Reflect` | Meta-log insights, blockers, claims |
63+
64+
Each folder in `loop/Week-X/` should contain a `pacer.yaml` or markdown journal documenting this cycle.
65+
66+
## Usage Instructions
67+
68+
1. **Fork this template** → rename to `USERNAME/[course|domain]` or `USERNAME/track-[course|domain]`
69+
e.g.: track-cs50x, track-ml-zero, track-rust-os
70+
71+
2. **Optional: Enable GitHub Pages**
72+
→ Serve `outputs/` as public-facing artifacts
73+
74+
3. **Loop Structure**
75+
76+
- Drop notes into `docs/`
77+
- Launch a loop via `loop/week-01/pacer.yaml`
78+
- Push deliverables to `outputs/`
79+
- Write blockers / insight logs in `logs/`
80+
81+
#### Example
82+
83+
```bash
84+
track-cs50x/
85+
├── docs/week-01.md # Schema of memory model
86+
├── loop/week-01/pacer.yaml # P.A.C.E.R. config
87+
├── outputs/pset1-mario.md # Artifact: reflection + code
88+
├── logs/2025-05-16-pointer-log.md # Blocker resolution
89+
```
90+
91+
#### Naming Convention (Optional)
92+
93+
Track repos should follow:
94+
95+
```txt
96+
[course|domain|theme]
97+
track-[course|domain|theme]
98+
```
99+
100+
Examples:
101+
102+
- `cs50x`
103+
- `openai-fine-tune`
104+
- `track-ml-zero`
105+
- `track-rust-os`
106+
- `track-freecodecamp-js`
107+
108+
Use as **public fork base** for consistent naming across teams/orgs.
109+
110+
#### Recommended Add-ons
111+
112+
- [ ] GitHub Actions for JSON metadata export
113+
- [ ] Auto-log CLI script (`log "note here"`)
114+
- [ ] Auto-site render via `outputs/` → `gh-pages`
115+
116+
## License
117+
118+
MIT — use freely under your personal or team workflows.
119+
120+
> **Note**: All forks must include the following in `README.md`:
121+
> _Powered by [**Second Mind OS Lab**](https://github.com/secondmindlab) — Protocol-first learning system for cognitive leverage._
122+
123+
## Maintained by
124+
125+
**🧱 Second Mind OS Lab**
126+
Protocol harmony, cognitive precision, outcome-driven learning.
127+
128+
⚓ Personal mastery is system-driven. Track everything. Reflect ruthlessly. Ship deliberately.
129+
130+
> _Powered by [**Second Mind OS Lab**](https://github.com/secondmindlab) — Protocol-first learning system for cognitive leverage._

‎docs/week-01.md‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
# Week 01 — [Insert Topic Title Here]
2+
3+
> Track: [track-name]
4+
> Week: 01
5+
> Protocol: Second Mind OS
6+
> Format: Verified Thinking Notes + Schema-Driven Capture
7+
8+
## OBJECTIVE
9+
10+
- **Core Concept(s)**: What is being learned this week?
11+
- **Outcome**: What am I expected to produce or understand?
12+
- **Protocol Scope**: This note follows the PACER loop → it serves as a **Check + Reflect** anchor.
13+
14+
## CONCEPT MAP / SCHEMA
15+
16+
> Use this section to describe the concept using:
17+
18+
- Bullet schemas
19+
- Diagrams (Mermaid or ASCII)
20+
- Causal chains
21+
22+
```mermaid
23+
graph TD
24+
A[High-Level Concept] --> B[Subcomponent 1]
25+
B --> C[Example / Application]
26+
A --> D[Subcomponent 2]
27+
```
28+
29+
## MENTAL MODELS
30+
31+
| Concept | Model / Metaphor | First-principle Breakdown |
32+
| --------------- | ---------------------------------- | --------------------------------- |
33+
| \[e.g. Pointer] | "Memory arrow → points to a box" | Address vs. value distinction |
34+
| \[e.g. Stack] | Stack = vertical tray, LIFO system | Memory ordering via frame context |
35+
36+
## ⌬ INSIGHT CLAIMS
37+
38+
List insights that are **non-obvious**, and **must be claimed explicitly**, not just mentioned.
39+
40+
| ⌬ ID | Claim Statement | Trigger Point | Verified In |
41+
| ---- | -------------------------------------------- | ------------- | ------------------------- |
42+
| 001 | "A pointer holds an address, not the value" | Lecture Q\&A | `logs/2025-05-16-log.md` |
43+
| 002 | "Refactoring reveals abstraction boundaries" | During pset | `loop/week-01/pacer.yaml` |
44+
45+
## 🚧 BLOCKERS / AMBIGUITIES
46+
47+
> List anything unclear, buggy, unresolved. These can be escalated into logs.
48+
49+
- Why is stack memory auto-freed, but heap not?
50+
- Pointer vs reference distinction in C vs Rust?
51+
52+
## 🧪 TESTS / SELF-CHECKS
53+
54+
> Add one or more test questions to check understanding
55+
56+
1. Draw memory diagram of `int *p = &x;`, label addresses and values
57+
2. When does segmentation fault occur when using pointers?
58+
59+
## 📃 TRACE LOG / LEARNING PATH
60+
61+
- [x] Watched Lecture 1
62+
- [x] Read `Pointers in C` (CS50 Notes)
63+
- [x] Completed `pset1-Mario`
64+
- [ ] Created public output reflection
65+
- [ ] Shared ⌬ card with claim `001`
66+
67+
## 🔁 LINKED PROTOCOL LOOPS
68+
69+
| Loop Phase | Linked File |
70+
| ---------- | -------------------------------- |
71+
| Plan | `loop/week-01/pacer.yaml` |
72+
| Reflect | `logs/2025-05-16-pointer-log.md` |
73+
74+
> _Powered by [**Second Mind OS Lab**](https://github.com/secondmindlab) — Protocol-first learning system for cognitive leverage._

‎logs/YYYY-MM-DD-week-01.md‎

Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
# Log — YYYY-MM-DD-topic-tag
2+
3+
## 1. Focus Unit / Context
4+
5+
**Track:** [track-name]
6+
**Week:** 01
7+
**Problem:** `pset1-mario`
8+
**Current Phase:** Debug + Reflection
9+
**Related files:**
10+
11+
- `docs/week-01.md`
12+
- `loop/week-01/pacer.yaml`
13+
- `outputs/pset1-mario.md`
14+
15+
## 2. 🚧 Blockers / Bugs / Blindspots
16+
17+
- Infinite loop in `mario.c` when `n = 1` → stack overflow suspicion
18+
- Confusion about how `printf("\n")` interacts with loop count
19+
- Misunderstood `i--` vs `--i` inside nested loop
20+
21+
## 3. 🛠️ Resolution / Fix Strategy
22+
23+
- Used `printf("i: %d j: %d\n", i, j)` for trace-based debugging
24+
- Re-read CS50 walkthrough → matched with my code
25+
- Rewrote condition as: `for (int i = 0; i < height; i++)`
26+
→ Resolved control flow logic
27+
28+
## 4. 📣 Insights / Claims (`⌬`)
29+
30+
- ⌬ Loop order always reveals mental model: outer = rows, inner = cols
31+
- ⌬ Debugging = trace over theory → always anchor back to observable I/O
32+
- ⌬ Bugs are often off-by-one mindset blindspots, not syntax
33+
34+
## 5. 🏛 Meta Reflection (System Layer)
35+
36+
> What did I learn about how I learn?
37+
38+
- I waste time when I try to “figure it out in my head” — should **externalize state early**
39+
- Debug logs are 10x leverage over mental simulation
40+
- From now on, I’ll use trace-dump before asking GPT or rereading docs
41+
42+
## 6. Next Steps
43+
44+
- Update `outputs/pset1-mario.md` with fixed version + ⌬ claims
45+
- Start new PACER loop for Week-02
46+
- Share selected insight card to LinkedIn ("⌬ Debug = trace > theory")
47+
48+
---
49+
50+
**Powered by Second Mind OS** — _Log-traceable insight loops for deep learning._

‎loop/week-01/claim.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# ⌬ Claim — Week 01
2+
3+
## 📣 Claim
4+
5+
- **Fact Lock-in**: (kiến thức đúng)
6+
Eg: “I understand the difference between stack and heap memory.”
7+
8+
- **Skill Capability**: (có thể hành động được)
9+
Eg: “I can debug null-pointer segfaults in C using `valgrind` and logical tracing.”
10+
11+
- **Insight Shift**: (mindset / abstraction layer nâng cấp)
12+
Eg: “Pointers are not just addresses — they represent indirection, which generalizes to references in high-level langs.”
13+
14+
## Evidence
15+
16+
- Verified via: [`logs/2025-05-18-pointer-log.md`](../../logs/2025-05-18-pointer-log.md)
17+
- Output artifact: [`outputs/pset1-mario.md`](../../outputs/pset1-mario.md)
18+
- Source of knowledge: CS50x Lectures + Pset1
19+
20+
## Note
21+
22+
This ⌬ **Mindstamp** represents a crystallized loop outcome.
23+
24+
> Powered by **Second Mind OS**

‎loop/week-01/pacer.yaml‎

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
# loop/week-01/pacer.yaml
2+
3+
loop_id: week-01
4+
title: '[PROJECT / PS]: <Name of Project, Problem Set, or Concept>'
5+
date_started: 2025-05-18
6+
date_finished: null
7+
status: 'in-progress' # or: done, skipped, blocked
8+
9+
pacer:
10+
plan:
11+
objective: '<What is the goal of this unit?>'
12+
scope: '<What does it include/exclude?>'
13+
constraints: '<Time, resource, context limits>'
14+
15+
act:
16+
actions_taken:
17+
- '<Study content, read paper, build small app, etc>'
18+
- '<What experiments or projects were done?>'
19+
tools_used: '<IDE, language, library, notebook...>'
20+
21+
check:
22+
self_test: '<How was the work tested or verified?>'
23+
key_mistakes:
24+
- '<What went wrong or revealed blindspots?>'
25+
- '<Debugging or concept gaps?>'
26+
27+
edit:
28+
what_was_refactored:
29+
- '<Code cleanups, structural rewrites, simplified model>'
30+
simplifications: '<How was the solution simplified?>'
31+
32+
reflect:
33+
insight:
34+
- '<What clicked? What got internalized?>'
35+
blockers:
36+
- '<What still feels unclear or painful?>'
37+
claim_link: 'claims/2025-05-18-week01-claim.md'
38+
39+
delta:
40+
skill_gain: "<What concrete skill moved from can't → can?>"
41+
concept_gain: '<What mental model was added or reshaped?>'
42+
productivity_lever: '<What tool/process made future work easier?>'
43+
44+
time_spent:
45+
total_hours: 4.5
46+
breakdown:
47+
- plan: 0.5
48+
- act: 2.5
49+
- check: 1
50+
- edit: 0.3
51+
- reflect: 0.2
52+
53+
meta:
54+
spH: 'High / Medium / Low'
55+
notes: 'Lock-in achieved fast due to <X>, but refactor was slow → bottleneck in Check phase.'

‎loop/week-01/reflect.md‎

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# 🪞 Reflect — Week 01
2+
3+
## What clicked?
4+
5+
- <Summarize top insights, conceptual locks, or shifts in model.>
6+
7+
## What was hard?
8+
9+
- <List where you struggled: mentally, technically, motivationally.>
10+
11+
## What would you do differently?
12+
13+
- <What would your 3-days-ago self do better now?>
14+
15+
## Meta-level feedback
16+
17+
- Protocol friction: <Was PACER too heavy or helpful?>
18+
- System effectiveness: <Did the loop create clarity or chaos?>
19+
- Tooling: <What was missing? What worked well?>
20+
21+
## Spillover
22+
23+
- <How will this insight / habit affect other domains, workflows, or life decisions?>
24+
25+
## Quote
26+
27+
> "Insert a quote or reflection sentence that encapsulates this week."

0 commit comments

Comments
 (0)