# dream-analysis

Demo trace: takes a dream description, gathers personal context, produces a
three-framework symbolic analysis (Jungian, Freudian, Eastern), renders an
imagery illustration, and composes a report.

## Layout

```
dream-analysis/
├─ trace.json         The static plan: step DAG, asset contracts.
├─ README.md           ← you are here
└─ steps/<step_id>/    One folder per step.
    ├─ STEP.md         Contract: what reads what, writes what; impl hints.
    ├─ scripts/        Reference implementations (analyze.py, render.py).
    └─ assets/         Prompt templates and CSS, where a step needs them.
```

The example ships a `build.sh` and a `fixtures/` directory one level up (next
to `template/`). `build.sh` replays the full pipeline through the CLI, using
the pre-baked PNGs/PDFs in `fixtures/` (regenerated by `fixtures/generate.R`)
so demo builds stay fast. Running it writes `runs/<run_id>/` with state,
replies, and per-step outputs.

For the canonical "mature trace folder" reference, see
[`../iris-analysis/README.md`](../iris-analysis/README.md).
