# Hatchways Agentic Mode Demo Script

Give a Hatchways product, partnerships, or reviewer-ops owner a short proof path that can be run without a meeting, account creation, or GitHub App setup.

Runtime: 7 minutes.

## Demo Steps

### 0:00

- Action: Open the Hatchways proof page and confirm the positioning is an add-on for repo-based practical assessments, not a replacement coding-test platform.
- URL: https://hottea.ai/hatchways
- Expected signal: The page names real GitHub repos, practical tasks, automated tests, hidden grading, and human review as the preserved Hatchways shape.

### 1:00

- Action: Open the sample reviewer packet and scan the top evidence summary.
- URL: https://hottea.ai/sample-report
- Expected signal: Reviewer sees a 9/10 aid score, hidden-test result, AI-process analysis, Claude JSONL export count, git/test evidence, VM events, and ATS-ready note.

### 2:30

- Action: Open the Markdown sample packet for copy/paste review.
- URL: https://hottea.ai/sample-report.md
- Expected signal: Reviewer can copy a concise packet into an internal review note without logging into HotTea.

### 3:30

- Action: Open the GitHub Actions fallback and integration guide.
- URL: https://hottea.ai/hatchways/integration.md
- Expected signal: Engineering sees a no-GitHub-App-required adapter path plus the account-gated GitHub App boundary.

### 5:00

- Action: Open the objection packet and security packet before deciding whether this is ready for a technical pilot.
- URL: https://hottea.ai/hatchways/objections.md
- Expected signal: Buyer sees the GitHub App, procurement, partnership, anti-cheat, and enterprise-readiness limits stated explicitly.

### 6:30

- Action: Use the decision brief to make the next-step call.
- URL: https://hottea.ai/hatchways/decision.md
- Expected signal: The only recommended next step is a limited technical pilot, not a customer rollout or procurement claim.

## Stop Conditions

- Stop if a real GitHub App is mandatory before any technical review; that remains account-gated until GITHUB_APP_INSTALL_URL is configured.
- Stop if enterprise procurement artifacts are required before a pilot; SOC 2, DPA, SSO, retention SLA, and vendor security review are not complete.
- Stop if the buyer expects perfect outside-AI prevention; the product provides standardized access, evidence, and anomaly context, not a perfect anti-cheat claim.

## Success Criteria

- A Hatchways reviewer can decide whether the sample packet adds useful signal within seven minutes.
- An engineering owner can identify the fallback integration path and the GitHub App blocker.
- A product or partnerships owner can describe the pilot boundary without overstating current claims.

## Not Claimed

- No official Hatchways partnership.
- No real GitHub App before GITHUB_APP_INSTALL_URL is configured.
- No enterprise procurement readiness.
- No perfect anti-cheat or outside-AI prevention.
- No automated hiring decision.

## Proof URLs

- Demo script JSON: https://hottea.ai/hatchways/demo-script.json
- Proof page: https://hottea.ai/hatchways
- Sample reviewer packet: https://hottea.ai/sample-report
- Markdown reviewer packet: https://hottea.ai/sample-report.md
- Integration guide: https://hottea.ai/hatchways/integration.md
- Objection packet: https://hottea.ai/hatchways/objections.md
- Security packet: https://hottea.ai/hatchways/security.md
- Decision brief: https://hottea.ai/hatchways/decision.md