• There are 20 files with 1,460 lines of code.
• 0 very long files (0 lines of code)
• 0 long files (0 lines of code)
• 3 medium size files (741 lines of code)
• 2 small files (208 lines of code)
• 15 very small files (511 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
cfn.yaml in root	316	~2k–5k	9	~20	~20
TestEventLoader.scala in src/main/scala/payment_failure_comms	222	~1.5k–5k	2	~70	~3
Handler.scala in src/main/scala/payment_failure_comms	105	~700–1.5k	2	~15	~7
brazeTrackEvents.scala in src/main/scala/payment_failure_comms/models	103	~700–1.5k	1	~20	~5
PaymentFailureRecordUpdate.scala in src/main/scala/payment_failure_comms/models	49	under 1k	1	~30	~2
EventTime.scala in src/main/scala/payment_failure_comms/models	24	under 1k	1	~10	~2

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

There are 2 files with lines longer than 120 characters. In total, there are 6 long lines.

File	# lines	# units	# long lines
cfn.yaml in root	316	-	5
brazeTrackEvents.scala in src/main/scala/payment_failure_comms/models	103	2	1

• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.