# Hatchways Pilot Next Step

Give Hatchways one concrete next action after the proof-packet follow-up: either an async packet review, a synthetic repo pilot through GitHub Actions, or an explicit account-level GitHub App blocker.

Recommended path: Start with a 20-minute async review of the proof index and sample reviewer packet. If the packet is useful, run one synthetic/internal Hatchways-style repo through the GitHub Actions fallback before spending account work on a real GitHub App.

## Next Actions

### Async proof review

- Owner: Hatchways product or reviewer lead
- Buyer ask: Open the proof index, sample report, and pilot kit; answer whether the packet is useful enough to test with one internal repo.
- Proof: https://hottea.ai/hatchways/index.md
- Pass signal: Reviewer can identify correctness, AI process quality, hidden-test state, git/test evidence, and follow-up questions in under 20 minutes.

### Synthetic repo pilot

- Owner: Hatchways engineering or assessment-ops owner
- Buyer ask: Pick one synthetic/internal repo assessment and allow the /github-action.yml fallback to post evidence into a HotTea session.
- Proof: https://hottea.ai/hatchways/integration.md
- Pass signal: A reviewer can compare the HotTea packet beside the normal Hatchways review surface without a custom integration.

### GitHub App account work

- Owner: Foundry/Owl after account-level GitHub App creation is available
- Buyer ask: Only require this before pilot if Hatchways will not evaluate the GitHub Actions fallback.
- Proof: https://hottea.ai/github-app/setup.md
- Pass signal: GITHUB_APP_INSTALL_URL is configured, /github-app/install redirects, and signed webhook ingestion exists.

## Proof Commands

- GET https://hottea.ai/hatchways/index.md
- GET https://hottea.ai/sample-report
- GET https://hottea.ai/github-action.yml
- GET https://hottea.ai/hatchways/pilot-next-step.json
- GET https://hottea.ai/api/config

## Decision Rules

- If the packet is not useful after async review, stop and revise the reviewer evidence format.
- If the packet is useful and GitHub Actions fallback is acceptable, run one synthetic/internal repo pilot.
- If the fallback is unacceptable, treat real GitHub App creation and GITHUB_APP_INSTALL_URL as the next account-level blocker.
- If procurement gates are required before any technical review, do not route customer candidate data through HotTea.

## 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.
- No signed GitHub App webhook ingestion exists until app credentials and webhook verifier are implemented.
- No enterprise procurement package exists beyond current proof/security/retention packets.

## Not Claimed

- No official Hatchways partnership.
- No real GitHub App before GITHUB_APP_INSTALL_URL is configured.
- No signed GitHub App webhook ingestion before credentials and verifier exist.
- No enterprise procurement readiness, SOC 2, DPA, SSO, or retention SLA claim.
- No production customer rollout.
- No perfect anti-cheat or outside-AI prevention.
- No automated hiring decision.

## Proof URLs

- Pilot next-step JSON: https://hottea.ai/hatchways/pilot-next-step.json
- Proof index: https://hottea.ai/hatchways/index.md
- Sample reviewer packet: https://hottea.ai/sample-report
- Pilot kit: https://hottea.ai/hatchways/pilot.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- GitHub App setup packet: https://hottea.ai/github-app/setup.md