Track your thinking. Loop your learning. Build public artifacts. Powered by SMOS.
Canonical template for learning tracks, project-based skill loops, and knowledge pipelines in the 🧱 Second Mind OS Lab.
Maximize your leverage. Build your cognitive stack. Ship high-signal work.
This is not a note-taking system. This is not a journaling habit. This is a feedback loop protocol — to think clearer, track deeper, and verify what you actually know.
This is the official template for constructing trackable learning systems from any course, project, or domain. Use this to:
- Structure your learning as iteration cycles, not passive consumption, verification (via P.A.C.E.R. protocol)
- Produce trackable insights, not fleeting thoughts, log-traceable progression
- Ship public artifacts, not private illusions
- Crystallize ⌬ Mindstamps — reusable thinking units, based on Second Mind OS OVL Protocol
Fork this repo to convert any study path into a systemized execution protocol.
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. You can either keep this convention or adopt your own style.
graph TD
A[Engage with Content] --> B[Note Docs / Build Project / Problem]
B --> C[P.A.C.E.R. Loop]
C --> D[Write Logs + Loop Claim]
D --> E[Claim ⌬ Symbol]
E --> F[Public Output in outputs/]
F --> G[Emit JSON to Personal Site]
Note → Log → Loop → Output
Each learning unit runs through the P.A.C.E.R. loop — a minimal feedback protocol for deliberate skill formation:
Stage | Function |
---|---|
Plan |
Define objective, scope, and constraint |
Act |
Execute, build, engage with material |
Check |
Self-test, validate via examples/tests |
Edit |
Refactor, simplify, correct blindspots |
Reflect |
Meta-log insights, blockers, claims |
Each folder in loop/week-xx-x/
should contain a pacer.yaml
or markdown journal documenting this cycle.
-
Fork this template → rename to
USERNAME/[course|domain]
orUSERNAME/track-[course|domain]
e.g.:track-cs50x
,track-ml-zero
,track-rust-os
-
Optional: Enable GitHub Pages → Serve
outputs/
as public-facing artifacts -
Loop Structure
- 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-c/pacer.yaml
,loop/week-01-c/claim.md
,loop/week-01-c/reflect.md
- Push deliverables to
outputs/
- New loop via CLI (Recommend)
track-cs50x/
├── 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
Track repos should follow:
[course|domain|theme]
track-[course|domain|theme]
Examples:
cs50x
openai-fine-tune
track-ml-zero
track-rust-os
track-freecodecamp-js
Use as public fork base for consistent naming across teams/orgs.
- GitHub Actions for JSON metadata export
- Auto-log CLI script (
log "note here"
) - Auto-site render via
outputs/
→gh-pages
MIT — use freely under your personal or team workflows.
Note: All forks must include the following in
README.md
:
Powered by Second Mind OS Lab — Protocol-first learning system for cognitive leverage.
🧱 Second Mind OS Lab Protocol harmony, cognitive precision, outcome-driven learning.
⚓ Personal mastery is system-driven. Track everything. Reflect ruthlessly. Ship deliberately.
Powered by Second Mind OS Lab — Protocol-first learning system for cognitive leverage.