# EP11 Website Draft

## Goal

Make context feel like a finite working budget, not an invisible background.
The page should teach one thing clearly: context helps the session continue, but
durable decisions live in files.

## Hero

**Claude Code Deep Dive**

One sentence:
Context is a runtime budget that helps you work, but it needs active management
before it turns into noise.

## Page Shape

The page should read like an editorial explainer, not a glossary. The flow is:
start with the problem, show the budget pressure, compare the reset choices,
then land on the durable-file habit.

## Interactive Blocks

### 1. Context Plane Map

Show how context sits in the five-layer model and where it stops being a source
of truth. The visual should make one point only: the live session is not where
long-term policy belongs.

### 2. Context Rot Meter

Let the reader compare:

- fresh context
- noisy context
- compacted context

The point is to show why quality matters more than raw size. A larger working
set can still be worse if it is full of stale branches or repeated outputs.

### 3. Reset Experiment

Show three choices:

- keep going
- compact
- clear and resume

Each choice should explain what gets preserved, what gets dropped, and what the
next step should be. The page should make it obvious that `clear` is not a
panic move. It is a reset when the thread has changed shape.

### 4. Durable-File Handoff Pattern

Show a short before/after story:

- before: the team keeps saying the same thing in chat
- after: the decision is written into a durable file and the session is cleared

This block should make the user feel the difference between "we remember
something" and "the repo now remembers it".

### 5. Comparison Table

Compare these pairs:

- context vs durable files
- compact vs clear
- live notes vs written handoff

Each row should answer:

- what it is
- when it helps
- what it cannot guarantee
- what to do when it gets noisy

## Teaching Rules

- Every block must map back to the five-layer model.
- Every block must include a failure mode.
- Every block must show what belongs in files instead of context.
- Prefer plain language and concrete examples over abstract summary language.
- When the page mentions a reset, show the consequence of not resetting.

## Minimum Viable UX

- calm, editorial pacing
- one strong visual for budget pressure
- mobile-safe text and callout blocks
- legible even without animation
- enough whitespace to make the reset decision feel deliberate

## Official Links

- `memory`
- `settings`
- `hooks`
- `sub-agents`
- `MCP`

## Exit Outcome

The reader should leave knowing when to compact, when to clear, and why
durable decisions belong in files instead of in a stretched-out session.