01
Run validation locally
Developers use the ArchPilot VS Code extension or CLI to validate architecture directly in their own environment.
How it works
A local-first workflow that turns architecture checks into a shared governance record.
ArchPilot separates validation from governance. Validation runs locally in VS Code and the CLI. ArchPilot Cloud stores only architecture metadata so teams can govern architecture across repositories and time.
Workflow summary
- Validate architecture locally in VS Code and CLI
- Sync architecture metadata to ArchPilot Cloud
- Track findings, scores, and history
- Govern architecture across repositories and teams
Overview
ArchPilot keeps validation local and makes governance shared.
The workflow is designed so developers get architecture feedback early, teams can run the same checks in CI, and the cloud becomes the place for governance visibility rather than hosted scanning.
02
Generate findings and metadata
The local validation run produces findings, scores, rule outcomes, and repository architecture metadata.
03
Sync metadata to Cloud
Only the governance metadata is synced to ArchPilot Cloud. The cloud does not need source code to store and organize the results.
04
Govern from shared history
Teams use the cloud workspace for visibility, policies, exceptions, ownership, and architecture history across repositories.
Step 1
Run validation locally in VS Code or the CLI
Developers validate architecture where code changes are actually made. The local-first workflow keeps feedback close to implementation and does not depend on a hosted scan.
- VS Code extension runs locally
- CLI runs locally
- Offline-friendly workflow
- Deterministic validation output
Step 2
Generate findings and architecture metadata
Local validation produces findings, scores, rule outcomes, and repository architecture metadata that can be shared without syncing source code.
- Findings and issues
- Repository scores
- Architecture summaries
- Policy outcomes
Step 3
Sync architecture metadata to ArchPilot Cloud
ArchPilot Cloud receives synced architecture metadata, not repository source code. This creates a shared governance record while preserving source code boundaries.
- No source code stored in cloud
- Metadata-only sync model
- Designed for security-conscious teams
- Clear product boundary between validation and governance
Step 4
Work from the governance workspace
The cloud workspace turns synced architecture metadata into organization-wide visibility across repositories and teams so architecture posture stays visible over time.
- Repository visibility
- Findings and scores
- Ownership context
- Multi-repository governance
Step 5
Use policies, scores, trends, and history to govern change
Teams use the cloud workspace to track architecture posture over time and act on the governance signals the local workflow produces.
- Policies and exceptions
- History and trends
- Repository score tracking
- Shared governance record
CI integration
Run the same architecture validation flow locally and in CI.
ArchPilot keeps the enforcement model consistent from the developer machine to automation, which helps teams move quickly without drifting away from architecture standards.
Same validation logic in CI
Teams can run the same architecture validation flow in CI that developers use locally, which keeps enforcement consistent.
Earlier feedback, fewer surprises
Developers get feedback before pushing code, while CI reinforces the same checks in automated pipelines.
Summary
Architecture visibility and governance for fast-moving engineering teams.
Validate locally, sync architecture metadata to the cloud workspace, and use it for findings, scores, policies, exceptions, history, and ownership context.