# STRUCTURE.md

## Purpose
This document defines the vault layout, note taxonomy, naming conventions, and frontmatter templates for a memory storage vault designed for Claude Code today and future CoWork plugin access through the Obsidian Local REST API.

## Recommended Vault Layout

```text
vault/
├── CLAUDE.md
├── STRUCTURE.md
├── BOOTSTRAP.md
├── spinup.md
├── index.md
├── README.md
├── inbox/
├── journal/
├── projects/
├── areas/
├── resources/
├── decisions/
├── reviews/
├── _agent/
└── archive/
```

## Note Types
- daily-note
- weekly-note
- monthly-note
- project
- project-update
- area
- concept
- reference
- person
- meeting
- decision
- review
- session-log
- working-memory
- episodic-memory
- semantic-memory
- context-bundle
- skill
- draft
- inbox-item

## Core Frontmatter
```yaml
---
type:
status:
created:
updated:
tags: []
agent_written: false
source_notes: []   # plain relative paths as strings — NEVER [[wikilinks]]
---
```

> **No `[[wikilinks]]` in frontmatter.** YAML parses `[[...]]` as nested lists, so wiki
> links placed in frontmatter (e.g. an old `related:` field) silently break and do not
> render as clickable links. All cross-references go in a **`## Related`** section in the
> note **body**, as a bulleted list of `[[links]]`. Keep frontmatter to scalar/string
> metadata only. `source_notes`, when used, holds plain relative path strings, not links.