# Hatchways Reply Kit

Convert a Hatchways reply into the next bounded action without overstating partnership, procurement readiness, or GitHub App status.

Boundary: One technical pilot conversation, one synthetic or internal repo assessment, GitHub Actions fallback only, and no customer or production candidate traffic.

## Response Paths

### They ask for a quick walkthrough.

- Reply goal: Send the proof index, demo script, and kickoff checklist; propose a seven-minute async review before any meeting.
- Proof: https://hottea.ai/hatchways/index.md

### They ask how it fits Hatchways' GitHub workflow.

- Reply goal: Point to the GitHub Actions fallback and integration guide; state that the real GitHub App is not configured yet.
- Proof: https://hottea.ai/hatchways/integration.md

### They ask security or procurement questions.

- Reply goal: Send the security packet and keep the answer scoped to a technical pilot, not enterprise procurement.
- Proof: https://hottea.ai/hatchways/security.md

### They ask what a pilot needs from Hatchways.

- Reply goal: Ask for one internal repo assessment, a workflow-secret owner, and one reviewer to judge the packet.
- Proof: https://hottea.ai/hatchways/kickoff.md

### They say a GitHub App is mandatory first.

- Reply goal: Record the account-level blocker; do not imply the app exists. The next action is app creation plus GITHUB_APP_INSTALL_URL configuration.
- Proof: https://hottea.ai/hatchways/readiness.md

## Required Access For A Pilot

- One synthetic or internal Hatchways-style candidate repo.
- Permission to add or simulate the /github-action.yml fallback.
- Workflow secret access for AGENTIC_EVIDENCE_SESSION_ID and AGENTIC_EVIDENCE_TOKEN.
- One reviewer owner who can compare the HotTea packet beside the normal Hatchways review surface.

## Suggested Reply

```
This is scoped as a technical proof, not an enterprise rollout.

The quickest path would be one internal Hatchways-style repo assessment using the GitHub Actions fallback.

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

Kickoff checklist: https://hottea.ai/hatchways/kickoff.md

If a real GitHub App is mandatory before any pilot, that is the current account-level blocker rather than a hidden product claim.
```

## Stop Conditions

- Stop before claiming an official Hatchways partnership.
- Stop before claiming enterprise procurement readiness, SOC 2, DPA, SSO, or retention SLA coverage.
- Stop before claiming a real GitHub App exists without GITHUB_APP_INSTALL_URL configured and live-smoked.
- Stop before sending customer or production candidate traffic through the pilot.

## Current Blockers

- The real GitHub App still requires account-level creation and GITHUB_APP_INSTALL_URL deployment configuration.
- Until that app exists, GitHub Actions remains the verified fallback adapter.

## Not Claimed

- No official Hatchways partnership.
- No real GitHub App before GITHUB_APP_INSTALL_URL is configured.
- No enterprise procurement readiness.
- No customer production rollout.
- No perfect outside-AI prevention or proctoring claim.
- No automated hiring decision.

## Proof URLs

- Reply kit JSON: https://hottea.ai/hatchways/reply-kit.json
- Proof index: https://hottea.ai/hatchways
- Demo script: https://hottea.ai/hatchways/demo-script.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- Security packet: https://hottea.ai/hatchways/security.md
- Kickoff checklist: https://hottea.ai/hatchways/kickoff.md