# EP06 Website Draft

## Goal

Show how lifecycle boundaries turn into enforceable acceptance gates.

## Hero

**Stop is not an end button. It is a checkpoint boundary.**

## Page Structure

1. lifecycle gate overview
2. stop / subagent stop / precompact comparison
3. checkpoint flow
4. acceptance failure modes
5. minimal handoff template
6. official links

## Interactive Blocks

### 1. Gate Timeline

Let the reader step through a session and see what should be written out before each boundary.

### 2. Boundary Comparison

Compare:

- `Stop`
- `SubagentStop`
- `PreCompact`

Each row should answer:

- when it fires
- what should happen
- what must be saved
- what happens if it is skipped

### 3. Acceptance Simulator

Show a simple state machine with these states:

- in progress
- needs checkpoint
- ready to compact
- blocked
- complete

## Minimum Viable UX

- calm, audit-like layout
- strong phase labels
- no decorative clutter
- readable on mobile as a checklist, not a dashboard

## Teaching Rules

- Every gate must point back to the context plane or automation plane.
- Every failure mode must show the cost of skipping the checkpoint.
- Every example must include an artifact path.

## Official Links

- hooks
- context window and compaction
- memory

## Exit Outcome

The reader should know when to force a checkpoint and why lifecycle boundaries are the safest place to do it.