# nested-deps

Demo trace: research-synthesis pipeline with branched dependencies
(`extract_facts` + `extract_quotes` both feed `synthesize`).

## Layout

```
nested-deps/
├─ 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 (format.py), where needed.
    └─ assets/         CSS and similar, 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 artifacts in `fixtures/` (sources, facts, quotes, plots, report;
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).
