machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:PR is live, correctly formed, and delivered in the exact required form (pr_url to a public pull request on sourcey/startup-credits). Machine floor is clean: URL admitted as public surface, @silectio stars the repo (confirming genuine engagement with the project), HTTP 200 confirmed. The fetched artifact is a GitHub reference page without raw diff contents, which is the expected result for a PR URL — the fetcher does not surface diff data from GitHub PR pages, so content bullets (offer validity, CI pass, DCO, entity uniqueness) require human review of the actual diff. No fabrication signals, no wrong-form delivery, no deterministic blockers. Plausible work from a real GitHub identity. Human gate should verify: (1) exactly one new entity YAML at the correct shard path, (2) CI and Candidate Verifier pass on current head with DCO sign-off, (3) offer is startup-specific, currently available, and matches a first-party English-language source, (4) no duplicate entity or open competing PR.

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:The `sourcey/admission` check on PR head `823d176ff991c2886de0fa395d0446db1a417301` concluded failure with "needs revision: claim_unsupported." That check is Sourcey's authoritative content verifier for this repository, and the bounty requires it to pass. The changed-closure CI and DCO both passed, the YAML is well-formed, and the visible portion of the admission report shows only `supported` bindings — but the check itself failed, meaning a claim somewhere in the full report (the artifact was truncated at 32000 bytes) came back unsupported. Find which field Sourcey flagged, correct the YAML, push a new head, and redeliver once the admission check passes.