Decide: name the first spec reviewers #8

Bar item 1 needs each specification approved by a reviewer on bar/reviewers.toml (added in #2) who did not write it. The list is empty, so no project can be called verified. Two specifications are waiting:

• tar: SPEC.md, Spec.lean, Spec/Defs.lean and the other files its bar.toml lists (tar#6; which set of tar PRs merges is still open in tar#7).
• codec: the same files (codec#1).

Claude, an AI agent, drafted both. Each bar.toml names claude as the spec author.

What a reviewer needs

• The ability to read Lean theorem statements and judge whether each says what the project page claims. The reviewer's checklist is in playbook/verified-bar.md (Verified bar v2: pin reviewed statements and claims, check by machine #2).
• A GitHub account other than ahrazzle. An approval counts only as the reviewer's approving review of the PR that records it in bar.toml, and GitHub does not let a PR's author approve it. The agents open their PRs from ahrazzle.
• Not to have written the specification, or committed to its files.

To decide

1. Who the first reviewers are: one person is enough to start, and two let them review each other's specifications later.
2. Who approves the PR that adds them. Verified bar v2: pin reviewed statements and claims, check by machine #2 gives that to the head of verification, a post that is still empty (Decide: name the director and the head of verification #7).

When decided

A PR to bar/reviewers.toml adds each reviewer's GitHub login and start date. Each reviewer can then review tar and codec.

Current work

The owner chose dynamic reviewers. The proposed checker uses independent repository maintainers rather than a fixed roster.

Awaiting independent review: #25.