Skip to content

Read GLOSSARY.md as domain vocabulary and show the analysed languages in About - #32

Open
rcosteira79 wants to merge 5 commits into
feat/briefing-grounding-part-4-measure-briefing-coverage-of-changed-linesfrom
feat/briefing-grounding-part-5-discover-glossary-files-and-show-analysed-languages
Open

rcosteira79 wants to merge 5 commits into
feat/briefing-grounding-part-4-measure-briefing-coverage-of-changed-linesfrom
feat/briefing-grounding-part-5-discover-glossary-files-and-show-analysed-languages

Conversation

@rcosteira79

Copy link
Copy Markdown
Collaborator

What

  • Domain glossary discovery reads GLOSSARY.md as well as CONTEXT.md and CONTEXT-MAP.md.
  • A code binding must use the nearest glossary, and a CONTEXT.md and a GLOSSARY.md in one folder are equally near. A nested GLOSSARY.md still outranks a root CONTEXT.md.
  • The domain prompt tells the agent that each glossary file outside CONTEXT-MAP.md is its own model, so two files in one folder give two models.
  • A concept citing a glossary with no model of its own is labelled by its folder, for GLOSSARY.md as for CONTEXT.md.
  • /api/about returns codeAnalysis, and the About dialog shows it as a "Code analysis" row after Mode: "TypeScript, TSX and Kotlin. Changes in other languages get no static facts. CodeGraph is used when this repository has a matching index." That sentence and the no-change-facts message are built from the same language table the parsers use.

Why

Discovery read only CONTEXT.md and CONTEXT-MAP.md, so a repository keeping its vocabulary in GLOSSARY.md got no domain maps. Nothing in the app said which languages get static change facts.

Decisions and trade-offs

Choice Why
Same-folder CONTEXT.md and GLOSSARY.md are equally near Picking one would silently hide the other's concepts from every file below that folder
One model per glossary file, stated in the prompt The validator already rejects a model citing another file, and one rejected model drops every domain map in the review
The About sentence is built from SYNTAX_LANGUAGES A new grammar then updates the About row and the no-change-facts message together, instead of a hand-written list drifting

Please check the nearest-glossary rule at src/domain-context.ts:102 with nested and same-folder glossaries: a binding must fail when its concept cites a shallower file than the nearest one.

No ADR was added or amended on this branch.

How to test

Open the settings menu, then About. The last row should read "Code analysis" with the sentence above. Then run a tour with architecture maps on a change to src/briefing.ts in this repository, which keeps its vocabulary in the root GLOSSARY.md. When the tour offers a domain map, its terms should cite GLOSSARY.md. Please check by eye that the long Code analysis sentence wraps inside the About dialog.

@rcosteira79
rcosteira79 added this pull request to stack #25 October 29, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant