Which file should I inspect first in Trigger.dev (packages/trigger-sdk)?

Start with src/v3/tracer. Run arc impact on that file before the change merges.

← Homepage All repository proof Validation record State of TS Architecture 2026

Repository proof

What ArcSight found in Trigger.dev

Real arc impact on Trigger.dev (packages/trigger-sdk) — blast radius, break paths, and evidence. Same question as the homepage: what breaks if I change this?

Project: Trigger.dev (packages/trigger-sdk) · Score: 92.7/100 (Excellent architecture) · 49 modules · 93 edges

arc impact src/v3/tracer

Install ArcSight →Why trust ArcSight →

Run the same analysis on your repository in under 3 minutes.

Proof summary

Four questions every public repository page must answer — see validation record.

Modules to inspect

One row per module. Fan-in is direct dependents. Blast radius is downstream modules reachable from that file.

Fan-in, direct dependents

src/v3/tracer17 dependents
src/v3/shared7 dependents
src/v3/ai-shared5 dependents
src/imports/ai-runtime3 dependents
src/v3/prompt3 dependents
src/v3/sessions3 dependents
src/v3/locals3 dependents
src/version1 dependents

Blast radius, downstream modules

src/v3/tracer24 modules
src/v3/shared7 modules
src/v3/ai-shared5 modules
src/imports/ai-runtime5 modules
src/v3/prompt5 modules
src/v3/sessions5 modules
src/v3/locals4 modules

Module	Fan-in	Blast	Risk
src/v3/tracer	17	24	MEDIUM
src/v3/shared	7	7	LOW
src/v3/ai-shared	5	5	LOW
src/imports/ai-runtime	3	5	LOW
src/v3/prompt	3	5	HIGH
src/v3/sessions	3	5	HIGH
src/v3/locals	3	4	HIGH
src/version	1		LOW

What ArcSight found

src/v3/tracer: fan-in 17, blast radius 24, MEDIUM. 49 modules and 93 dependency edges traced.

Why it matters

In Trigger.dev (packages/trigger-sdk), Change-risk signal at src/v3/tracer (fan-in 17) — merge impact can travel beyond the diff you see. Blast radius on src/v3/tracer reaches 24 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.

What we'd inspect first

src/v3/tracer
src/v3/shared
src/v3/ai-shared

What evidence supports it

Local CLI analysis — repository source stays on your machine
Structural coverage: 49 modules, 93 edges in this snapshot
Reproducible fields match homepage live demo and frozen proof output

Architectural Risk Map

Where risk accumulates by control surface — drill down Surface → Substrate → Mechanism → Evidence.

See control surfaces →

Dependency evidence

Architecture visualization

Diagrams are generated from ArcSight analysis data. Dependency graph and risk map show key modules; subsystem view shows high-level structure.

Dependency graph for this codebase — Dependency graph

Subsystem architecture for this codebase — Subsystem architecture

Architecture score & metrics

Score: 92.7/100 · Stability: 61/100 · Status: healthy · Confidence: 100%

Duplicate authorities: 19

Architectural gravity centers

src/v3/tracer— concentrates too many responsibilities
src/v3/tracer— shared utility hub

CLI workflow

Impact, then scan, fix, finish, and watch.

arc impact <file>See what a change breaks
arc scanFind issues
arc fixApply fixes
arc finishResolve remaining
arc watchKeep clean

More commands (explain, guard…) →

Trigger.dev (packages/trigger-sdk) architecture metrics

Score: 92.7
Modules: 49
Edges: 93

Metrics

Metric	Value
Architecture score	92.7/100
Modules	49
Edges	93

FAQ

What did ArcSight find in Trigger.dev (packages/trigger-sdk)?: src/v3/tracer: fan-in 17, blast radius 24, MEDIUM. 49 modules and 93 dependency edges traced.
Why does the Trigger.dev (packages/trigger-sdk) structure matter?: In Trigger.dev (packages/trigger-sdk), Change-risk signal at src/v3/tracer (fan-in 17) — merge impact can travel beyond the diff you see. Blast radius on src/v3/tracer reaches 24 downstream modules. ArcSight answers “what breaks if I change this?” before you ship; high fan-in is a change-risk signal, not a verdict on design quality.
Which file should I inspect first in Trigger.dev (packages/trigger-sdk)?: Start with src/v3/tracer. Run arc impact on that file before the change merges.

Key takeaways

•Architecture score 92.7/100 indicates a healthy structure with room to reduce cycles and violations.
•High fan-in modules are change-risk zones; run arc explain <path> before refactoring.
•Run the full workflow (analyze, hotspots, explain, impact, snapshot, drift) in your repo for deterministic architecture insights.

Run ArcSight on your repo

Install locally, then run arc impact on the file you plan to change — before merge.

npm install -g arcsight

arc impact <path>

Install ArcSight →

Embed this report

Use this iframe to show the architecture badge on your site.

<iframe src="https://arcsight.ai/embed/trigger/" width="320" height="180" frameborder="0"></iframe>

Evidence-backed analysis snapshot. Validation record · Install · Homepage demo