# Brainstorm

A thinking partner for a large-scale software change. The session's product is the repository's living documentation: the conversation helps the user think correctly, the working surface reads well at any pause, and the stop pipeline harvests the session so completely that its folder is redundant. The folder then moves to history, and the user deletes or commits it.

The design, its reasons and its evidence live in `docs/skills/brainstorm/` in the etna repo.

## One capability, two seats

| Seat | Component | Owns |
| --- | --- | --- |
| Conversation (main loop) | `SKILL.md`, the facilitator | the dialogue, the basis gate, the moves, the per-turn capture into `ops/capture.md`, the sync-log dispatch lines |
| Paper (dispatched agent) | the `brainstorm` agent, the twin, pinned to a strong tier | every working-surface file: distillation, the whole-thesis recompose, the semantic audits, the harvest |
| Integrity (script) | `scripts/detector.mjs` | mechanical checks with stable rule ids, blocking the manifest and the move while they fail |
| Quality (authoring time) | `evals/`, never shipped | activation and behaviour cases, session-replay scenarios, the two-agent audit |

## Files

| Path | Holds |
| --- | --- |
| `SKILL.md` | the facilitator hub: re-anchor, commands, write ownership, capture, moves, dispatch, questions, promises |
| `references/entry.md` | `/brainstorm start`: lookup, basis gate, bootstrap, intake, aspect map, orientation |
| `references/doctrine.md` | the epistemics of the surface, shared by both seats, with the capture-and-converge field lessons |
| `references/session-schema.md` | the on-disk contract the detector parses, and its rule table |
| `references/harvest.md` | `/brainstorm stop`: the pipeline, the routing map, the apply field lessons |
| `scripts/detector.mjs` | the rule registry: `node detector.mjs <folder> [--gate=session\|manifest\|move] [--json]` |
| `scripts/fixtures/` | contrastive fixtures and their runner, `node scripts/fixtures/run-fixtures.mjs` |
| `evals/` | `activation.json`, `evals.json`, the replay driver and its scenarios |