Repositories

What a repository record gives you

Repository coverage and retained snapshot history vary by plan.

• Repository dashboard for shared governance history
• Latest architecture posture and repository health
• Repository findings and finding details
• Repository inventory and module views
• Snapshot history and Snapshot Diff
• Repository Intelligence and Blast Radius on Team and above
• Ownership links to teams and systems
• Policy, exception, and affected repository context

What a snapshot represents

A snapshot is a point-in-time governance record derived from a local ArchPilot validation run and optional governance upload.

It captures architecture score, setup readiness, findings counts, enforcement signal, risk context, and available architecture inventory so Cloud can track repository posture over time.

Repository inventory

Repository inventory shows the architecture entities available for the repository: components, resources, modules, and related dependency signals.

Components are logical units such as apps, services, libraries, workers, and infrastructure packages. Modules remain code-level groupings inside a component. Resources are external or system dependencies such as APIs, databases, queues, storage, and infrastructure.

• Monorepo example: web app, API service, background worker, and shared package components.
• Service example: a backend service with worker and shared library components plus queue and database resources.
• Product app example: frontend component, API component, and database resource linked through architecture inventory.

Repository intelligence

Team and above can use Repository Intelligence, Snapshot Diff, and Blast Radius to understand repository-level trends, hotspots, architecture insights, ownership impact, and posture movement.

• Use Snapshot Diff to compare repository snapshots and see what changed.
• Use Repository Intelligence to review repository trends, hotspots, and architecture insights.
• Use Blast Radius to understand ownership and repository impact when posture changes occur.

Why this matters

A single local result is useful for an engineer. Snapshot history is what makes architecture governance useful for a team, a platform group, or an engineering organization.

Snapshots let Cloud show trend and drift over time without moving the validation engine out of local workflows, which is how architecture results become operational instead of one-off.

Manual governance upload is available on all plans. Automatic CI upload to Cloud on main is available on paid plans.