ADR-030: VibesPro™ Integration Strategy

[!CAUTION] SUPERSEDED: This ADR has been superseded by ADR-030: VibesPro™ Foundation Integration Strategy, which elevates VibesPro™ from an adapter to a foundational substrate.

Status: Superseded
Superseded-By: ADR-030
Version: 1.0
Date: 2025-10-09
Related ADRs: ADR-030
Related PRDs: N/A

Context

SEA™ requires a rapid, repeatable scaffolding workflow for services, APIs, and documentation. “Vibe-coding” (conversational generation) is desirable for velocity, but risks semantic drift and governance bypass if used unchecked.

We have access to VibesPro™, an Nx-based generator platform using Copier templates.

Decision

We will adopt VibesPro™ as the internal generator workbench for SEA™, wrapped securely behind a SEA™ Generation Orchestrator.

• Pattern: VibesPro™ acts as a Driving Adapter. It emits scaffolded code (via Copier) which is then validated and enhanced by SEA™ logic.
• Gates: All generated artifacts must pass:
  1. Semantic Validation (CADSL/SBVR check).
  2. Governance Check (CALM policies).
  3. Knowledge Graph Projection (Metadata emission).
• Runtime: Local-first LLM execution (Ollama) proxied via LiteLLM to allow governed remote fallback.
• Stack: Python-first backend (FastAPI), Type-safe frontend (Next.js), Bidirectional Type Sync (Pydantic -> JSON Schema -> TypeScript).

Rationale

• Velocity: VibesPro™ provides a “batteries-included” developer experience (scaffolding, docs, multi-language support).
• Control: By wrapping it as an adapter, we ensure no code enters the repo without passing semantic and governance checks.
• Alignment: VibesPro™ uses Nx, pnpm, and Just, aligning perfectly with the SEA™ monorepo standard.

Constraints

• MUST wrap VibesPro™ behind SEA™ Generation Orchestrator
• MUST pass all generated artifacts through Semantic Validation, Governance Check, and Knowledge Graph Projection
• MUST use local-first LLM execution via Ollama with LiteLLM proxy
• MUST maintain Copier templates aligned with SEA™ architectural standards
• MUST NOT allow generated code into repo without passing all gates

Quality Attributes

• Consistent project structure and types
• Rapid prototyping capability
• “Demo Ready” scaffolds
• Governed generation workflow
• Local-first with remote fallback

Bounded Contexts Impacted

• Developer Tooling
• SEA™ Generation Orchestrator
• Semantic Core
• Knowledge Graph
• Governance Layer

Consequences

Positive

• Consistent project structure and types
• Rapid prototyping
• “Demo Ready” scaffolds
• Full governance integration

Negative

• Must maintain the integration adapter
• Must ensure Copier templates don’t drift from SEA™ architectural standards

Additional Notes