# s1 — cold bootstrap → author → validate

**Protected property:** starting from `aura --help` alone (no repo, no docs), a
downstream agent can scaffold a project, author a new strategy over the
discovered op-grammar vocabulary, and drive it to a green backtest — using only
what the binary emits.

## Trail (binary-only)
1. `aura --help` — states what aura is, the two-layer model, and the execution
   model (bias in [-1,+1], held as target position, stop = R).
2. `aura new demo-strat` — scaffolds `Aura.toml`, `blueprints/signal.json`, and a
   machine-written `CLAUDE.md` bootstrap card.
3. `aura graph build --help` — the op-list authoring grammar (one line of meaning
   per op).
4. `aura graph introspect --vocabulary` / `--node <T>` — node types and port
   schemas.
5. Author `ema_cross.oplist.json` (this dir); build it:
   `aura graph build < ema_cross.oplist.json > blueprints/ema_cross.json`
6. Validate green:
   - synthetic: `aura run blueprints/ema_cross.json` → exit 0 (18-cycle synthetic
     stream → 0 trades; all-zero metrics, no note that the stream is tiny).
   - real: `aura run blueprints/ema_cross.json --real EURUSD --from 1577836800000
     --to 1583020800000` → 3944 trades, valid metrics JSON, exit 0.

`ema_cross.blueprint.json` is the built artefact `graph build` emitted.

## Notes
- The harness auto-wraps the bias with `sim-optimal+risk-executor` and reports R
  metrics even though the blueprint emits only a bias — confirming the documented
  execution model without any extra authoring.
- Minor friction: `graph build` has no op to set the blueprint name; it defaults
  to `graph`, and that name leaks into the sweep axis namespace
  (`graph.fast.length`).