An Obsidian Vault for College Records You Can Keep and Explain

When students start using Obsidian, they often mix everything into one large vault folder structure: daily class notes, active group assignment drafts, administrative receipts, personal journals, and technical concept summaries. At first, having dozens of subfolders feels organized. But after a semester or two, finding an exact record or knowing which notes are safe to archive becomes frustratingly difficult.

A personal knowledge vault should not try to mimic a busy course directory or a team project workspace. Its explicit purpose is to store extracted, synthesized knowledge—understandings rewritten in your own words, conceptual frameworks, and reflective learning logs—rather than raw data, program source code, datasets, or runtime artifacts that belong in a dedicated project directory. It works best when organized by lifecycle responsibility—separating incoming raw notes, original event logs, durable conceptual knowledge, active personal tasks, and long-term archives.

Direct Answer

To build a maintainable four-year college record vault, organize your files into six clear lifecycle folders:

01-knowledge/
02-timeline/
03-tasks/
04-assets/
05-inbox/
06-archive/

Keep durable, rewritten topic explanations in 01-knowledge/. Store original dated records, journals, advising notes, and equipment maintenance logs in 02-timeline/. Use 03-tasks/ only for active personal work. Keep referenced media, diagrams, and PDFs in 04-assets/, unprocessed quick notes in 05-inbox/, and completed or inactive material in 06-archive/.

(Note: Third-party browser extensions like the Obsidian Web Clipper often create a Clippings/ folder automatically when saving web excerpts, but for your core vault organization, these six folders handle all essential personal knowledge responsibilities.)

Always preserve original facts and dates in your timeline notes. Extract a standalone concept note or task into 01-knowledge/ or 03-tasks/ only when that note serves an independent purpose.

The 6-Folder Lifecycle Responsibilities

Rather than creating new folders for every subject or semester, these six numerical folders represent how information moves through your personal workflow over time:

1. 01-knowledge/: The home for your reusable, synthesized understandings. Notes here are written in your own words, organized by topic or concept rather than by date or course number (e.g., git-worktree-basics.md or python-memory-management.md).
2. 02-timeline/: A chronological record of real events, advising conversations, semester reviews, degree planning decisions, and equipment logs. Notes here record what actually happened on a specific date.
3. 03-tasks/: A lean folder for active personal checklists and project milestones. Keep only current, actionable personal items here.
4. 04-assets/: Storage for embedded diagrams, images, templates, or local attachments referenced by your Markdown notes.
5. 05-inbox/: The temporary holding area for rapid captures, unverified thoughts, and quick meeting scratchpads. Every note here is waiting for triage.
6. 06-archive/: The resting place for completed projects, past semester records, and inactive logs. Archived notes remain fully searchable via Markdown links without cluttering your active view.

Capture, Triage, and Extraction Workflow

A common pitfall is treating a note capture as a one-step task. A durable vault relies on a clear four-step loop: Capture → Triage → Classify → Extract.

+-----------------------+
|   05-inbox/           |
| (Raw Quick Captures)  |
+-----------+-----------+
            |
            v (Triage & Preserve Facts)
+-----------+-----------+
|   02-timeline/        |
| (Original Event Logs) |
+-----+-----------+-----+
      |           |
      |           +-----------------------+
      v (Extract Reusable Concept)        v (Extract Action)
+-----+-----------+                     +-+---------+
|   01-knowledge/ |                     | 03-tasks/ |
| (Durable Notes) |                     | (Actions) |
+-----------------+                     +-----------+

1. Capture Raw Information (05-inbox/)

Suppose you attend an academic advising session about upper-division course registration. You open Obsidian and quickly record notes in 05-inbox/2026-08-04-advising-raw.md:

# Advising Notes - Aug 4
- Met with Dr. Smith.
- Need COP 4534 (Data Structures II) before taking Senior Design.
- Need to file a prerequisite override form by Oct 15 if taking CIS 4930.
- Recommended reading: "Operating System Concepts" Ch 3-4.

2. Triage & Preserve Original Facts (02-timeline/)

During your review, move the raw note into 02-timeline/2026-08-04-academic-advising.md. Keep the original facts, date, and context intact:

---
type: record
date: 2026-08-04
tags:
  - type/record
  - area/advising
  - term/2026-fall
---
# Academic Advising Record - Fall 2026

**Date:** 2026-08-04  
**Advisor:** Dr. Smith  

## Original Record
Discussed senior course sequencing. Confirmed COP 4534 prerequisite requirement for Senior Design. Dr. Smith noted that CIS 4930 requires an override form submitted before Oct 15.

## Extracted Actions
- [ ] Submit CIS 4930 override form by Oct 15 -> extracted to `03-tasks/`

3. Extract Reusable Concepts & Tasks

Once the original record is preserved in 02-timeline/, extract independent items only where necessary:

• Active Task: Create a task item in 03-tasks/cis-4930-override-form.md or track it in your primary task manager.
• Durable Concept: If you read Chapter 3 of the recommended textbook later, write a new, standalone concept note in 01-knowledge/process-state-transitions.md. Link back to the timeline note, but keep the concept explanation self-contained.

Delegating Vault Maintenance to AI Agents (Codex, Claude Code, Antigravity)

Maintaining a personal knowledge base across four years of college can take considerable time if done manually. Inspired by Andrej Karpathy’s concept of an AI-maintained personal wiki, you can delegate routine organizational mechanics to workspace AI agents such as Codex, Claude Code, or Antigravity.

Because your Obsidian vault is stored locally as plain Markdown files, an AI coding agent can inspect your vault directory and handle routine structural maintenance:

• Triage & Classification: Ask an AI agent to read raw meeting notes in 05-inbox/, format front matter, assign initial tags, and place the file into 02-timeline/.
• Index Generation: Have the AI inspect 01-knowledge/ and update your top-level index.md table of contents automatically whenever new concepts are added.
• Consistency & Link Audits: Ask the AI agent to scan your vault for broken [[internal links]], missing YAML metadata fields, or duplicate note titles.

[!TIP] Human Review Boundary: Always let the AI agent handle structural formatting and link indexing, but retain full personal review over the content. Never let an AI overwrite original event facts or invent source claims.

Academic Namespaced Tags and Indexes

As your vault grows across four years, light metadata helps you filter notes without spending hours creating complex folder structures.

Academic Namespaced Tags

Avoid unstructured tags like #important or #stuff. Use namespaced tags with explicit prefixes to organize academic records:

• Course Tags: course/cop3530, course/enc1101, course/cis4930
• Semester & Term Tags: term/2026-fall, term/2027-spring, term/2027-summer
• University Area Tags: area/advising, area/financial-aid, area/housing, area/research
• Note Type Tags: type/record, type/concept, type/journal, type/project
• Status Tags: status/active, status/archived, status/pending

Lightweight Indexes (index.md)

Instead of relying on deep nested folders, create a top-level index.md file in 01-knowledge/ that acts as a curated table of contents for key topics:

# Personal Knowledge Index

## Computing Foundations
- [[git-worktree-basics]] — Parallel development workflows with Git.
- [[process-state-transitions]] — OS kernel process lifecycle states.

## Degree & Academic Records
- [[2026-08-04-academic-advising]] — Fall 2026 advising and course planning (`area/advising`, `term/2026-fall`).

Vault Synchronization vs. Git Version Checkpoints

Managing your vault across multiple devices and preserving your history requires two complementary tools: synchronization and version checkpoints.

1. Cloud Storage & Obsidian Sync (For Basic Device Sync)

For complete beginners who simply want their notes available across a laptop, phone, and tablet without using command-line tools, standard cloud synchronization works well. You can store your vault folder in:

• Cloud Storage Services: iCloud Drive, Google Drive, or Microsoft OneDrive.
• Obsidian Sync: Obsidian’s official encrypted synchronization service.

These services handle automatic background synchronization so your notes are available wherever you work.

2. Why Git Checkpoints Are Uniquely Essential for AI-Assisted Workflows

While cloud storage syncs your files, it continuously overwrites previous versions in place without showing what changed line-by-line.

This creates a serious safety risk when you use AI coding assistants (Codex, Claude Code, Antigravity) to perform automated vault maintenance. When an AI agent performs a batch operation—such as reorganizing raw notes, formatting front matter across 20 files, or regenerating your index.md—it can update dozens of Markdown files in a single pass.

If the AI makes a mistake, hallucinates an internal link, or accidentally truncates text, standard cloud sync cannot easily pinpoint or rollback those specific lines. This is why Git is uniquely essential for AI-assisted workflows:

git add .
git commit -m "checkpoint: preserve Fall 2026 advising records and knowledge index"

With local Git checkpoints:

• Inspect Exact Diffs (git diff): You see precisely which lines and files the AI modified before accepting the changes.
• Instant Rollbacks (git checkout / git restore): If an AI agent messes up a note or breaks links, you can undo the exact commit instantly without losing your surrounding work.
• Audit-Ready History (git log): You maintain a clear, chronological audit trail of your vault’s evolution across four years.

Privacy & Institutional System Boundaries

A personal Obsidian vault is a personal reflection and knowledge tool—it is not an official university record system, secure credential store, or official archive.

[!WARNING] Privacy & Boundary Rules:

• Keep Project Repositories Outside the Vault: Do not place software code repositories, build artifacts (node_modules/, __pycache__/), or large test datasets inside your Obsidian vault. Toolchains and compilers create thousands of temporary files that slow down vault indexing and cloud sync. Keep project execution trees in a dedicated project directory (such as Projects/weather-analysis/) and link to them from your vault notes by relative path or URL.
• Never Store Credentials: Do not copy passwords, SSH private keys, recovery codes, or API tokens into your vault.
• Protect Confidential Information: Do not store sensitive student records, confidential institutional data, or unencrypted personal health information in local vault files or third-party sync plugins.
• Respect Official Systems: University degree audits, official transcripts, and Canvas assignment submissions remain the canonical source of truth for official academic standing. Your vault is for your personal learning and record tracking.

Do This Now

1. Create the 6-Folder Vault: In Obsidian, create the six numerical folders (01-knowledge/ through 06-archive/) and move any raw unorganized notes into 05-inbox/.
2. Process One Record: Take one real advising note, project log, or journal entry from your inbox. Move the original record into 02-timeline/, assign it academic namespaced tags (e.g., type/record, area/advising, term/2026-fall), and extract any reusable concept into 01-knowledge/.
3. Commit a Git Checkpoint: Open your terminal in the vault folder, run git add . and git commit -m "initial 6-folder vault structure", and verify your clean working tree with git status.

Log what you learned

Record only:

• Result: What did the action produce?
• Evidence: What observation, test, or source supports that result?
• Next action or unresolved question: What should happen next?

References

• Obsidian Help: Basic note taking and linking — Official guide on internal links, Markdown formatting, and vault structure.
• Git Documentation: Recording Changes to the Repository — Official Git guide on staging, committing, and inspecting local version history.