AtlasArc

Architecture Report - Printable Version

Vue Core - AtlasArc 1.0.1+736db9b9 - 2026-07-31T21:30:00Z

All selected report sections in one print-ready HTML document.

Section 1 of 3

Architecture Overview

Open this chapter

Key Findings

HighCycles

8 problem cycle groups reported in this report scope.

NeutralCoupling

NCCD is 1.50. Use it as a same-project dependency-shape baseline; inspect cycles and concrete paths before interpreting a change.

NeutralJVM public surface

JVM public-surface metrics are not available for the typescript-artifact backend.

NeutralGovernance

No Safe Havens or repository governance records are active; all findings are treated as active structural findings.

Highest-Value Targets

  1. packages.shared.srcArchitectural cycle participant, fan-in 25 / fan-out 1
  2. packages.runtime-core.srcArchitectural cycle participant, fan-in 10 / fan-out 5
  3. packages.compiler-dom.srcNested cycle participant, fan-in 8 / fan-out 3
  4. packages.runtime-dom.srcArchitectural cycle participant, fan-in 5 / fan-out 6
  5. packages.compiler-core.srcArchitectural cycle participant
  • The report reads package structure and dependency evidence; it does not know what the code is meant to do.
  • Coverage metrics are not loaded, so coverage-dependent risk readings are unavailable.
  • Package exclusions are disabled for this report context.

What This Report Says

Cycle risk is the dominant signal

Read this report as cycle-first evidence: resolve or consciously accept the reported cycle groups before treating lower-level metrics as optimization work.

  • 8 problem cycle groups reported in this report scope.
  • First source folder to inspect: packages.shared.src (Architectural cycle participant, fan-in 25 / fan-out 1).
  • Largest cycle group: Problem cycle 5 with 4 source folders.

Evidence Summary

NCCD1.50

Same-project dependency-shape baseline; compare only on an equivalent analysis basis.

Cycle groups8

Cycle clusters remain in the report scope.

Precise graph statistics remain available below so the report stays auditable.

CCDCumulative Component Dependency231.00
ACDAverage Component Dependency7.45
RACDRelative Average Component Dependency0.25
NCCDNormalized Cumulative Component Dependency1.50
ARVAverage Relative Visibilityn/a
GRVGlobal Relative Visibilityn/a

Architecture Overview Focus

This profile reads the whole model first: cycle posture, highest inspection target, and any governance context that changes how warnings should be interpreted.

Cycle posture8 groups

Start by comparing the cycle map with the cycle groups table.

Primary inspection targetpackages.shared.src

Architectural cycle participant, fan-in 25 / fan-out 1

Governance context0 Safe Havens / 0 debt records

Safe Havens, exclusions, and repository governance shape which findings remain active warnings.

Suggested Next Steps

1Start with Problem cycle 5

4 source folders participate in this architectural cycle group. Use the cycle table and topology figure to decide whether to break the loop or record an explicit governance decision.

2Inspect packages.shared.src

This source folder has the strongest combined structural signal in the report scope: Architectural cycle participant, fan-in 25 / fan-out 1.

Report Basis

SectionArchitecture Overview
Report basisWhole model
Active lensgraph
Structural intentNormal
FiltersWhole-model defaults; durable governance retained

Structural Map

Topology, cycle-only topology, and Matrix figures show broad source folders structure and cycle evidence from complementary angles.

Rendered as Topology Open

How do source folders and subsystems depend on each other in this report?

Configuration
Focus
project root
Filter
All visible source folders
Heatmap
Off
Encoding
Nodes
Source Folders and grouping folders
Edges
Source Folder dependencies; line width follows dependency weight
Border colour
Cycle, Safe Haven, intentional governance, and debt status from the model
arc-templatespackagesteacupcompiler-corecompiler-domcompiler-sfccompiler-ssrreactivityruntime-coreruntime-domruntime-testserver-renderersharedvuevue-compatsrcsrcsrcsrcsrcsrcsrc distcompattransformsSource filestransformsSource filesscriptstyletemplateSource filestransformsSource filessrccompatcomponentshelpersSource filescomponentsdirectiveshelpersmodulesSource filessrchelpersSource filessrcsrcsrcreact-domlibvue-core
Rendered as Dependency Matrix Open

Which source folders depend on which other source folders?

