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

auto-review:The entity format, file path, schema version, DCO sign-off, and machine checks are all clean. The structural work is real. What fails is the core acceptance requirement: offer economics, eligibility, and terms must match the first-party source without invented facts. The submitted `vendor_source_url` (segment.com/industry/startups/) redirects to and serves a generic Twilio startup resources page (twilio.com/en-us/solutions/startups). That page covers all Twilio products broadly and does not describe a specific "Segment for Startups" credit program, benefit amount, eligibility thresholds, or application route. The YAML's benefit description ("Segment credits toward the customer data platform"), eligibility statement ("Available to eligible early-stage startups through the Segment for Startups program"), and `access.method: other` cannot be verified against what the source actually contains. The offer economics are too vague to confirm and may be invented or inferred rather than read from a real program page. To pass: locate a first-party Segment or Twilio source that specifically describes the Segment for Startups program with verifiable benefit details (credit value or structure, eligibility criteria, application or access route). Update the YAML fields to reflect exactly what that source states. Redeliver with the corrected `vendor_source_url` and a `entity_url` pointing to the updated branch revision. Rubric blockers: auto_review_verdict: The entity format, file path, schema version, DCO sign-off, and machine checks are all clean. The structural work is real. What fails is the core acceptance requirement: offer economics, eligibility, and terms must match the first-party source without invented facts. The subm...