Skip to content

Pipeline integrity: epic integration review, git isolation, spec-aware context & escalation resolve #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lycha merged 10 commits into from
Jul 24, 2026
Merged

Pipeline integrity: epic integration review, git isolation, spec-aware context & escalation resolve #3

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
cc404c9
fix(engineer): enforce the task's scope boundary in IMPLEMENTATION
lycha Jul 22, 2026
17734de
fix(implementation): stage the repo before the agentic diff check
lycha Jul 22, 2026
fcd5ee8
feat(git): per-task commits so each task's review sees only its own diff
lycha Jul 22, 2026
dd32db3
docs: STAN-1 postmortem + pipeline integrity tech spec
lycha Jul 24, 2026
b1964c7
feat(rubrics): Phase 1 — spec traceability + integration-seam checks …
lycha Jul 24, 2026
8bda398
feat(context): Phase 2 — inject epic PRD/tech-spec into child-task co…
lycha Jul 24, 2026
d856fa9
feat(escalation): Phase 2 — resolve escalations via an editable escal…
lycha Jul 24, 2026
f9186d2
feat(git): Phase 3 — per-epic branch isolation (WI-1)
lycha Jul 24, 2026
e3e4bf3
feat(pipeline): Phase 4 — epic INTEGRATION_REVIEW stage over the asse…
lycha Jul 24, 2026
edf8cfa
docs: mark pipeline-integrity spec implemented; README for INTEGRATIO…
lycha Jul 24, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co

AEOS is a CLI that drives tickets through LLM-agent pipelines. A ticket is an **epic** or a **task**, and each has its own column sequence:

- **epic** — `BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN → DOD_GATE → DONE`
- **epic** — `BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN → INTEGRATION_REVIEW → DOD_GATE → DONE`
- **task** — `BACKLOG → IMPLEMENTATION → CODE_REVIEW → QA → DONE`

Each column has a worker agent, a reviewer agent with rubrics, and a human approval gate. An epic decomposes into child tasks and cannot leave `TASK_BREAKDOWN` until every child is `DONE`. `aeos orchestrator run <epicId>` drives the whole thing autonomously. See `README.md` for the full command surface, state machine table, and executor matrix — that document is current; prefer it over re-deriving behaviour from code.
Expand Down
31 changes: 19 additions & 12 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -60,14 +60,15 @@ aeos ticket dod-approve MYPRJ-1
A ticket is either an **epic** or a **task**, and each follows its own pipeline.

```
EPIC BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN ─────────→ DOD_GATE → DONE
PM Agent Architect Architect Human
↓ ↓ ↓ ▲
PRD Tech Spec tasks.md │
↓ ↓ ↓ │
Reviewer Reviewer Reviewer │
│ │
fans out into child tasks all children DONE
EPIC BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN ──→ INTEGRATION_REVIEW → DOD_GATE → DONE
PM Agent Architect Architect Integration Reviewer Human
↓ ↓ ↓ ↓ ▲
PRD Tech Spec tasks.md integration-review.md │
↓ ↓ ↓ ↓ │
Reviewer Reviewer Reviewer Reviewer │
│ (whole-feature diff │
fans out into child tasks vs PRD/tech spec) │
all children DONE ────────────┘
▼ │
TASK BACKLOG → IMPLEMENTATION → CODE_REVIEW → QA → DONE ───────────────────┘
Engineer Engineer QA
Expand All @@ -79,7 +80,9 @@ TASK BACKLOG → IMPLEMENTATION → CODE_REVIEW → QA → DONE ────

An epic is scoped, specced, and decomposed — it never implements anything itself.
Its child tasks do that, and the epic cannot leave `TASK_BREAKDOWN` until every
child reaches `DONE`.
child reaches `DONE`. It then runs `INTEGRATION_REVIEW`, which reviews the whole
assembled feature (the epic branch's `base..HEAD` diff) against the PRD and tech
spec — the check per-task review cannot make — before the human `DOD_GATE`.

Each column follows the same cycle:

Expand Down Expand Up @@ -124,7 +127,7 @@ The forward order depends on the ticket's kind:

| Kind | Pipeline |
| ------ | -------------------------------------------------------------------------- |
| `EPIC` | `BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN → DOD_GATE → DONE` |
| `EPIC` | `BACKLOG → PRODUCT_SCOPING → TECH_SPEC → TASK_BREAKDOWN → INTEGRATION_REVIEW → DOD_GATE → DONE` |
| `TASK` | `BACKLOG → IMPLEMENTATION → CODE_REVIEW → QA → DONE` |

`aeos ticket approve` uses the kind to pick the next column, so a task never
Expand Down Expand Up @@ -181,6 +184,7 @@ Every non-terminal column allows the same set:
| `IMPLEMENTATION` | task | all eight |
| `CODE_REVIEW` | task | all eight |
| `QA` | task | all eight |
| `INTEGRATION_REVIEW` | epic | all eight |
| `DOD_GATE` | epic | all eight |
| `DONE` | both | `null` only |

Expand Down Expand Up @@ -264,7 +268,8 @@ Notes:
| `aeos ticket approve <id>` | Advance a SIGNED_OFF ticket to the next column |
| `aeos ticket sign-off <id>` | Manual override — set a ticket sub-state to SIGNED_OFF |
| `aeos ticket move <id> <status>` | Human override — move a ticket directly to any workflow status |
| `aeos ticket answer <id>` | Unblock a ticket after answering pre-flight questions |
| `aeos ticket answer <id>` | Unblock a `BLOCKED` ticket after answering pre-flight questions |
| `aeos ticket resolve <id>` | Resume an `ESCALATED` ticket after writing a decision in its `escalation.md` |
| `aeos ticket dod-approve <id>` | Final human gate — mark ticket as DONE _(not yet implemented)_ |
| `aeos dashboard` | Cross-project Kanban summary _(not yet implemented)_ |
| `aeos costs [--project] [--ticket]` | LLM spend report _(not yet implemented)_ |
Expand Down Expand Up @@ -293,7 +298,9 @@ aeos ticket approve AEOS-2 && aeos ticket run AEOS-2 # implementation
...

# 5. Only once every task is DONE can the epic advance
aeos ticket approve AEOS-1 # → DOD_GATE
aeos ticket approve AEOS-1 # → INTEGRATION_REVIEW
aeos ticket run AEOS-1 # reviews the whole feature vs PRD/spec
aeos ticket approve AEOS-1 # → DOD_GATE (after human reads the verdict)
```

Nesting is one level deep: tasks hang off epics, and a task cannot itself have
Expand Down
Loading
Loading