pipeline-bootstraplisted

# Skill: Pipeline Bootstrap > **Load trigger:** `"load pipeline-bootstrap skill"` > **Agent:** Used by pipe-agent > **DORA:** Cap 4 + Cap 6 > **Token cost:** Medium ## Purpose Step-by-step guide for connecting a uFawkesAI project to uFawkesPipe (paruff/uFawkesPipe) and the fawkes platform delivery infrastructure. ## Prerequisites Before starting, confirm these are in place: - [ ] `AGENTS.md` populated (run onboarding agent if not) - [ ] `ci-quality.yml` passing on main branch - [ ] `OTEL_SERVICE_NAME` decided (format: `[org]-[service]-[env]`, e.g. `fawkes-payments-prod`) - [ ] ArgoCD application name decided (same as service name by convention) ## Step 1 — Create Pipeline Contract Document Create `docs/PIPELINE_CONTRACT.md`: ```markdown # Pipeline Contract — [Service Name] ## CI Gates (uFawkesAI) | Gate | Tool | Threshold | | ------------ | -------- | ------------- | | PR size | git diff | 400 lines max | | Lint | [tool] | 0 errors | | Typecheck | [tool] | 0 errors | | Coverage | [tool] | 80% minimum | | Architecture | [tool] | 0 violations | ## Delivery Config (uFawkesPipe) - ArgoCD app name: `[service-name]` - Target namespace: `[namespace]` - Image registry: `ghcr.io/[org]/[service-name]` - Deploy on: merge to `main` ## Observability - OTEL service name: `[OTEL_SERVICE_NAME]` - OTLP endpoint: from env `OTEL_EXPORTER_OTLP_ENDPOINT` - Grafana dashboard: `docs/obs/[service-name]-dashboard.json` ## Rollba