Write a tag in the content
Write #reading or a nested tag such as #work/review in eligible Markdown text. A nested tag also supplies its ancestor: work/review contributes work. Tags are derived from source text, so renaming a tag across notes requires editing those occurrences. Changing display metadata alone does not rewrite memo content.
Consistency matters
Tag equality preserves case and Unicode spelling. Treat #Work and #work as different tags, and choose one form for recurring topics. Code, URL syntax and other opaque Markdown contexts are not ordinary tag text. The application uses shared recognition rules across editing, rendering and stored memo values; use the saved memo's tag list to check an unfamiliar spelling.
A small useful vocabulary
Start with a few recurring subjects rather than tagging every word. Combine a topic and a workflow clue when useful, for example #reading and #ideas. Tags organize retrieval, not access: adding #private does not change a memo's visibility.
Check recognition with a tiny fixture
Save the example below in a private memo, then inspect its derived tags. Expect work/review and its ancestor work, plus the distinct Work value. literal should not be extracted from inline code. Edit #work/review to #work/notes and save again; the derived nested tag should follow the text edit. Changing only tag colors or display metadata does not perform this content rewrite.
A review note. #work/review #Work
Literal example: `#literal`