Repositories & Snapshots

What a repository record gives you

Repository coverage and retained snapshot history vary by plan.

• A stable identity for shared governance history
• Latest architecture posture and findings context
• Ownership links to teams and systems
• A place for snapshots, findings, and related governance workflows

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 the architecture score, readiness, findings counts, enforcement signal, risk context, and other repository governance metadata that Cloud can track over time.

Architecture inventory in snapshots

When the uploaded snapshot includes architecture inventory, Cloud can display components, resources, and cross-component dependency signals without changing validation semantics.

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 uploaded metadata.

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.