Author Claim
A claimant receives a one-time challenge. Verification can use a GitHub repository file, registry profile, or DNS TXT proof, but the result is not effective until a trusted reviewer signs the release-bound action.
These controls separate author identity, evidence correction, security decisions, and commercial access. Claims and appeals cannot overwrite scanner evidence; recovery requires two distinct trusted reviewer signatures.
A claimant receives a one-time challenge. Verification can use a GitHub repository file, registry profile, or DNS TXT proof, but the result is not effective until a trusted reviewer signs the release-bound action.
Ownership, classification, security-finding, and takedown appeals bind to the current fixed release, content hash, and scan report. Evidence URLs must use HTTPS and the original record remains auditable.
An accepted appeal is necessary but insufficient. Two different trusted reviewers must approve within the configured validity window; the requester cannot approve their own recovery.
The production design is private and disabled by default. It combines edge rate limiting, an exact daily budget ledger, R2 request/result storage, Queue retries and dead-letter handling, a durable Kill Switch, stale-run alarms, and Sandbox destruction.
11 recorded steps; completed 8/13/2026, 4:30:00 AM with result passed.