# Git worktree census — 2026-10-30

Ledger-lane extraction artifact: a point-in-time census of the `troupe-standup`
worktree, re-derived from live `git` (the repository is the single source of
truth). No value is invented.

## Files

| File | Purpose |
| --- | --- |
| `git-worktree-census-2026-10-30.json` | Machine-readable census (author rows, top-modified files, branch/remote state). |
| `git-worktree-census-2026-10-30.csv` | Machine-readable table (rank, path, commits) of the most-changed files. |
| `git-worktree-census-2026-10-30.md` | Human-readable table plus the key scalars. |
| `extract_git_worktree_census.py` | Reproducer (Python stdlib) that re-derives all of the above from `git`. |
| `CHECK-git-worktree-census-2026-10-30` | Re-derives the census from live `git` and compares it field-for-field against the JSON. Exit 0 only on exact match. |

## Data captured (as of `2026-10-30`)

- `branch`: main; `branch_head`: d2594c5
- `commit_count`: 2207 (re-derived at time of extract)
- `tracked_file_count`: 4279
- `total_unique_emails`: 38
- `ahead_by_origin_main`: 22 | `behind_by_origin_main`: 1
- `author_census`: 48 rows (name/email count/first/last/collisions)
- `top_modified_files`: 60 paths with commit frequency

## Reproducing

```sh
python3 wizard-work/ledger/extract_git_worktree_census.py
./wizard-work/ledger/CHECK-git-worktree-census-2026-10-30
```

The CHECK exits 0 only if the JSON matches a fresh derivation from live git.

## Notes

- This is a point-in-time snapshot of a live, actively committed worktree. The
  scalars (`commit_count`, `ahead`, `remote_heads`, …) move with new commits and
  are not stable across ticks.
- Run from a checkout with `origin/main` configured (the extract uses `origin/main` for ahead/behind).