I generated a deterministic execution level structural context for the cal.com repository directly from source code.

[Arc-a-it]

It surfaces real coordination hubs and blast-radius risks that aren’t obvious when reading files individually.

Notable findings:

packages/features/schedules/repositories/ScheduleRepository.ts is a central scheduling hub (24-file blast radius), meaning changes here propagate widely across the system.

CredentialRepository.ts has similarly broad impact, making credential logic a high-risk coordination point.

Parts of the RPC availability API act as aggregation layers where small changes can cascade through scheduling and routing.

This is not documentation or a file index — it’s a machine-derived snapshot of how execution and dependencies actually flow.

Sharing in case it’s useful for onboarding, reviews, or AI context.
No action required.

Canonical context (JSON):
Uploading arcvision.context.json…

Human-readable summary:
README.md