Hack Day: TraderX Evolution Experiments (Graph-Aware)

## Goal
Create and track a portfolio of TraderX hack-day experiments that are explicitly graph-aware:
- candidate canonical follow-on states, or
- durable optional/alternative branches worth keeping alive.

Each sub-issue should clarify state lineage impact and promotion criteria.

## Classification Model
For each experiment, record:
- Graph intent: canonical candidate | optional branch | exploratory branch
- Jump-off state(s): baseline state(s) to branch from
- Expected outcome: new state proposal vs bounded PoC
- Decision gate: evidence required to promote/park

## State Graph Context
Current implemented lineage includes:
001 -> 002 -> 003 -> 004(C0) -> 005 -> 006 -> 007(C1) -> 008 -> 009(C2) -> 010 -> 011 -> 012(C3)
plus adjacent 013 (optional) and 014 (planned interop extension).

## Sub-Issues
- [ ] #370
- [ ] #371
- [ ] #372
- [ ] #373
- [ ] #374
- [ ] #375
- [ ] #376
- [ ] #377
- [ ] #378
- [ ] #379
- [ ] #380
- [ ] #381
- [ ] #382
- [ ] #383
- [ ] #384
- [ ] #385
- [ ] #386

## Done Criteria
- Parent issue links every sub-issue.
- Each sub-issue includes jump-off states and graph intent.
- Each sub-issue has acceptance criteria and explicit promotion/park decision gate.

Start with this parent issue and review sub-issues #370–#386 alongside the listed state lineage. Check that every sub-issue records its jump-off states, graph intent, expected outcome, acceptance criteria, and promotion/park decision gate, then verify the parent links all of them.

Written by the indexing model from the issue text.