google-gemini/workshops
Logical Components
An overview of source code logical components.

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 26 components.

learning6476 LOC (4%) 38 files
chess5831 LOC (3%) 21 files
fantasy3411 LOC (2%) 30 files
games2656 LOC (1%) 10 files
tv2200 LOC (1%) 10 files
cameo1868 LOC (1%) 17 files
waker1330 LOC (<1%) 7 files
smash1041 LOC (<1%) 7 files
artifacts955 LOC (<1%) 6 files
history360 LOC (<1%) 8 files
podcast354 LOC (<1%) 2 files
kundali244 LOC (<1%) 2 files
tools238 LOC (<1%) 2 files
wearable217 LOC (<1%) 2 files
factuality212 LOC (<1%) 6 files
roast198 LOC (<1%) 3 files
prisoner180 LOC (<1%) 1 file
doodles80 LOC (<1%) 1 file
startupcon72 LOC (<1%) 4 files
oxford67 LOC (<1%) 5 files
bricks66 LOC (<1%) 3 files
recap66 LOC (<1%) 3 files
cost66 LOC (<1%) 3 files
utils64 LOC (<1%) 5 files
tedx53 LOC (<1%) 3 files
ROOT38 LOC (<1%) 1 file

scope details...
  • 200 files, 28,343 LOC (18.2% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
learning56 commits (17%)
chess24 commits (7%)
waker19 commits (6%)
smash15 commits (4%)
tv14 commits (4%)
utils11 commits (3%)
cameo11 commits (3%)
artifacts10 commits (3%)
factuality8 commits (2%)
tools7 commits (2%)
recap6 commits (1%)
podcast6 commits (1%)
games6 commits (1%)
kundali6 commits (1%)
ROOT5 commits (1%)
startupcon5 commits (1%)
bricks5 commits (1%)
cost5 commits (1%)
history4 commits (1%)
prisoner3 commits (<1%)
roast3 commits (<1%)
wearable3 commits (<1%)
fantasy3 commits (<1%)
oxford2 commits (<1%)
doodles2 commits (<1%)
tedx2 commits (<1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024
learning
56
chess
24
waker
19
smash
15
tv
14
cameo
11
tools
7
startupcon
5
bricks
4
1
prisoner
3
roast
3
fantasy
3
recap
2
4
oxford
2
utils
2
9
games
2
4
cost
2
3
history
2
2
factuality
2
6
tedx
2
ROOT
1
4
podcast
6
doodles
2
artifacts
10
kundali
6
wearable
3


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report...

No temporal dependencies found.

About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-04 23:21