Technical organization boundary
Praxis Software Structure Model
Engineering Maps
The root index is only responsible for the software structure document tree, version and navigation; the specific UML and explanations are located in each diagram directory.
Technical complexity index
Key technical objects
Run collaboration link
Run and deploy portal
Technical complexity hotspots
Software structure model document tree
Each graph type has its own maps document; each specific graph has an independent markdown/html document.
Package Diagrams
18 diagrams · docs/engineering/package-diagrams
Enter the package/module boundary dashboard and view how the 18 modules assume entry, contract, adaptation, shared capability, running assembly or infrastructure responsibilities according to the project directory, and continue to drill down to components, structures, sequences, deployment nodes and technical hotspots.
Component Diagrams
22 diagrams · docs/engineering/component-diagrams
Enter the component dashboard to view the responsibilities, referenced/calling relationships, external dependencies/calling relationships, belonging modules and drill-down risks of 22 key classes, functions, React components, command entrances or interface objects.
Deployment Diagrams
0 diagrams · docs/engineering/deployment-diagrams
Enter the running/deployment node dashboard to see how the build configuration, desktop shell, CLI, package management, CI or local running entry affects the startup, packaging and delivery path of the project.
Class / Structural Diagrams
10 diagrams · docs/engineering/class-structural-diagrams
Enter the structure collaboration dashboard and view how classes, interfaces and value objects form domain models, strategies, ports, adaptations or shared supports according to the nameable business/technical context; it is not a list of class names generated by the number of top-level layers or relationships.
Sequence Diagrams
18 diagrams · docs/engineering/sequence-diagrams
Enter the Sequence dashboard, view 18 real call fragments observed by local warehouse evidence, and supplement the static structure diagram with a dynamic collaboration perspective. Static import/reference will not be treated as a sequence diagram.
State Machine Diagrams
0 diagrams · docs/engineering/state-machine-diagrams
Enter the state machine dashboard; it will only be generated when there is evidence that key state fields, enumerations, or migration semantics do exist. Avoid making up fictitious state machines for UML.
Technical Hotspots
16 diagrams · docs/engineering/technical-hotspots
E