# Hatchways Technical Pilot Kickoff

Turn the limited-pilot setup worksheet into a first-call agenda and access checklist for one Hatchways-style repo assessment.

Boundary: One synthetic or internal candidate repo, one Hatchways reviewer, GitHub Actions fallback only, no customer traffic, and no procurement claim.

## Pre-Call Artifacts

### Sample reviewer packet

- URL: https://hottea.ai/sample-report
- Use: Confirm the evidence packet adds reviewer signal before any integration work.

### Sample manifest

- URL: https://hottea.ai/sample-report/manifest.md
- Use: Inspect the packet in a deterministic order: correctness, AI collaboration, engineering process, reviewer handoff.

### GitHub Actions fallback

- URL: https://hottea.ai/github-action.yml
- Use: Validate that repo, PR, SHA, diff, test, and session-export evidence can post without a GitHub App.

### Trial acceptance checklist

- URL: https://hottea.ai/hatchways/trial-acceptance.md
- Use: Decide whether the fallback evidence path is enough for a technical trial.

## Kickoff Agenda

1. Pick one Hatchways-style repo assessment and identify the expected public test command.
2. Decide where the HotTea URL should appear: candidate invite, candidate repo README, PR summary, reviewer note, or ATS note.
3. Add /github-action.yml or equivalent POST from an existing marking workflow.
4. Run one candidate-style dry run through the VM, ae-task, ae-claude or ae-codex, tests, ae-finalize, and final submission.
5. Have one reviewer compare the generated packet beside the normal Hatchways review surface.
6. Make a go/no-go call on whether the real GitHub App is worth account-level setup.

## Required Access

- Pilot repo write access: Adding the GitHub Actions fallback or equivalent evidence POST.
- Workflow secret access: Setting AGENTIC_EVIDENCE_SESSION_ID and AGENTIC_EVIDENCE_TOKEN for the pilot repo.
- One reviewer owner: Answering whether the packet adds useful signal beside hidden grading.
- GitHub App setup authority: Only needed after the fallback packet proves useful; still blocked until GITHUB_APP_INSTALL_URL is configured.

## Proof Commands

- `curl -fsS https://hottea.ai/sample-report/manifest.md`
- `curl -fsS https://hottea.ai/hatchways/trial-acceptance.md`
- `curl -fsS https://hottea.ai/github-action.yml`
- `curl -fsS https://hottea.ai/hatchways/kickoff.json`

## Success Signals

- Reviewer can identify correctness, hidden grading, AI-session evidence, git/test telemetry, and final notes in under 10 minutes.
- Engineering can attach the fallback without a GitHub App.
- Product can state the next action without implying partnership, procurement readiness, or perfect anti-cheat.

## 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

- Kickoff JSON: https://hottea.ai/hatchways/kickoff.json
- Sample reviewer packet: https://hottea.ai/sample-report
- Sample manifest: https://hottea.ai/sample-report/manifest.md
- GitHub Action adapter: https://hottea.ai/github-action.yml
- Trial acceptance checklist: https://hottea.ai/hatchways/trial-acceptance.md
- Pilot setup worksheet: https://hottea.ai/hatchways/pilot-setup.md