Start with a path.
Go deeper when you're ready.
The website gives you the product model. The Vericore repository remains authoritative for implementation details, contracts, schemas, limitations, and current behavior.
What are you trying to do?
Understand the product before going deep.
Getting Started → Architecture → DemoGo from installation to a real local workflow.
Getting Started → How to Use → Change SafetyUnderstand the boundary between AI reasoning and verified change.
Engineering Reality → MCP → Change SafetyInspect data flow, API boundaries, and security constraints.
Data & Privacy → API → SecurityExplore the system.
Go directly to the source material when you need implementation-level detail.
Getting Started ↗
Shortest path from installation to your first local analysis.
REFERENCEArchitecture ↗
System model, package boundaries, evidence flow, and deterministic layers.
REFERENCEEngineering Reality ↗
How analysis and repository context become a deterministic state identity.
REFERENCEChange Safety ↗
Prepare, persisted Agent Change Contracts, verification, tamper and stale-state behavior.
REFERENCEREST API ↗
Local Ktor API surface, path boundaries, health endpoints, and request behavior.
REFERENCEMCP / AI Agents ↗
Local MCP tools, safety boundary, and persisted change-contract integration.
REFERENCEPR Intelligence ↗
Pull-request change analysis, risk signals, architecture findings, and evidence.
REFERENCEData & Privacy ↗
Local-first data flow, AI provider boundaries, generated artifacts, and limits.
REFERENCEDevelopment ↗
Project structure, tests, CI, contributor workflow, and implementation guidance.
REFERENCEImplementation Status ↗
Implemented capabilities, current limitations, and explicit future direction.
REFERENCESecurity ↗
Security policy and vulnerability reporting guidance.
Vericore v0.7.0
For installation, platform artifacts, checksums, and release notes, use the GitHub release archive and the authoritative implementation docs in the main Vericore repository.