Repository facts
Source structure, dependencies, Git signals, architecture findings, and history are established before optional model reasoning.
Evidence flows
through the system.
Vericore separates deterministic repository facts from higher-level reasoning and delivery surfaces so engineering outputs remain traceable to evidence and repository state.
INPUTRepository + GitJava/Kotlin source · history · working-tree state
↓
ANALYSISScanner + parsers + Git intelligenceStructure · dependencies · cycles · PageRank · churn · authorship · evolution · reports
↓
ARTIFACTAnalysis Snapshot + Engineering ContextVersioned signals, repository-relative fingerprints, stable digests, context snapshots and diffs
↓
REALITYEngineering RealityDeterministic identity binding analysis and repository context; stale analysis can be rejected
↓
GROUNDINGEvidence + deterministic intelligenceImpact · PR · architecture · drift · Q&A retrieval · test signals · planning inputs · provenance
↓
OUTPUTRepository Q&AIntent classification, bounded evidence, deterministic ranking, optional AI
OUTPUTEngineering PlannerRead-only implementation and verification plan from grounded evidence
GOVERNANCEArchitecture ContractsExplicit baseline, limits, deterministic decisions and idempotent records
↓
SAFETYPrepare → Change → VerifyPersist Agent Change Contract before implementation; verify the original artifact afterwards
↓
DELIVERYCLI · REST · MCP · CI · HTMLLocal workflows, trusted agent integration, automated verification, self-contained reports
Engineering Reality
Analysis and repository context receive a deterministic identity. Wall-clock timestamps do not silently make equivalent state look different.
Architecture contracts
Explicit baselines can be evaluated against findings, cycles, and layer limits with stable decision records.
Persisted change boundary
The Agent Change Contract binds planned paths, evidence, verification commands, architecture expectations, and repository identity. Verify checks the persisted contract rather than regenerating it.
Reasoning is downstream
AI is disabled unless configured. When invoked, providers receive bounded repository-derived context instead of being treated as the source of repository truth.
Local interfaces
The CLI is the primary workflow surface; REST and MCP expose local/internal integrations. Neither is an authentication or tenant-isolation layer.
THE BOUNDARY MODEL
Each layer narrows what can be assumed.
Vericore does not jump from source code to an AI answer. Evidence is progressively shaped into state, decisions, and a verifiable change boundary.
Repository
Source, Git history, and working-tree state
Deterministic analysis
Structure, dependencies, cycles, PageRank, churn, architecture, evolution
Context + Reality
Versioned context, repository fingerprint, Git HEAD binding, deterministic identity
Evidence
Bounded citations and deterministic intelligence for impact, PR, Q&A, tests, and planning
Change boundary
Engineering plan plus persisted Agent Change Contract
Verification
Original prepared artifact checked against the changed repository