From 31fa30893d98081d1e07c9cad698e1a818519d18 Mon Sep 17 00:00:00 2001 From: jared Date: Tue, 30 Jun 2026 15:19:21 -0400 Subject: [PATCH] vault: session notes 2026-06-30 --- journal/2026-06-30.md | 7 ++++++ vault-conventions.md | 54 +++++++++++++++---------------------------- 2 files changed, 25 insertions(+), 36 deletions(-) diff --git a/journal/2026-06-30.md b/journal/2026-06-30.md index ffa90a4..32e0080 100644 --- a/journal/2026-06-30.md +++ b/journal/2026-06-30.md @@ -142,3 +142,10 @@ tags: [scope/global, type/log] **Reason:** clear **Vault notes touched:** (none) + +## Session — 2026-06-30T19:19:21Z + +**Project:** /home/jared/dev/ruby-gems/notify +**Reason:** prompt_input_exit +**Vault notes touched:** +(none) diff --git a/vault-conventions.md b/vault-conventions.md index 3189e17..d5adade 100644 --- a/vault-conventions.md +++ b/vault-conventions.md @@ -2,7 +2,6 @@ summary: Universal conventions for all notes in this vault — naming, frontmatter, tag taxonomy, hub notes, and Graphify awareness. tags: - type/meta - - scope/global source: SecondBrain date: 2026-06-08 --- @@ -28,32 +27,15 @@ should not be archived here until they have something stable to say. ## File Naming -`YYYY-MM-DD-descriptive-slug.md` +`descriptive-slug.md` -- Date is creation date - Slug is lowercase kebab-case -- Source platform suffix when applicable: `-chatgpt`, `-gemini`, `-claude` -- Generated by tooling — do not rename manually +- No date prefix +- Directories by type: `convention/`, `reference/`, `howto/` ## Frontmatter Contract -Every note requires these fields. No exceptions; defer writing the `summary` for nothing. - -```yaml ---- -summary: One sentence, human-written at creation. Used by the Graphify graph and SessionStart context injection. -tags: - - type/reference # facet-namespaced; type/ listed first; at least one type/ required - - client/acme # omit if not client-specific - - project/website-redesign # omit if not project-specific - - domain/seo # topic area - - tool/semrush # tool referenced, if any - - convention/api-style # cross-project convention, if applicable - - scope/global # or scope/project — always include one -source: -date: YYYY-MM-DD ---- -``` +Every note requires these fields. No exceptions; defer writing the `summary` for nothing. See [Standard Frontmatter Schema](#standard-frontmatter-schema) below for the authoritative schema. **`summary` field rules:** - One sentence, written by the human (or agent) at creation time. @@ -79,7 +61,7 @@ Use exactly one `type/` tag per note. ## Tag Taxonomy -Tags are **flat and parallel** — no nested paths, no hierarchy inside a facet. Six facets plus `scope/`: +Tags are **flat and parallel** — no nested paths, no hierarchy inside a facet. Six facets (`scope` is a frontmatter field, not a tag): | Facet | Purpose | Example | |---|---|---| @@ -89,14 +71,9 @@ Tags are **flat and parallel** — no nested paths, no hierarchy inside a facet. | `domain/` | Topic area or discipline | `domain/seo`, `domain/cold-email` | | `tool/` | Tool, library, or platform referenced | `tool/graphify`, `tool/semrush` | | `convention/` | Cross-project convention or pattern | `convention/api-style` | -| `scope/` | Applicability breadth | `scope/global` or `scope/project` | - -**`scope/` values:** -- `scope/global` — applies across all work; not tied to a specific client or project -- `scope/project` — specific to one client/project context; pair with `client/` or `project/` **Rules:** -- Always include `type/` and `scope/`. All other facets are optional. +- Always include `type/`. All other facets are optional. - Use multiple tags within a facet when accurate (e.g., `domain/seo` and `domain/cold-email`). - Facets are not nested: `domain/cold-email` is correct; `domain/outbound/cold-email` is not. @@ -162,18 +139,23 @@ All notes use this frontmatter block. Type-specific additions are noted inline. ```yaml --- type: [convention|reference|howto] +subtype: [pattern/framework|api-integration|role-definitions|design-rules] # reference only title: [Human-readable title] summary: [1-2 sentences answering "what question does this note answer?"] tags: - type/[convention|reference|howto] - - domain/[field] # e.g., domain/rails, domain/ai-agents, domain/design - - tool/[tool] # if tool-specific; omit if not - - client/[client] # if client-specific; omit if general - - project/[project] # if project-specific; omit if general + - domain/[field] + - tool/[tool] # if tool-specific + - client/[client] # if client-specific + - project/[project] # if project-specific scope: [global|project|client] last_updated: YYYY-MM-DD -# For mutable facts (API integration refs, billing rates): -# last_reviewed: YYYY-MM-DD +date: YYYY-MM-DD # creation date — set once, never updated +last_reviewed: YYYY-MM-DD # mutable facts only (API integration refs, billing rates) +update_note: experience-driven # howtos only, when steps involve changing UIs/APIs +related: + - [note-slug] # cross-links to companion notes +source: [project name] # project that spawned the note (e.g., llf-schema, design-mode, hyperthrive_dev) --- ``` @@ -181,7 +163,7 @@ last_updated: YYYY-MM-DD - `type` — machine-readable; mirrors the `type/` tag. Required. - `title` — human-readable display name. Required. - `summary` — 1-2 sentences that answer the note's core question. Used by Graphify and SessionStart injection. Required; never defer. -- `tags` — at minimum `type/` and `scope/` are required (see Tag Taxonomy above). Add `domain/`, `tool/`, `client/`, `project/` as applicable. +- `tags` — at minimum `type/` is required (see Tag Taxonomy above). Add `domain/`, `tool/`, `client/`, `project/` as applicable. - `scope` — `global` (applies across all work) or `project` (specific to one client/project). Required. - `last_updated` — date of last substantive edit. Required. - `last_reviewed` — optional; add only for mutable facts (API integration refs, billing rates, role definitions that change).