# tipoc-tv Testcase Agent Entry

## Scope

This directory contains reusable benchmark scenario definitions and report
field contracts. It is not runtime evidence and it is not a pass certificate.
Scenario files may reference concrete dataset sizes, machine classes, or
evidence sample ids because those values are testcase parameters and measured
evidence anchors, not product package names or Go runtime abstractions.

## Required Context

Before changing files in this directory, read:

1. `../AGENTS.md`
2. `../docs/DESIGN-CAPSULE.md`
3. `../docs/CRITICAL-PATH-MAP.md`

## Rules

1. Keep canonical TPC-E securities workload, restore-isolated sweep, continuous
   ramp, and hotspot stress scenarios separate.
2. Do not mark a pressure report as a formal four-stage pass. A pass requires
   fresh attempt-root guard evidence.
3. Do not change scenario ids after reports or premium runs reference them.
4. Hotspot scenarios must use workload profile parameters. Do not express
   hotspots as SQL literals.
5. Premium or larger datasets may reuse the same scenario ids only by binding
   a new target size, topology, object store, BR baseline, and concurrency
   gradient in a separate task card.

## Verification

For docs/data-only testcase changes, run at minimum:

```bash
python3 tools/critical_path_guard.py
git diff --check
```

Run `python3 tools/go_lint_guard.py` as well when the surrounding change set
touches Go files or when this directory is part of a broader product commit.