Repository navigation
docs: remove NOMENCLATURE_GUIDE.md, ported to GLOSSARY.md - #707
Conversation
The guide duplicated the role of a glossary: terminology standards for writing and auditing docs. Its content moved to GLOSSARY.md (machine-local, companion-linked into every worktree) with per-term entries for the core concepts so vocabulary settles in one file going forward. No other file referenced the guide.
|
|
View your CI Pipeline Execution ↗ for commit ba7cb58
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
🚀 Production Deployment: Website✅ Successfully deployed to production! 🔗 Production URL: https://pgflow.dev 📝 Details:
Deployed at: 2026-10-18T00:03:49+02:00 |

Summary
The guide duplicated the role of a glossary. Its content moved verbatim into the companion-owned
GLOSSARY.md(symlinked into every worktree); core concepts restructured into per-term entries so/domain-modelingextends them one at a time. The public repo keeps no copy.Evidence
NOMENCLATURE_GUIDE.mdat the repo root; case-insensitive grep across the repo and the companion found no other reference to itAfter:
git grep -i nomenclatureon this branch returns nothing; theGLOSSARY.mdsymlink resolves in every worktreeMerge Danger
Door: two-way (docs-only; revert restores the guide)
Blast Radius: doc writers who reference the guide by path — none found in-repo