You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,27 +1,27 @@
1
1
# TokenMap
2
2
3
-
TokenMap is a desktop app for quickly finding the parts of a local codebase that are large, complex, hotspot-heavy, or likely to be worth refactoring first.
3
+
TokenMap is a desktop app for quickly finding the parts of a local codebase that carry the most structural risk or are most worth refactoring first.
4
4
5
5
<imgsrc="docs/readme/screenshot.png"alt="TokenMap main window"width="838">
6
6
7
7
## Why TokenMap?
8
8
9
9
- See which folders and files actually dominate a repository.
10
-
- Find complexity and hotspot signals before refactors, cleanup, or architecture work.
10
+
- Find refactor candidates before cleanup, decomposition, or architecture work.
11
11
- Estimate which parts of a codebase will cost the most tokens in LLM workflows.
Copy file name to clipboardExpand all lines: docs/architecture.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,7 @@ This document covers project purpose, canonical ownership, runtime flow, and non
39
39
-`Clever.TokenMap.Metrics` stays below app/infrastructure orchestration and above core models; UI consumes metric abstractions through core contracts.
40
40
- File metrics flow as raw file metrics, then chained derived file metrics, then directory rollup; raw parser objects stay inside the metrics layer.
41
41
- Infrastructure may enrich a snapshot with one optional repo-wide git history pass before per-file metrics so product metrics can consume cached per-file git artifacts without per-file repository walks.
42
-
-`Refactor Priority` is the product-facing composite score for refactoring urgency; git-derived change pressure stays an internal input, not a separate public metric.
42
+
-`Structural Risk` is the product-facing intrinsic quality score; it summarizes file scale, callable burden, and how concentrated that burden is inside the file.
43
+
-`Refactor Priority` is the product-facing composite score for refactoring urgency; it layers recent change and co-change pressure on top of Structural Risk instead of exposing git signals as separate public metrics.
0 commit comments