Configuration
Focus
project root
Filter
All visible source folders
Heatmap
Off
Encoding
Rows
Origin source folders
Columns
Target source folders
Cells
source file dependency count and cycle/heatmap styling where applicable
arc-templates
dist
packages
compiler-core
src
compat
transforms
compiler-dom
src
transforms
compiler-sfc
src
script
style
template
compiler-ssr
src
transforms
reactivity
src
runtime-core
src
compat
components
helpers
runtime-dom
src
components
directives
helpers
modules
runtime-test
src
server-renderer
src
helpers
shared
src
vue
vue-compat
src
src
react-dom
teacup
lib
vue-core
▼ arc-templates -
  dist -
▼ packages -
▼ compiler-core -
▼ src - 3 26 7
  compat 3 -
  transforms 61 1 - 12
▼ compiler-dom -
▼ src 4 - 10 2
  transforms 9 11 - 3
▼ compiler-sfc -
▼ src 3 4 - 18 7 2 1 3
  script 6 5 - 1 4 3
  style 1 1 - 2
  template 2 - 2 3
▼ compiler-ssr -
▼ src 4 - 14 1
  transforms 13 19 - 2
▼ reactivity -
  src - 8
▼ runtime-core -
▼ src 19 - 20 16 17 28
  compat 2 26 - 6 15
  components 1 27 - 1 4
  helpers 3 19 - 8
▼ runtime-dom -
▼ src 3 - 2 3 2 5 3
  components 2 - 1 2
  directives 2 - 1 2
  helpers 2 - 2
  modules 4 1 1 1 1 - 4
▼ runtime-test -
  src 1 1 - 4
▼ server-renderer -
▼ src 4 - 12 4 1
  helpers 1 6 4 - 7
▼ shared -
  src 1 -
▼ vue -
▼ vue-compat -
  src 1 1 1 5 2 -
  src 1 3 1 -
  react-dom -
▼ teacup -
  lib -
  vue-core -

Hierarchy & Size

Composition figures show how code size and source folders are distributed through the selected scope.

Rendered as Composition · Sunburst Open

Where is the analysed codebase concentrated across the source folder hierarchy?

Configuration
Focus
project root
View
Sunburst
Size metric
Lines of code
Heatmap
Off
Encoding
Arc
Source Folder hierarchy segment
Arc size
Relative lines of code
Colour
Hierarchy depth
packages p.runtime-core p.compiler-core p.compiler-sfc p.runtime-dom p.reactivity p.compiler-ssr p.compiler-dom server-renderer packages.shared p.runtime-test p.r.src p.c.src p.c.src p.r.src p.r.src p.c.src p.c.src p.s.src p.shared.src p.r.src p.r.src.compat components p.r.src.helpers transforms p.c.src.compat p.c.src.script p.c.src.style p.c.s.template components directives p.r.src.modules transforms transforms p.s.src.helpers project root
Rendered as Composition · Circle Pack Open

How does the same hierarchy read as nested containment rather than radial depth?

Configuration
Focus
project root
View
Circle Pack
Size metric
Lines of code
Heatmap
Off
Encoding
Circle
Source Folder hierarchy segment
Area
Relative lines of code
Colour
Hierarchy depth
p.s.src directives p.r.s.components p.r.src.helpers p.r.src.modules p.c.src.style p.c.s.template p.runtime-test p.c.src.transforms packages.shared.src compat vue-compat p.c.src.transforms p.vue p.runtime-core.src.components packages.runtime-core.src.compat helpers packages.runtime-dom.src packages.compiler-core.src.transforms packages.reactivity.src packages.compiler-sfc.src.script packages

Governance Summary

Repository documentReady
Revisionmissing
EvidenceFresh
Local view exclusionsNone
Safe Havens0
Intentional records0
Debt records0
Maintenance findings0
CoverageNot loaded

Metric Notes

CCD, ACD, RACD, and NCCD describe structural graph shape. Source Folder tables include fan-in, fan-out, instability, and line count. Dependency scope: source architecture dependencies. Type-only imports are included as source coupling. Metrics not available for the typescript-artifact backend are rendered as n/a or omitted from tables.

Section 2 of 3

Cycle Evidence

Open this chapter

Cycle Evidence Briefing

This section separates current problem cycles from governance audit work. Repository decisions remain concise structural context here; their rationale and maintenance history live only in the optional Governance Audit.

Reported groups8
Debt records0
Intentional records0
Safe Havens0
Cycle modeAll cycle groups
Governed edge listIncluded
TypesArchitectural: 5, Nested: 3

