ARC — Audit Layer for AI-Assisted Coding
ARC XT — Audit Ready Core is the first live product: a local-first VS Code extension that brings the ARC audit layer into the moment of change.
ARC introduces a deterministic, tamper-evident audit layer inside your IDE.
It records and verifies every critical code decision at the moment it’s made — before it reaches PR, CI, or production.
In an AI-assisted workflow where code is generated faster than it can be reviewed, ARC ensures every change is accountable, traceable, and verifiable.
AI (Copilot / Cursor / Claude)
↓
ARC (Audit Layer)
↓
Git / PR / CI
Status
Status: Controlled internal release (Stage 4)
Distribution: Direct VSIX transfer to authorized operators
Feedback: Internal pilot channels
Current product posture:
- local-first by default
- cloud lanes disabled by default
- suitable for authorized developer testing and workflow feedback
- not authorized for public marketplace or broad external distribution
Quick Start
Install
From VSIX
- Download the latest
.vsix from the releases page
- In VS Code: Extensions →
... → Install from VSIX...
- Select the downloaded
.vsix file
- Reload VS Code when prompted
Verify Installation
- Open any code file in your workspace
- Make a change to a governed file such as
auth.ts, schema.sql, or package.json
- Attempt to save — ARC XT will prompt for acknowledgment or proof when required
- Use
Ctrl+Shift+P → ARC XT: Review Audit Log to inspect recent decisions
What ARC XT Does
| Decision |
When |
Action Required |
| ALLOW |
Low-risk changes such as UI components or tests |
None — save proceeds |
| WARN |
Medium-risk changes such as config or schema edits |
Acknowledge risk before save |
| REQUIRE_PLAN |
High-risk changes such as auth or core logic |
Link to governance blueprint proof |
| BLOCK |
Critical-risk violations |
Save blocked — address the risk first |
Key Features
- Local-first — enforcement happens locally; no cloud dependency is required
- Audit trail — append-only record of save decisions with hash-chain integrity
- Blueprint proofs — high-risk changes can be linked to governance directives
- Review surfaces — built-in UI for audit inspection, proof review, and decision context
- Fail-closed — missing configuration defaults to the strictest safe posture
Requirements
- VS Code
1.90.0 or later
- Node.js
20+ only if you want to build from source
- No external services required
- Optional: Ollama for local AI evaluation experiments
Configuration
ARC XT works out of the box with sensible defaults. Optional configuration lives in .arc/router.json:
{
"mode": "RULE_ONLY",
"localLaneEnabled": false,
"cloudLaneEnabled": false
}
| Setting |
Default |
Description |
mode |
RULE_ONLY |
Enforcement mode (RULE_ONLY, LOCAL_PREFERRED, CLOUD_ASSISTED) |
localLaneEnabled |
false |
Enable local AI model evaluation |
cloudLaneEnabled |
false |
Enable cloud fallback only after explicit approval |
Commands
| Command |
Description |
ARC XT: Review Home |
Open the main ARC XT review surface |
ARC XT: Decision Feed |
View recent enforcement decisions |
ARC XT: Audit Timeline |
Inspect chronological audit entries |
ARC XT: Why Panel |
Explain the current or recent decision |
ARC XT: Review Audit Log |
Inspect recent save decisions |
ARC XT: Show Active Workspace Status |
View current workspace targeting and route posture |
ARC XT: Review Blueprint Proofs |
Review linked governance blueprints |
ARC XT: Review False-Positive Candidates |
Advisory review of potential false positives |
ARC XT: Show Welcome Guide |
Display onboarding information |
Limitations
- Heuristic classification — risk assessment is rule-based, not full semantic understanding
- File-level audit integrity — hash chains verify individual files, not archive completeness
- Local-only blueprints — shared/team blueprint deployment is not yet supported
- Cloud disabled by default — cloud fallback requires explicit configuration and approval
- Observational diagnostics only — status surfaces describe posture; they do not authorize changes
FAQ
What programming languages does ARC XT support?
ARC XT is language-agnostic at the VS Code save layer. Today its built-in rules are strongest for common config, auth, and schema files such as package.json, .env, schema.sql, *.sql, and *.prisma.
How does ARC XT detect high-risk changes?
ARC XT currently uses heuristic rules based on file paths, filenames, and extensions. For example, auth/session paths and core config files can trigger higher-risk handling, while schema files often trigger review-aware warnings.
Can I disable cloud options?
Yes. Cloud is disabled by default. If you do not want cloud fallback, keep cloudLaneEnabled: false in .arc/router.json. RULE_ONLY mode also works without cloud services.
How will ARC XT affect my workflow?
Most low-risk saves continue normally. Medium-risk saves may ask for acknowledgment, and higher-risk saves may require a linked plan or proof before the save proceeds. The goal is to add friction only where risk is higher.
How does ARC XT help with code security?
ARC XT improves security posture through local-first enforcement, fail-closed defaults, visible save-time decisions, append-only audit logging, and proof-backed handling for higher-risk changes. It is a governance and review layer, not a full semantic security scanner.
Support
Learn More
For deeper technical and governance details, see:
docs/ARCHITECTURE.md
docs/CODE_MAP.md
docs/TESTING.md
docs/BETA-RELEASE-CHECKLIST.md
For retained validation and evidence artifacts, see:
artifacts/ARC-UX-VALIDATION-001-LOG.md
artifacts/evidence/ARC-UX-VALIDATION-001/