Submatter/plans/Plan-automation-foundation/Epic-pipeline-convoy-scaffolding/Epic-pipeline-convoy-scaffolding.md
Randall Stillwell e256380671 plan(automation): add mission-control foundation backlog and model-routing ADR
Documents the automation foundation plan (nine epics, Epic 1 taskified) and
the accepted model-provider registry contract. Updates .env.example for backlog
import workspace id and local/cloud AI provider env guidance.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-07-07 13:55:03 -05:00

46 lines
1.3 KiB
Markdown

---
kind: epic
slug: pipeline-convoy-scaffolding
title: Pipeline convoy scaffolding — .convoys/ and metrics in tasks repo
plan_slug: automation-foundation
status: draft
priority: P1
tenant_id: global
cursor_epic_id: null
updated_at: "2026-07-03"
---
# Epic objective
Install L3 convoy infrastructure in the `tasks` repo so agent-pipeline dogfooding works: `.convoys/README.md`, `scripts/log-convoy-event.sh`, `.cursor/rules/convoy-planning.mdc`, `.gitignore` entry for `.convoys/.metrics.jsonl`.
Can run **in parallel** with Epic 1 (model provider registry).
## In scope / out of scope
**In scope**
- Copy/adapt from `agent-pipeline` L3 `_common` templates (manifest-aware paths).
- Document kickoff ritual in `.convoys/README.md`.
**Out of scope**
- Convoy lifecycle MCP (Epic 4).
- Creating convoy files for other consumer repos.
## Dependencies
- None (bootstrap from agent-pipeline templates).
## Blocks
- Epic 4 (convoy lifecycle MCP) — operators need a place to write convoy files first.
## Acceptance criteria
- [ ] `bash scripts/log-convoy-event.sh role=role-conductor convoy=test` appends valid JSONL.
- [ ] `role-conductor` can write `.convoys/<slug>.md` without conflicting rules.
## Tasks
_To be decomposed by architect when epic graduates to `ready`._