# Hatchways Pilot Decision Brief

Give a Hatchways product or partnerships owner the concrete pilot decision, acceptance bar, current gates, and next proof URL without requiring a full packet read.

## Recommended Decision

Run a limited technical pilot through the verified GitHub Actions fallback before investing in a real GitHub App.

Decision-owner question: Is a tokenized reviewer packet plus GitHub Actions evidence enough to evaluate the Agentic Mode fit, or must the GitHub App exist before any Hatchways-side review?

## Pilot Acceptance Bar

### Reviewer can inspect one packet in under 10 minutes.

- Proof: https://hottea.ai/hatchways/pilot.md
- Pass signal: Reviewer finds hidden checks, transcript/session counts, git/test evidence, VM events, and ATS-ready reviewer note without a live walkthrough.

### Repo assessment flow stays intact.

- Proof: https://hottea.ai/hatchways/integration.md
- Pass signal: Candidate repo, PR metadata, public tests, hidden grading, and human review remain the core Hatchways workflow.

### AI-agent evidence is visible without proctoring.

- Proof: https://hottea.ai/sample-report
- Pass signal: Claude JSONL exports, terminal events, prompt sequence, git snapshots, and anomaly context are available to the reviewer.

### Current limits are explicit.

- Proof: https://hottea.ai/hatchways/security.md
- Pass signal: GitHub App, SOC 2, DPA, SSO, retention SLA, and procurement gaps are named before any enterprise claim.

## Go Path

1. Use /github-action.yml with a Hatchways-style candidate repo.
2. Attach /hatchways/pilot.md and /sample-report to one internal reviewer evaluation.
3. Collect reviewer feedback on where the report URL should sit: candidate invite, PR summary, reviewer note, or ATS note.
4. Only build or configure the real GitHub App after the fallback packet proves useful.

## No-Go Signals

- Hatchways requires a real GitHub App before even a technical pilot.
- Hatchways reviewers need formal procurement artifacts before inspecting public sample packets.
- The buyer wants anti-cheat/proctoring claims rather than standardized AI-use evidence.

## 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 perfect anti-cheat or outside-AI prevention.
- No automated hiring decision.
- No enterprise procurement readiness before the named gates are complete.

## Proof URLs

- Decision JSON: https://hottea.ai/hatchways/decision.json
- Pilot kit: https://hottea.ai/hatchways/pilot.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- Security packet: https://hottea.ai/hatchways/security.md
- Sample reviewer packet: https://hottea.ai/sample-report