---
title: Vault Conventions
area: reference
tags: [reference, assistant]
created: 2026-03-18
updated: 2026-03-18
status: active
---

# Vault Conventions

Shared conventions for `will/will-shared-zap/`. Both Will and zap ⚡ follow these.

---

## Folder Structure

```
Plans/              → Schedules, goals, decisions, active plans
Infrastructure/     → Stack architecture and technical setup
  Services/         → Individual service docs (Docker, K8s, etc.)
  Automation/       → Cron jobs, n8n workflows, scripts
People/             → People, contacts, relationships
Notes/              → Dated one-off notes (YYYY-MM-DD Topic.md)
Resources/          → Stable reference material
```

---

## Naming

- **Path-based**: `Plans/Daily Schedule.md`, not `Daily-Schedule.md` at root
- **Title case** for note names
- **Dated notes**: `Notes/YYYY-MM-DD Topic.md`

---

## Frontmatter

Every note should include:

```yaml
---
title: Note Title
area: infrastructure | plans | health | automation | personal | reference
tags: [tag1, tag2]
created: YYYY-MM-DD
updated: YYYY-MM-DD
status: active | draft | archived
related: [[Note A]], [[Note B]]
---
```

- `area`: top-level category (single value)
- `tags`: specific descriptors (multiple allowed)
- `status`: use for plans/projects; omit for pure reference notes if not relevant
- `related`: explicit relations; also use inline `[[wikilinks]]` for contextual links

---

## Linking

- **`[[wikilinks]]`** for internal note references → shows in graph, enables backlinks
- **`[markdown](url)`** for external URLs
- Link liberally — more edges = more useful graph

---

## Tag Taxonomy

| Tag | Use |
|---|---|
| `#infrastructure` | Stack, services, networking |
| `#automation` | Cron jobs, n8n workflows, scripts |
| `#plans` | Schedules, goals, decisions |
| `#health` | Monitoring, backups, ops |
| `#daily` | Routines, habits |
| `#reference` | Stable reference material |
| `#assistant` | zap-specific, memory, AI layer |
| `#homelab` | Kubernetes, Raspberry Pi cluster |
| `#integrations` | External services (Telegram, Google, Obsidian) |

---

## Maintenance

- zap updates notes when the stack changes
- Will can edit freely — zap will respect existing structure
- Add new tags to this doc when introducing them
- `updated` frontmatter field should be refreshed on meaningful edits
