# Phase 9: Etapes - Discussion Log

> **Audit trail only.** Do not use as input to planning, research, or execution agents.
> Decisions are captured in CONTEXT.md -- this log preserves the alternatives considered.

**Date:** 2026-05-15
**Phase:** 9-Etapes
**Areas discussed:** Etape surface, Task grouping behavior, Ordering model, Assignment workflow

---

## Etape Surface

| Option | Description | Selected |
|--------|-------------|----------|
| Top strip | Compact etape strip above the existing kanban, with create/edit/reorder controls there. Preserves the current task board. | yes |
| Left sidebar | Makes filtering prominent, but reduces kanban space and needs more responsive layout work. | |
| Separate section | Simpler visually, but etapes feel less integrated with daily task work. | |

**User's choice:** Top strip
**Notes:** User wants something functional now; a beautiful UI will come later.

### Top Strip Detail

| Option | Description | Selected |
|--------|-------------|----------|
| Etape chips plus counts | Each etape appears as a compact chip with task count, plus an `Unassigned` chip. | yes |
| Etape cards | Wider blocks with title, description, count, and actions. | |
| Minimal filter only | Just a dropdown or segmented filter, with management elsewhere. | |

**User's choice:** Etape chips plus counts
**Notes:** Include an `Unassigned` chip.

---

## Task Grouping Behavior

| Option | Description | Selected |
|--------|-------------|----------|
| Filter the existing kanban | Selecting an etape shows only tasks in that etape, while columns/status/order stay the same. | yes |
| Group inside each status column | Each kanban column is subdivided by etape. | |
| Etape lanes around kanban | Etapes become the primary layout, with statuses inside each etape. | |

**User's choice:** Filter the existing kanban
**Notes:** Keep the existing kanban model as the primary task view.

---

## Ordering Model

| Option | Description | Selected |
|--------|-------------|----------|
| Keep current status-scoped task order | Etapes have their own order, tasks keep the existing `(tablo, status, position)` behavior. | yes |
| Scope task order by etape and status | Each etape gets independent task ordering per status. | |
| Agent decides | Planner may choose the simplest implementation that preserves visible behavior. | |

**User's choice:** Keep current status-scoped task order
**Notes:** This preserves current drag/drop semantics.

---

## Assignment Workflow

| Option | Description | Selected |
|--------|-------------|----------|
| Task create/edit form | Add an etape selector to the existing task forms. | yes |
| Quick dropdown on task cards | Faster day to day, but more HTMX/card update work. | |
| Both form and quick dropdown | Most complete, but broader than the first functional pass. | |

**User's choice:** Task create/edit form
**Notes:** Quick assignment on task cards is deferred.

---

## Agent Discretion

- Planner may choose exact route names, query names, and HTMX fragment boundaries if the locked product behavior is preserved.

## Deferred Ideas

- Etape progress rollups.
- Etape templates.
- Etape dependencies.
- Quick assignment dropdowns on task cards.
