Operations (Index)
Canonical environment, deployment, CI/CD, and operational runbooks for ConversionIQ.
Purpose
Section titled “Purpose”If the product must be rebuilt from scratch, engineering still needs to know how to run it, validate it, and recover its toolchain. This section owns those operational contracts.
Use docs/ops/** for:
- environment variables and secrets handling
- deployment topology and environments
- CI/CD expectations and validation gates
- local development prerequisites
- recovery and incident runbooks
Canonical contract rules
Section titled “Canonical contract rules”- Machine-specific setup may live outside the repo, but the project-critical configuration required to recreate it must be documented here.
- If CI, deployment, or environment behavior changes, update
docs/ops/**in the same change.
Planned ops areas
Section titled “Planned ops areas”- environment and secrets matrix
- local development setup
- CI/CD and validation gates
- release and rollback procedures
- MCP and editor/tooling machine setup where project-critical
- private documentation site deployment and access control
Current docs
Section titled “Current docs”The MVP status page is a generated snapshot intended for stakeholder reviews. Refresh it from the docs repo with npm run refresh-status when both the docs and app repos are available locally.