# Anand's Four-Moves Capstone &mdash; Schema

Flat CSV in `anand-headcount-fourmoves.csv`. One row per move-action pair (each move has one or more actions).

## Columns

| Column | Type | Description |
| --- | --- | --- |
| `move_id` | integer | Move id (1..4) in canonical order. |
| `move_name` | text | One of `Provenance`, `Fairness`, `Decision-Boundary`, `Disclosure`. |
| `purpose` | text (quoted) | One-phrase purpose of the move. |
| `action_index` | integer | Action index (1..N) within the move. |
| `action_text` | text (quoted) | The specific action Anand took. |
| `surfaced_issue` | text (quoted) | The substantive issue the move surfaced (empty for moves that produced no issue). |

## Row inventory

- Provenance: 2 actions.
- Fairness: 3 actions.
- Decision-Boundary: 3 actions.
- Disclosure: 2 actions.

Total: 10 rows.

## Deliberate design choices

Actions are stored one-per-row (rather than as a delimited list on a single move row) so the CSV can be pivoted, filtered, or joined against a checklist template. This also lets an instructor building a workshop enumerate expected actions per move without parsing embedded delimiters.

`surfaced_issue` is populated on every row of a move that surfaced an issue (so the join is visible on any action row within that move); moves that produced no substantive issue leave the field empty.

## License

Released for teaching use alongside *The Defensible Decision*. Use freely.
