2026-07-04 Sat
Ideas
Banning AI from using specific words or phrases
- I'd like to make a system that makes it very easy for me to ban AI from using words and phrases with me or when creating documents.
- My first thought about this was to make an AI/Agent/Skill in rulesync which would let me quickly add a word or phrase to a part of the knowledge garden that catalogs the words or phrases that I'd like AI to avoid when communicating with me or on my behalf, following progressive disclosure. I was thinking that ideally, there would be a table of contents page that would have logseq wikilinks to individual pages, one per word or phrase. That way listing the contents of a namespace would be sufficient to tell the AI what to ignore.
- Later, I was thinking of using Claude/Code/Hooks for this.
- I'd like to make a system that makes it very easy for me to ban AI from using words and phrases with me or when creating documents.
Convert
#taglinks to[[wikilink]]form on commit- I'd like a pre-commit converter, built like the
text:fix-invisiblemise task, that rewrites Logseq#tagand#[[Page]]links into[[...]]form — one obvious way to link (Py/Zen of Python), and the shape Looksyk can import, since it reads[[...]]but not#tag. - Not as safe a rewrite as invisible whitespace, so it stays deferred. A
#also begins headings, hex colors, shell comments, and URL fragments, so the converter has to skip fenced and inline code, ignore#before a space or another#, and treat#as a link only at a word boundary. Scope it to.mdfiles under pages/ and journals/, where well over a thousand inline#links live today.
- I'd like a pre-commit converter, built like the
Filed
- fail2ban
- Person/James Clear
- Person/James Clear/Book/18/Atomic Habits
- Person/James Clear/Book/18/Atomic Habits/Quote/Good Easy, Bad Difficult
- My/Principle/Make the Right Thing Easy and the Wrong Thing Hard
- Py/Zen of Python
- My/Principle/Simplify/Not every distinction is worth recording
- Terminal/Multiplexer/Idea
- Logseq/Entity/Dotfiles/Dep/Idea
Updated