# Hatchways First-Call Meeting Brief

Turn buyer interest into one concrete technical-pilot decision without drifting into generic platform sales or unsupported enterprise claims.

Boundary: Twenty-five minutes, one Hatchways-style repo assessment, one reviewer owner, GitHub Actions fallback only, and no customer production traffic.

## Agenda

### 0-3: Confirm fit

- Question: Does Hatchways want an additive Agentic Mode evidence layer for practical repo assessments, or a different AI-interview product shape?
- Proof: https://hottea.ai/hatchways/index.md

### 3-8: Inspect sample packet

- Question: Can one reviewer use the sample packet to see correctness, hidden checks, AI process quality, git/test evidence, and follow-up questions?
- Proof: https://hottea.ai/sample-report

### 8-13: Validate repo workflow

- Question: Is the GitHub Actions fallback enough to evaluate a technical pilot before a real GitHub App exists?
- Proof: https://hottea.ai/hatchways/integration.md

### 13-18: Name gates

- Question: Which gate blocks a pilot: GitHub App, security/procurement, reviewer usefulness, or no buyer need?
- Proof: https://hottea.ai/hatchways/readiness.md

### 18-25: Decide next action

- Question: Should the next step be an async packet review, one synthetic repo pilot, GitHub App creation, or stop?
- Proof: https://hottea.ai/hatchways/decision.md

## Decision Log Template

- pilot_repo: One internal or synthetic Hatchways-style repo assessment to use, or explicit none.
- reviewer_owner: One owner who will inspect the packet and answer the pilot questions.
- adapter_path: GitHub Actions fallback accepted, real GitHub App required first, or no integration path.
- security_gate: Technical pilot allowed without procurement, procurement required first, or blocked.
- next_action: Async review, synthetic pilot, GitHub App setup, procurement packet, or stop.

## Useful Outcomes

- Hatchways accepts a GitHub Actions fallback for one internal technical pilot.
- Hatchways says a real GitHub App is mandatory first, making the account-level blocker explicit.
- Hatchways reviewer-ops says the packet is or is not useful after inspecting the sample.
- Hatchways security/procurement states the minimum gate for a technical pilot.

## Stop Conditions

- Stop if the conversation requires customer candidate traffic before a synthetic/internal pilot.
- Stop if the buyer asks for proctoring, locked browser, or perfect anti-cheat as the core promise.
- Stop if a real GitHub App is mandatory before any review and GITHUB_APP_INSTALL_URL is still unconfigured.
- Stop before claiming Hatchways partnership, enterprise procurement readiness, or automated hiring decisions.

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

- Meeting brief JSON: https://hottea.ai/hatchways/meeting-brief.json
- Proof index: https://hottea.ai/hatchways/index.md
- Sample reviewer packet: https://hottea.ai/sample-report
- Integration guide: https://hottea.ai/hatchways/integration.md
- Readiness scorecard: https://hottea.ai/hatchways/readiness.md
- Decision brief: https://hottea.ai/hatchways/decision.md