Skip to content

Instantly share code, notes, and snippets.

@danialhasan
Created October 31, 2025 19:20
Show Gist options
  • Select an option

  • Save danialhasan/d1faecb824cc69fd6bfe2b79748681d0 to your computer and use it in GitHub Desktop.

Select an option

Save danialhasan/d1faecb824cc69fd6bfe2b79748681d0 to your computer and use it in GitHub Desktop.
CarGO Review: coverage-checklist.md (2025-10-31)

Discovery Call Coverage Checklist (Gate for Dataset Expansion)

  • Rapport/Consent
    • Opens with explicit consent and fallback to reschedule
    • Includes at least one human repair/clarification (e.g., "sorry—go ahead")
  • Facts Coverage (must be stated or implied)
    • 24/7/365 operations; all‑weather/holiday reliability
    • Zero‑tolerance lateness with explicit consequence (one strike)
    • No substitutions/no riders policy
    • HIPAA/privacy; specimen photos/counts/staff names via app
    • Daily driver app check‑ins; follow live resequencing; responsive comms
    • Onboarding + two‑week extended interview; uniforms/supplies provided
    • E‑ZPass expectation for bridges/tunnels
    • Compensation basics: per‑assignment, multi‑stop bundles, deadhead handling mentioned at high level
    • Availability windows expressed clearly (days + times)
  • Geography Anchors
    • At least two named anchors (bridges/tunnels/merges/facilities)
    • One micro‑anchor with reason (e.g., "LIE/Grand Central merge eastbound backs up at…")
  • Naturalness Targets
    • Candidate word count ≥ interviewer word count
    • Avg words per turn ~15–60; avoid rigid labels (no SCAR headers)
    • Prose, not bullet lists; warm close that invites questions
  • Close
    • Explicit invitation for candidate questions
    • Next‑steps preview without over‑promising

This checklist must be satisfied for each synthetic before expansion or PR sign‑off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment