# PSKA Tag Taxonomy Valid `tags` values for PSKA notes. The summary-note skill reads this note before creating or editing notes, so changes here take effect on the next batch run. > [!note] Scaffold by Jake (2026-09-03). Fill in and adjust. ## Note-type tags (structural) One or more per note; describes what the note *is*. Each note has at least one and no more than two tags. - `document` — generic source-derived note - `summary` — summary note built from a source document - `claim` — a statement asserting something is true, linked to evidence - `concept` — a concept or idea note - `moc` — Map of Content note - `convention` — meta note defining system rules (like this one) - `person` – a note describing an individual (an author, teacher, consultant, etc.) ## Topic tags (subject matter) Topic tags describe what the note is *about* and are entered in the `related:` field as links to concept notes. Link to existing concepts first. If a new concept is required, it's acceptable to create a new empty link (e.g., `[[example]]`) ## mediaType tags One per note to indicate the source material’s media type. - article - includes blog posts as well as articles in newspapers, magazines, or journals - book - including ebooks and audiobooks - email - pdf - social media post - video - podcast ## sourceSystem tags Indicates where the full resource is stored in my personal library. - [[Readwise Reader]] - [[DEVONthink]] - [[Raindrop]] - [[obsidian-public]] - [[obsidian-private]] - [[stumax.com]] - [[ebook]] - [[iCloud]] - [[email]] - [[hardcopy]] ## Workflow markers Tags applied in external systems, not in vault notes. - `z-in-vault` — applied in Readwise Reader when a document's summary note is saved to the vault - `ia`, `ia/ux`, `ia strategy`, `iaclass` — Reader-side corpus filter tags for Phase 4 processing ## Notes -