Vrida Documentation

Project orientation and documentation index — the entry point for every session with CC.

The AI Capability Plane: governance controls, capabilities, authority levels, and rules that apply across every module.

System-wide technical decisions and conventions that every module must follow.

Authoritative schema definitions and the schema-design discipline every module follows.

Architecture Decision Records — the durable "why" behind non-obvious design choices.

Per-module documentation: v1 reference specs (superseded), v2 module specs, module index, build status, and cross-module contracts.

The repeatable module pipeline, its two gates (Design-lock and Ship), and the runbooks every module flows through.

Market research, the gaps registry, and the explicit product scope for v2.

Brand reference for UI builders — colours, typography, logo usage, and naming conventions.

Navigation, app-shell, and per-module page specs (route, data, service calls, actions, manual/AI behavior).

Full docs from the Sprig-era project — retained as reference. Not confirmed v2 design.

All open items across the build — dependencies, deferred FKs/APIs/integrations, and issues found. Checked at every module lock gate.