Markdown for Project
Project documentation lives in doc/. Each entry is a separate file in its own subdirectory:
| Subdirectory | When to create | Naming pattern |
|---|---|---|
doc/logs/ | After ANY code change or task | <topic>.md |
doc/experiments/ | When running simulations/tests | <topic>.md |
doc/issues/ | When encountering bugs/errors | <topic>.md |
doc/knowledge/ | When capturing domain knowledge, concepts, or reference material | <topic>.md |
Workflow
- •Do the work
- •After completing, create a new file in the appropriate subdirectory
- •If experiments were run, create a file in
doc/experiments/ - •If issues were found, create a file in
doc/issues/ - •If domain knowledge or reference material was gathered, create a file in
doc/knowledge/
Frontmatter (Obsidian)
Every .md file in doc/ must have this frontmatter:
yaml
--- id: <uuid-v4> name: <note-name> description: <brief description> type: <experiment|issue|knowledge|log|plan|notes|reference> created: <YYYY-MM-DDTHH:MM:SS> updated: <YYYY-MM-DDTHH:MM:SS> tags: [tag1, tag2] aliases: [alternate-name] ---
Generate UUID: python -c "import uuid; print(uuid.uuid4())"
Get datetime: date +%Y-%m-%dT%H:%M:%S
File Naming
- •All files:
<topic>.md(lowercase, hyphenated, no spaces) - •Examples:
reward-shaping.md,ppo-training-run.md,cpg-frequency-bug.md
Entry Templates
See references/templates.md for the exact format of log, experiment, and issue entries.
Linking
Use basic wikilinks only: [[note-name]]
Avoid: [[note|display]], [[note#heading]], ![[embed]]