Structure Proposal

Knowledge Base Structure Proposal

Archived — structure proposal, superseded

This was an early proposal for the vault folder structure (Jan 2026). The actual structure has since been implemented and evolved. Do not treat as a reference for current vault organization — read the actual directory structure instead.

---

Proposed Structure

02-areas/
└── teaching/
    ├── _index.md                    ← You are here (Teaching Hub)
    │
    ├── courses/
    │   └── primer/
    │       ├── _index.md            ← Course overview & pedagogy
    │       ├── segment-01-[name]/
    │       │   ├── _index.md        ← Segment overview
    │       │   └── lesson-001/
    │       │       ├── _index.md    ← Lesson summary
    │       │       ├── transcript-en.md
    │       │       ├── transcript-ja.md
    │       │       └── subtitles/
    │       │           ├── en.vtt
    │       │           └── ja.vtt
    │       └── ... (10 segments, 72 lessons)
    │
    ├── events/
    │   └── 2026/
    │       └── 2026-01-tokyo-intensive/
    │           ├── _index.md        ← Event overview
    │           ├── preparation/     ← Planning docs
    │           └── sessions/        ← Session notes & transcripts
    │
    └── curriculum/
        └── _index.md                ← Pedagogical framework

03-resources/
└── reference-archive/
    ├── pre-baseworks/               ← Historical materials
    └── external-influences/         ← Reference materials

---

Design Decisions

Decision	Rationale	Open Questions
Lessons as folders	Keeps transcript + subtitles + summary together	Too nested?
Numbered lessons (001)	Maintains sort order	Or use titles only?
Language suffix (transcript-en)	Clean multi-language support	Other languages needed?
Events link to courses	Shows relationships	How to handle standalone events?
Subtitles in subfolder	Separates non-markdown files	Or keep flat?

---

Sample Content Created

To see how this feels, I’ve created:

1. Teaching Hub — Main navigation page
2. Primer Course — Course overview
3. Segment 01 — Example segment
4. Lesson 001 — Full example with transcript
5. Tokyo Event — Example event linked to course

---

Feedback Section

Patrick’s Thoughts

Add your feedback here…

---

Ksenia’s Thoughts

For 02_areas, I propose sys like:

• rename “teaching” to “educational programs”
• under “educational programs”, have: study groups study labs events (for one-off events) curriculum .md (overall structure of offerings)
• in addition to “educational programs”, add:

Primer Practice platform Clusters Info articles Community Forums (where we document questions and answers Website Main pages Blog articles (tag by author) Method Admin (internal documentation) Core Key Definitions History Science Marketing (audience, campaigns, planning) Brand Guide

For Primer, I think the structure is better like this:

Primer Transcripts (en) Lesson Summaries (en) Subtitles (en) Subtitles (fr)

This way, there is less to refer to for Claude - we save tokens if Claude only need to open the folder with transcripts and they are all there than if Claude need to open 79 folders and look inside for the transcript file. Need to confirm with Claude if this strategy is more token-economical

---

Questions to Consider

1. Segment naming: Should segments have descriptive names (e.g., segment-01-foundations) or just numbers?

2. Lesson numbering: Global (001-072) or per-segment (01-01, 01-02)?

3. Languages: Which languages do we need? (en, ja, others?)

4. Event types: What types of events do we run? (intensive, workshop, retreat, other?)

5. Historical content: What categories of pre-Baseworks material should we include?

6. Anything missing?

---

Next Steps

1. Review the sample content in Obsidian
2. Add feedback above
3. Commit and push: Cmd+P → “Obsidian Git: Commit all changes” → “Push”
4. Resume with Claude to refine and build out full structure

---

Last updated: 2026-01-30