AtlasArc

Architecture Overview

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

A whole-model architecture report for the current analysis.

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

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.