> ## Documentation Index
> Fetch the complete documentation index at: https://podium.do/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reference issue and session states

> Distinguish issue stages, session phases, attention states, and completion.

Issue stages track the delivery record. Session phases track one running process. Read both before deciding whether work is ready.

## Issue stages

The issue stage records where the overall deliverable sits:

| Stage | Meaning |
| - | - |
| `proposed` | Newly discovered top-level work awaiting triage |
| `backlog` | Accepted work that has not started |
| `planning` | The operator or agent is preparing scope, placement, or approach |
| `in_progress` | An assignee is actively delivering the issue |
| `review` | The deliverable and evidence await a decision |
| `shipping` | A system-managed transient delivery stage |
| `done` | The issue is closed; dedicated close commands also record a reason |

The normal board omits the transient shipping stage. Experimental shipping behavior should not define a baseline workflow.

## Common session states

The session state records what one harness process needs now:

| State | Meaning | Operator action |
| - | - | - |
| Working | The harness is processing a turn | Wait or inspect status |
| Idle | The harness has no active turn | Review output or send work |
| Needs input | The harness asked a question | Answer in the session |
| Permission needed | A command awaits approval | Check the exact action and target |
| Retryable error | The run can continue after intervention | Fix the cause, then continue |
| Hibernated | The process ended and can be resumed later | Resume it or close its issue |

## Close reasons

`podium issue close` accepts `done`, `cancelled`, `duplicate`, or `superseded`. Use the reason that explains why no work remains.

## Dependency meanings

Podium defines behavior for `blocks`, `related`, `parent-child`, `discovered-from`, `tracks`, `supersedes`, `caused-by`, and `validates`. The dependency store accepts other nonempty type names, but custom types have no documented workflow behavior. Use `blocks` only when the dependent issue cannot finish first. Manage `parent-child` through issue creation or `podium issue reparent`; `podium issue dep-add` rejects that type.