openai / orion-multistep-analysis
Components

An overview of source code logical components.

Intro

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.
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

  • primary (4 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 4 components.
  • 63 files, 7,495 LOC (100.0% vs. main code).
  • "frontend" is biggest, containing 55.61% of LOC.
  • "ROOT" is smallest, containing 0.13% of LOC.


frontend4168 LOC (55%) 19 files
src3298 LOC (44%) 41 files
scripts19 LOC (<1%) 1 file
ROOT10 LOC (<1%) 2 files


2026-06-24 10:42