Submatter/plans/Plan-automation-foundation/Epic-pipeline-convoy-scaffolding/Epic-pipeline-convoy-scaffolding.md

53 lines
1.5 KiB
Markdown
Raw Permalink Normal View History

---
kind: epic
slug: pipeline-convoy-scaffolding
title: Pipeline convoy scaffolding — .convoys/ and metrics in tasks repo
plan_slug: automation-foundation
status: done
priority: P1
tenant_id: global
cursor_epic_id: null
updated_at: "2026-07-07"
agent_prompt: |
Epic: pipeline convoy scaffolding. Install .convoys/, log-convoy-event.sh,
convoy-planning.mdc. No MCP or orchestrator code. claim_task before work.
---
# 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
- [x] `bash scripts/log-convoy-event.sh role=role-conductor convoy=test` appends valid JSONL.
- [x] `role-conductor` can write `.convoys/<slug>.md` without conflicting rules.
## Tasks
| Task | Link |
|------|------|
| log-convoy-event script | `./Task-log-convoy-event-script.md` |
| README + planning rule | `./Task-convoy-readme-and-planning-rule.md` |