# Orch Council Start

## Status

- `completed`

## Owner

- codex

## Started At

- `2026-03-19`

## Goal

- implement the first Milestone 7 slice by adding council input storage and `orch council start`

## Scope

- persist council run metadata plus target input references
- add `orch council start` to create a council run and dispatch three reviewer tasks
- add integration tests for council start dispatch behavior
- update the implementation roadmap and archive this workstream when complete

## Checklist

- [x] inspect council docs, schema, and existing orch dispatch primitives
- [x] implement council storage and `orch council start`
- [x] add integration coverage for council start
- [x] run `go test ./...`
- [x] update `docs/implementation-roadmap.md`
- [x] archive this roadmap with a completion summary

## Files

- `docs/roadmaps/archive/orch-council-start.md`
- `docs/implementation-roadmap.md`
- `internal/db/schema/*.sql`
- `internal/store/council.go`
- `internal/cli/orch/root.go`
- `internal/cli/orch/council*.go`
- `internal/cli/orch/integration_test.go`

## Decisions

- treat `orch council start` as creating a dedicated run id rather than attaching to a pre-existing ordinary run
- persist target prompt/file/repo/task references in a separate council input table instead of overloading the existing `runs` table

## Blockers

- none

## Next Step

- continue Milestone 7 with `orch council wait`, then add tally and report on top of the persisted reviewer data

## Completion Summary

- council input references are now persisted separately from council run metadata
- `orch council start` creates a dedicated council run, dispatches the three fixed reviewer roles, and records reviewer assignment rows for downstream wait/tally/report steps
- integration tests now cover council start dispatch behavior and stored council metadata