# Field Map

The Chapter 13 template for supervised computer-use runs. Draw this once, on paper or in a sheet, before the agent touches a single field: source value to each system's field name. One source file, many systems, and the map is the bridge.

## The Map

```
SOURCE VALUE | SYSTEM | FIELD NAME | FORMAT
[The value in your source file] | [Which system receives it] | [The field's name in that system] | [Number, percent, date, yes or no, text]
```

Rules:

- One row per system field, not per record. The map is drawn once; the records flow through it.
- Write the format down. Systems reject numbers in text fields and dates in the wrong shape, and the map is where that stops.
- Draw it before you build the source file. The map tells you what the source file must contain.
- The source file stays out of the chat entirely. Descriptions only.

## A Filled Example (Sam's shape, six systems, names invented)

| SOURCE VALUE | SYSTEM | FIELD NAME | FORMAT |
| --- | --- | --- | --- |
| production total | ERP | Yesterday production total | number, whole units |
| production total | ERP | Open orders count | number, whole units |
| line A total | Scheduling tool | Line A output | number, whole units |
| line B total | Scheduling tool | Line B output | number, whole units |
| production total | Customer portal | Production vs forecast | percent, one decimal |
| production total | Forecasting form | Daily actual | number, whole units |
| verified flag | Compliance tracker | Verified | yes or no |
| open orders | Shared dashboard | Open orders | number, whole units |

A 15-row synthetic version of this map ships in the kit's `data/` folder as `migration-source.csv`. Run the verify pass before touching the next record: row counts match across every system, spot-check three fields per record against the source, and if a count is off by one, stop the run, not the record.