All Problem Cycles Overview

One combined downward-layout topology shows how the current problem cycle groups sit together. It is included only when more than one group exists.

Rendered as Topology · Cycles Only Open

Which cycle warnings remain when non-cycle dependency structure is stripped away?

Configuration
Focus
project root
Filter
Cycles only
Heatmap
Off
Encoding
Nodes
Only source folders needed to show reported cycle evidence
Edges
Cycle-participating dependencies after governance rules are applied
Border colour
Problem, Safe Haven, intentional governance, and debt cycle status
  • This overview orients the cycle focus maps below.
packagescompiler-corecompiler-domcompiler-sfccompiler-ssrreactivityruntime-coreruntime-domserver-renderersharedsrcsrcsrcsrcsrcsrcsrc compattransformsSource filestransformsSource filesscriptstyleSource filestransformsSource filessrccompatcomponentshelpersSource filescomponentsdirectivesmodulesSource fileshelpersSource filessrc

Problem Cycles

Each card is one current problem strongly connected component. Every group gets one compact horizontal map. When additional maps are requested, a second map appears only when its focused architecture units or dependency edges strictly extend the compact evidence; layout-only duplicates are suppressed.

Problem cycle 1

Architectural cycle

3 source folders5 cycle edges
packagescompiler-coresrc compattransforms
Source Folders
  • packages.compiler-core.src
  • packages.compiler-core.src.compat
  • packages.compiler-core.src.transforms
Problem cycle 2

Nested cycle

2 source folders2 cycle edges
packagescompiler-domsrc transforms
Source Folders
  • packages.compiler-dom.src
  • packages.compiler-dom.src.transforms
Problem cycle 3

Architectural cycle

3 source folders5 cycle edges
packagescompiler-sfcsrc scriptstyle
Source Folders
  • packages.compiler-sfc.src
  • packages.compiler-sfc.src.script
  • packages.compiler-sfc.src.style
Problem cycle 4

Nested cycle

2 source folders2 cycle edges
packagescompiler-ssrsrc transforms
Source Folders
  • packages.compiler-ssr.src
  • packages.compiler-ssr.src.transforms
Problem cycle 5

Architectural cycle

2 source folders2 cycle edges
packagesreactivityshared srcsrc
Source Folders
  • packages.reactivity.src
  • packages.shared.src
Problem cycle 6

Architectural cycle

4 source folders8 cycle edges
packagesruntime-coresrc compatcomponentshelpers
Source Folders
  • packages.runtime-core.src
  • packages.runtime-core.src.compat
  • packages.runtime-core.src.components
  • packages.runtime-core.src.helpers
Problem cycle 7

Architectural cycle

4 source folders8 cycle edges
packagesruntime-domsrc componentsdirectivesmodules
Source Folders
  • packages.runtime-dom.src
  • packages.runtime-dom.src.components
  • packages.runtime-dom.src.directives
  • packages.runtime-dom.src.modules
Problem cycle 8

Nested cycle

2 source folders2 cycle edges
packagesserver-renderersrc helpers
Source Folders
  • packages.server-renderer.src
  • packages.server-renderer.src.helpers

Problem Cycle Edges

These are the strongest currently reported problem-cycle edges. They are not fully covered by repository governance and are not removed by Safe Havens in this report scope. The Dependency refs value counts acquired source file dependency references aggregated into each source folder-to-source folder edge; it is not a source line number.

