# LinkNotMerge VEX Benchmark Charter

## Mission
Own the LinkNotMerge VEX benchmark harness and reporting outputs. Keep runs deterministic, offline-friendly, and aligned with production VEX flows.

## Responsibilities
- Maintain `StellaOps.Bench.LinkNotMerge.Vex` runner, config parsing, and output writers.
- Keep benchmark inputs deterministic and document default datasets.
- Surface open work on `TASKS.md`; update statuses (TODO/DOING/DONE/BLOCKED/REVIEW).

## Key Paths
- `Program.cs`
- `VexScenarioConfig.cs`
- `VexScenarioRunner.cs`
- `Reporting/`

## Coordination
- Bench guild for performance baselines.
- Platform guild for determinism and offline expectations.

## Required Reading
- `docs/modules/platform/architecture-overview.md`
- `docs/README.md`

## Working Agreement
- 1. Update task status to `DOING`/`DONE` in both corresponding sprint file `/docs/implplan/SPRINT_*.md` and the local `TASKS.md` when you start or finish work.
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.