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

auto-review:PR #1236 adds exactly one Entity YAML at entities/pu/pulseadt.yaml (shard and filename match slug). The offer is startup-specific (≤36 months, <50 employees, <$500k ARR, tech product), currently active, and materially useful: $250 API credit on $100 spend within 90 days, followed by an ongoing 30% discount, with a public Typeform access route. Two first-party sources from getpulseadt.com are bound via source_ids. All structured fields (consideration, benefits with correct minor_units and basis_points, eligibility criteria, lifecycle, access, roles) are complete and internally consistent. The file is data-only with no code or unrelated content. Machine checks 3/3 passed. CI/DCO pass is not machine-confirmed and must be verified by the human reviewer directly on the PR before acceptance is finalized.

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

auto-review:PR #1232 adds one new Entity YAML at entities/pa/paypercut.yaml, correctly sharded and named. The offer is startup-specific (early-stage European companies, application-gated), materially useful (fee waivers on up to EUR 10,000 transaction volume per month for six months, reduced pricing through month 24, EUR 10,000 aggregate cap), and sourced from two first-party vendor URLs. The economics are specific and internally consistent: monthly allowances stated as non-rollover, two distinct pricing phases with exact month ranges, dual eligibility path for bootstrapped and VC-backed startups. Frantic-side machine checks 3/3 passed. No dealbreakers: artifact is real, form is correct, no fabricated evidence, no credentials, no steering.

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

auto-review:The PR URL resolves and the claimant stars the repo, but the artifact fetcher returned only a GitHub HTML reference page with no file contents or diff. Every substantive acceptance bullet — the entity YAML path and contents, offer validity, field completeness, startup-specificity, first-party source, entity uniqueness, CI/DCO pass status — lives inside the PR diff and none of it was retrievable. A live PR URL proves the PR exists; it does not prove the offer is genuine or complete. Redeliver with a raw file URL pointing directly to the entity YAML (e.g., https://raw.githubusercontent.com/sourcey/startup-credits/refs/pull/1234/head/entities/{shard}/{slug}.yaml) so the content is fetchable, and confirm CI passes on the current PR head before redelivering. Rubric blockers: auto_review_verdict: The PR URL resolves and the claimant stars the repo, but the artifact fetcher returned only a GitHub HTML reference page with no file contents or diff. Every substantive acceptance bullet — the entity YAML path and contents, offer validity, field completeness, startup-specific...