Core Concepts

VibePro works by keeping product intent, technical constraints, and evidence in separate but connected artifacts.

Story

A story states the user value, scope, acceptance criteria, and relevant source documents for a change.

Stories can live under the target repository's VibePro workspace or in project documentation. They are the anchor for checks, verification records, agent reviews, and PR evidence.

Architecture

Architecture documents describe boundaries and responsibilities that a change must respect. They help VibePro and AI agents reason about blast radius instead of treating every file as equally safe to change.

Spec

Specs define behavioral requirements and invariants. VibePro uses them to connect acceptance criteria to code, verification, and review evidence.

Verification evidence

Verification evidence records commands and observations that actually ran against the current git state.

Common kinds include:

• unit
• integration
• e2e
• typecheck
• build

Agent Review

Agent Review is a structured review loop for AI subagents. VibePro can prepare role-specific requests, track lifecycle state, and require completed review evidence before PR readiness.

Gate DAG

The Gate DAG is the dependency graph for readiness. It shows which evidence, decisions, reviews, or waivers are required before PR creation.

Small documentation changes may have a light gate set. Workflow-heavy changes can add gates for replay coverage, production path confidence, release risk, preview smoke, network/runtime behavior, or broader review roles.

.vibepro/

.vibepro/ is the repo-local workspace where VibePro stores generated artifacts.

Typical contents include:

.vibepro/
  config.json
  vibepro-manifest.json
  diagnostics/
  graphify/
  pr/
  qa/
  raw/
  stories/

Treat .vibepro/ as evidence and workflow state, not as the application implementation itself.