Summary
The Corpus knowledge graph supports author nodes (documents linked to the authors who wrote them), but the option to turn them on is hardcoded off at both call sites in the renderer — there is no way to enable them from the UI.
Found while auditing the ClioDeck wiki against the actual code (1.8-Corpus-Analysis-Guide.md).
Current behavior (verified against code)
backend/core/analysis/KnowledgeGraphBuilder.ts:43,92,125 — includeAuthorNodes?: boolean is a real, implemented option (default false); when true, the builder adds author nodes to the graph.
src/renderer/src/components/Corpus/useCorpusData.ts:78 and :122 — both call sites that build graph options hardcode includeAuthorNodes: false.
- No component exposes a toggle for this —
grep -rn "includeAuthorNodes" src/renderer/ only shows the two hardcoded call sites.
Why this matters
This is fully-implemented, working functionality on the backend side that a user can never reach — same shape as the collection-filter gap (separate issue) and the embedding-provider UI gap (#18). A historian who wants to see author relationships in their corpus graph has no path to that view today, even though the code to render it exists and works.
Suggested fix
Add a toggle (e.g., in the Knowledge Graph settings, alongside the existing similarity-threshold slider) that flips includeAuthorNodes to true, wired through the two call sites in useCorpusData.ts.
Evidence trail
backend/core/analysis/KnowledgeGraphBuilder.ts:43,92,125
src/renderer/src/components/Corpus/useCorpusData.ts:78,122
- Wiki page corrected in the same pass:
1.8-Corpus-Analysis-Guide.md.
Summary
The Corpus knowledge graph supports author nodes (documents linked to the authors who wrote them), but the option to turn them on is hardcoded off at both call sites in the renderer — there is no way to enable them from the UI.
Found while auditing the ClioDeck wiki against the actual code (
1.8-Corpus-Analysis-Guide.md).Current behavior (verified against code)
backend/core/analysis/KnowledgeGraphBuilder.ts:43,92,125—includeAuthorNodes?: booleanis a real, implemented option (defaultfalse); whentrue, the builder adds author nodes to the graph.src/renderer/src/components/Corpus/useCorpusData.ts:78and:122— both call sites that build graph options hardcodeincludeAuthorNodes: false.grep -rn "includeAuthorNodes" src/renderer/only shows the two hardcoded call sites.Why this matters
This is fully-implemented, working functionality on the backend side that a user can never reach — same shape as the collection-filter gap (separate issue) and the embedding-provider UI gap (#18). A historian who wants to see author relationships in their corpus graph has no path to that view today, even though the code to render it exists and works.
Suggested fix
Add a toggle (e.g., in the Knowledge Graph settings, alongside the existing similarity-threshold slider) that flips
includeAuthorNodestotrue, wired through the two call sites inuseCorpusData.ts.Evidence trail
backend/core/analysis/KnowledgeGraphBuilder.ts:43,92,125src/renderer/src/components/Corpus/useCorpusData.ts:78,1221.8-Corpus-Analysis-Guide.md.