# EP05 Website Draft

## Goal

Show hooks as a lifecycle map, not just as a list of shell scripts.

## Hero

**Soft policy becomes real when the lifecycle enforces it.**

## Page Structure

1. lifecycle timeline
2. hook guardrail demo
3. stop vs compact gate
4. deterministic vs subjective panel
5. official-doc links

## Interactive Blocks

### 1. Lifecycle Timeline

Show the key moments:

- session start
- pre-tool use
- post-tool use
- stop
- pre-compact

### 2. Guardrail Demo

Let the reader toggle a few actions and see whether a hook should:

- allow
- block
- log
- checkpoint

### 3. Stop vs Compact Gate

Compare:

- finish and validate
- checkpoint before compaction
- fail fast on unsafe actions

## Minimum Viable UX

- architecture-lab tone, not console tool spam
- clear lifecycle steps
- short explanatory blocks
- mobile-safe flow with stacked stages

## Teaching Rules

- Hooks must be presented as deterministic, not magical.
- Every example must say what stage it runs at.
- Distinguish a block from a review comment.

## Official Links

- `research/topic-notes/hooks.md`
- `research/official-map.md`
- `architecture/patterns/hooks-guardrails.md`
- `architecture/context-governance.md`

## Exit Outcome

The reader should know where hooks fit in the lifecycle, what they can enforce, and why they are not a substitute for judgment.