Dependency refsCycleGovernance
Sourcepackages.compiler-core.src.transforms
Targetpackages.compiler-core.src
61NestedProblem
Sourcepackages.runtime-core.src.components
Targetpackages.runtime-core.src
27NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.transforms
26NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src
26NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.compat
20NestedProblem
Sourcepackages.compiler-ssr.src.transforms
Targetpackages.compiler-ssr.src
19NestedProblem
Sourcepackages.runtime-core.src.helpers
Targetpackages.runtime-core.src
19NestedProblem
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.script
18NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.helpers
17NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.components
16NestedProblem
Sourcepackages.compiler-ssr.src
Targetpackages.compiler-ssr.src.transforms
14NestedProblem
Sourcepackages.server-renderer.src
Targetpackages.server-renderer.src.helpers
12NestedProblem
Sourcepackages.compiler-dom.src.transforms
Targetpackages.compiler-dom.src
11NestedProblem
Sourcepackages.compiler-dom.src
Targetpackages.compiler-dom.src.transforms
10NestedProblem
Sourcepackages.reactivity.src
Targetpackages.shared.src
8ArchitecturalProblem
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.style
7NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src.helpers
6ArchitecturalProblem
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-sfc.src
5NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.modules
5NestedProblem
Sourcepackages.server-renderer.src.helpers
Targetpackages.server-renderer.src
4NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.compat
3NestedProblem
Sourcepackages.compiler-core.src.compat
Targetpackages.compiler-core.src
3NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.directives
3NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.components
2NestedProblem
Sourcepackages.compiler-core.src.transforms
Targetpackages.compiler-core.src.compat
1ArchitecturalProblem
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-sfc.src.style
1ArchitecturalProblem
Sourcepackages.compiler-sfc.src.style
Targetpackages.compiler-sfc.src
1NestedProblem
Sourcepackages.runtime-core.src.components
Targetpackages.runtime-core.src.helpers
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.components
Targetpackages.runtime-dom.src.directives
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.directives
Targetpackages.runtime-dom.src.modules
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src
1NestedProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src.components
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src.directives
1ArchitecturalProblem
Sourcepackages.shared.src
Targetpackages.reactivity.src
1ArchitecturalProblem

Cycle Dependency Matrix

The cycle-only Matrix gives directional source folder-to-source folder dependency evidence complementary to the diagrams.

Rendered as Dependency Matrix · Cycles Only Open

Which reported cycle dependencies remain when non-cycle structure is stripped away?

Configuration
Focus
project root
Filter
Cycles only
Heatmap
Off
Encoding
Rows
Origin source folders in reported cycle evidence
Columns
Target source folders in reported cycle evidence
Cells
Cycle-participating dependency count and governance styling
  • This matrix is rendered from the cycle-only report model, not the full global architecture model.
packages
compiler-core
src
compat
transforms
compiler-dom
src
transforms
compiler-sfc
src
script
style
compiler-ssr
src
transforms
reactivity
src
runtime-core
src
compat
components
helpers
runtime-dom
src
components
directives
modules
server-renderer
src
helpers
shared
src
▼ packages -
▼ compiler-core -
▼ src - 3 26
  compat 3 -
  transforms 61 1 -
▼ compiler-dom -
▼ src - 10
  transforms 11 -
▼ compiler-sfc -
▼ src - 18 7
  script 5 - 1
  style 1 -
▼ compiler-ssr -
▼ src - 14
  transforms 19 -
▼ reactivity -
  src - 8
▼ runtime-core -
▼ src - 20 16 17
  compat 26 - 6
  components 27 - 1
  helpers 19 -
▼ runtime-dom -
▼ src - 2 3 5
  components - 1
  directives - 1
  modules 1 1 1 -
▼ server-renderer -
▼ src - 12
  helpers 4 -
▼ shared -
  src 1 -
Section 3 of 3

Hotspot Risk

Open this chapter

Refactoring Risk Briefing

This chapter ranks source folder-level risk signals before the diagrams: coupling pressure, cycle participation.

Source Folders ranked31
High coupling4
Cycle source folders22
CoverageNot loaded

Top Risk Drivers

Primary driverFan-inFan-out
Source Folderpackages.shared.src
Cycle participation251
Source Folderpackages.runtime-core.src
Cycle participation105
Source Folderpackages.compiler-dom.src
Cycle participation83
Source Folderpackages.runtime-dom.src
Cycle participation56
Source Folderpackages.compiler-core.src
Cycle participation63
Source Folderpackages.compiler-sfc.src
Cycle participation27
Source Folderpackages.runtime-dom.src.modules
Cycle participation26
Source Folderpackages.reactivity.src
Cycle participation61

Subsystem-Level Architecture

Subsystem figures summarize boundary pressure, internal cohesion, and recursive architecture signals.

Rendered as Subsystems · Boundary Risk Open

Where does boundary pressure concentrate across the visible architecture?

Configuration
Focus
project root
Curated view
Boundary Risk
Filter
All visible source folders
Encoding
Bubble
Package-folder subsystem rollup
X axis
Fan-out
Y axis
Fan-in
Size
Source files
Colour
Instability
  • How to read this graph: each bubble is a visible architecture-boundary rollup. Right means more outgoing boundary dependencies; up means more incoming boundary dependencies; size is total class count.
  • Colour follows instability, so red means outgoing-heavy rather than automatically wrong. Use the figure to find boundary surfaces worth inspecting in Topology or Matrix.
  • Dashed rings mark expanded aggregate boundaries whose visible descendants are also present. Terminal packages or source folders remain valid boundaries and use their own metrics.
