# Hatchways Agentic Mode Objection Packet

Answer the likely first objections from Hatchways product, engineering, security, reviewer-ops, and partnerships owners before a limited technical pilot.

## Objections

### Product: This sounds like a new coding-test platform, not a Hatchways add-on.

The verified path is an evidence layer around a Hatchways-style GitHub assessment. The repo task, public tests, hidden grading, and human review stay intact.

Proof: https://hottea.ai/hatchways/integration.md

### Engineering: A GitHub App does not exist yet.

Correct. The pilot path uses the verified GitHub Actions fallback. The real GitHub App remains gated on account-level app creation and GITHUB_APP_INSTALL_URL configuration.

Proof: https://hottea.ai/github-action.yml

### Reviewer Ops: AI-agent transcripts may add more noise than signal.

The sample packet separates procedural prompts from substantive candidate reasoning and gives reviewers a 1-10 aid score, hidden-test summary, process analysis, and follow-up questions.

Proof: https://hottea.ai/sample-report.md

### Security: This is not enterprise-procurement ready.

Correct. The security packet names current limits explicitly: no SOC 2, DPA, SSO, retention SLA, or completed enterprise review. The proposal is a limited technical pilot, not an enterprise rollout claim.

Proof: https://hottea.ai/hatchways/security.md

### Partnerships: There is no official Hatchways partnership.

Correct. The proof packet is buyer-specific positioning and technical evidence only. It does not claim partnership, endorsement, procurement approval, or production customer rollout.

Proof: https://hottea.ai/hatchways/decision.md

### Candidate Experience: This could feel like proctoring.

The Hatchways path avoids locked browsers and screen recording. It standardizes the developer VM, Claude/Codex access, task packet, test evidence, and reviewer packet.

Proof: https://hottea.ai/hatchways/pilot.md

## Pilot Reply

- If the objections above are acceptable, the next useful step is a technical pilot on one internal Hatchways-style repo assessment.
- If the GitHub App must exist first, the current blocker is account-level app creation plus GITHUB_APP_INSTALL_URL deployment configuration.
- If procurement must clear first, the current packet should stay a technical proof asset and not be positioned as enterprise-ready.

## Not Claimed

- No official Hatchways partnership.
- No real GitHub App before GITHUB_APP_INSTALL_URL is configured.
- No enterprise procurement readiness.
- No perfect anti-cheat or outside-AI prevention.
- No automated hiring decision.

## Proof URLs

- Objection JSON: https://hottea.ai/hatchways/objections.json
- Decision brief: https://hottea.ai/hatchways/decision.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- GitHub Action adapter: https://hottea.ai/github-action.yml
- Security packet: https://hottea.ai/hatchways/security.md
- Pilot kit: https://hottea.ai/hatchways/pilot.md
- Sample reviewer packet: https://hottea.ai/sample-report.md