PKM Vault — AGENTS.md

This is Phuriwaj’s personal knowledge management vault, built in Obsidian and managed with the zk CLI tool. Use this file to understand the folder structure, note types, naming conventions, and writing rules before creating or modifying any notes.

Folder Structure

Notes/
├── calendar/
│   ├── notes/          ← Daily journals (YYYY-MM-DD.md)
│   └── weekly/         ← Weekly reviews (YYYY-Www.md)
├── efforts/
│   ├── on/             ← Active and in-progress projects
│   └── done/           ← Completed efforts (archive)
├── evergreen/          ← Permanent, developed ideas (promoted from journals)
├── inbox/              ← Fleeting captures awaiting processing
├── reference/          ← Evergreen how-tos, configs, cheatsheets
├── library/            ← Documents, guides, attachments
├── scripts/            ← Automation scripts and skill files
│   └── send-daily-summary.py  ← Discord + email delivery script
├── .zk/templates/      ← Note templates (journal, effort, evergreen, reference)
└── index.md            ← Vault home / navigation

Note Types

Journal (calendar/notes/YYYY-MM-DD.md)

Daily log of conversations, decisions, and insights. Created automatically by the pkm-daily-generator skill. Structure: Freewrite → Big Things Today → Conversations (grouped by theme) → Open Tasks Surfaced → Insights Worth Developing.

Weekly (calendar/weekly/YYYY-Www.md)

Weekly synthesis. Created by the pkm-weekly-consolidator skill every Friday. Structure: Summary → Topics Covered table → Key Decisions → Open Tasks Carried Forward → Insights Promoted to Evergreen.

Effort (efforts/on/*.md)

Active project tracking notes. One per project. Contains: status indicator, goal, current focus, open task checklist, progress log (dated entries), people. Move to efforts/done/ when the primary goal is achieved.

Evergreen (evergreen/*.md)

Permanent, developed ideas promoted from journal “Insights Worth Developing” sections. Written in timeless language — no diary-style. Structure: Core Idea → Why This Matters → Key Points → Connections → Source.

Reference (reference/*.md)

Evergreen how-tos, command references, configs, and tool guides. No diary language. Code blocks for everything runnable. One topic per note. Structure: Why/When to Use → Key Points → Details → Gotchas → Source.

Fleeting / Inbox (inbox/*.md)

Quick captures, unprocessed notes. Named with date prefix: YYYYMMDD-slug.md. Process into reference/effort/evergreen then delete or archive.

Frontmatter Schema

All notes use this frontmatter — fill every field:

---
title: "Descriptive title"
date: YYYY-MM-DD        # creation date
source: claude-ai       # or: self, web, book, meeting
type: journal | effort | evergreen | reference | fleeting
tags: [tag1, tag2]
related: ["[[note-slug]]", "[[another-note]]"]
up: ["[[ParentNote]]"]  # parent in the hierarchy (Calendar, Efforts, Evergreen, reference)
rank:                   # optional 1–10 personal importance score
---

up: values by type:

• journal → ["[[Calendar]]"]
• effort → ["[[Efforts]]"]
• evergreen → ["[[Evergreen]]"]
• reference → ["[[reference]]"]

Naming Conventions

• All files: kebab-case.md
• Daily journals: YYYY-MM-DD.md
• Weekly reviews: YYYY-Www.md (e.g. 2026-W21.md)
• Inbox: YYYYMMDD-short-description.md
• Efforts, references, evergreens: descriptive slug (e.g. hermes-agent-configuration.md)

Writing Rules

1. Evergreen language — reference and evergreen notes must be written without diary language. No “today we did X”. Just facts, commands, and principles.
2. One topic per reference note — if a note covers two distinct things, split it.
3. Wiki-links for all cross-references — use [[note-slug]] syntax everywhere. Never use plain text to reference another note.
4. Code blocks for everything runnable — commands, config snippets, scripts always go in fenced code blocks.
5. Append, don’t overwrite — when updating an existing note, add a dated section (## Updates — YYYY-MM-DD) rather than rewriting the original content.
6. Open tasks in effort notes — use - [ ] task checkboxes in the ## Open Tasks section; check them off when done.

Delivery System

After writing notes, the PKM generator sends a summary via:

• Discord: scripts/send-daily-summary.py — posts to the configured webhook
• Email (Gmail): Claude’s native Gmail MCP connector (create_draft) — drafts land in r.phuriwaj@gmail.com

Script location: D:\OneDrive\Personal\Notes\scripts\send-daily-summary.py Bash path: /sessions/<session-id>/mnt/Notes/scripts/send-daily-summary.py

Note: The <session-id> segment of the bash path changes each Cowork session. Always resolve it dynamically with ls /sessions/ or pwd.

Key Efforts (active as of 2026-05-23)

Automation Schedule