Fan-in
0 2 4 6 8 10 12 0 5 10 15 20 25 packages runtime-core src vue-core compiler-core src compiler-sfc src compiler-ssr src compat runtime-dom src
Fan-out
Rendered as Subsystems · Internal Tangles Open

Which subsystem areas contain internal cycle pressure?

Configuration
Focus
project root
Curated view
Internal Tangles
Filter
All visible source folders
Encoding
Bubble
Package-folder subsystem rollup
X axis
cycleCount
Y axis
largestCycle
Size
packageCount
Colour
Cycle status
  • How to read this graph: each bubble is a visible architecture-boundary rollup. Right means more fully contained package-cycle groups; up means the largest contained package cycle is larger; size is package count.
  • Only package cycles fully inside the boundary count here. Terminal-package class/file tangles remain separate Package Internals evidence in Topology. Use the cycle tables, Topology, or Matrix for concrete dependency edges and cross-boundary cycle context.
  • Dashed rings mark expanded aggregate boundaries whose visible descendants are also present. Terminal packages or source folders remain valid boundaries and use their own metrics.
Largest cycle
0 2 4 6 8 0 1 2 3 4 packages runtime-dom src compiler-sfc src runtime-core src compiler-core src compiler-dom src compiler-ssr src server-renderer src
Cycle groups

Source Folder Hotspots

Hotspot figures rank source folders by available metric-space risk signals such as coupling and complexity.

Rendered as Hotspots · Coupling Open

Which leaf source folders stand out by coupling pressure?

Configuration
Items
Leaf source folders
Focus
project root
Scope
Recursive
Preset
Coupling
Encoding
Bubble
One leaf source folder
X axis
Fan-out
Y axis
Fan-in
Size
Lines of code
Colour
Instability
  • Labels are shown for the largest report bubbles; inspect the source folder metrics table for the full ranked list.
Fan-in
0 2 4 6 0 5 10 15 20 25 src src script src transforms src src compat components transforms src
Fan-out

Source Folder Metrics

This table ranks source folders by structural signals. Use it to inspect source folders that combine high fan-in, high fan-out, cycle membership or size.

Fan-inFan-outInstabilityCycleLOC
Source Folderpackages.shared.src
2510.04Architectural983
Source Folderpackages.runtime-core.src
1050.33Architectural13748
Source Folderpackages.compiler-dom.src
830.27Nested432
Source Folderpackages.runtime-dom.src
560.55Architectural2726
Source Folderpackages.compiler-core.src
630.33Architectural6438
Source Folderpackages.compiler-sfc.src
270.78Architectural2551
Source Folderpackages.runtime-dom.src.modules
260.75Architectural523
Source Folderpackages.reactivity.src
610.14Architectural3573
Source Folderpackages.compiler-sfc.src.script
150.83Architectural3925
Source Folderpackages.compiler-ssr.src
330.50Nested415
Source Folderpackages.runtime-core.src.compat
240.67Architectural2442
Source Folderpackages.runtime-core.src.helpers
330.50Architectural684
Source Folderpackages.runtime-dom.src.directives
330.50Architectural575
Source Folderpackages.compiler-sfc.src.style
230.60Architectural758
Source Folderpackages.runtime-core.src.components
140.80Architectural2417
Source Folderpackages.runtime-dom.src.components
230.60Architectural683
Source Folderpackages.server-renderer.src
140.80Nested743
Source Folderpackages.server-renderer.src.helpers
140.80Nested526
Source Folderpackages.vue-compat.src
051.00—182
Source Folderpackages.compiler-core.src.transforms
130.75Architectural3563
Source Folderpackages.compiler-dom.src.transforms
130.75Nested899
Source Folderpackages.compiler-sfc.src.template
130.75—471
Source Folderpackages.compiler-ssr.src.transforms
130.75Nested1698
Source Folderpackages.runtime-dom.src.helpers
220.50—129
Source Folderpackages.compiler-core.src.compat
210.33Architectural314
Source Folderpackages.runtime-test.src
031.00—372
Source Folderpackages.vue.src
031.00—127
Source Foldervue-core
300.00—0
Source Folderarc-templates.dist
00——0
Source Folderreact-dom
00——0
Source Folderteacup.lib
00——0