# Pilot Onboarding Playbook

This playbook is the shortest path from Frontier-grade product evidence to a real first pilot DAO.

It does not claim that a pilot has already signed. It defines how to onboard the first serious organization without improvisation.

## Pilot Goal

Get one real organization through:

1. Create DAO
2. Submit proposal
3. Private vote
4. Execute treasury

on Devnet first, with an evidence packet that a non-builder stakeholder can understand.

## Best First Pilot Segments

- grant committee
- crypto-native fund
- gaming DAO
- enterprise-style internal governance team

## Matching Packs

- `docs/grant-committee-pack.md`
- `docs/fund-governance-pack.md`
- `docs/gaming-dao-pack.md`
- `docs/enterprise-dao-pack.md`

## Pilot Intake

Before kickoff, record:

- organization name
- segment
- target use case pack
- named operator contact
- signer and custody expectations
- whether confidentiality is required for voting, payouts, or both
- success criteria

## Recommended 14-Day Pilot Sequence

### Day 1-2 — discovery

- map one real approval flow
- choose one treasury action type
- choose one operator

### Day 3-5 — simulation

- run the Production Simulation DAO path
- complete the guided UI lifecycle
- capture runtime evidence and notes

### Day 6-9 — operator rehearsal

- operator creates a DAO
- operator submits a proposal
- operator completes a private vote
- operator executes the treasury step on Devnet

### Day 10-14 — review and next step

- review evidence packet with stakeholders
- decide whether to extend the pilot
- decide whether stronger custody and audit steps are justified

## Pilot Success Criteria

- operator can complete the full lifecycle without developer intervention
- stakeholders understand the privacy boundary
- evidence packet is strong enough for internal review
- the chosen use case pack fits the real operating need

## Required Pilot Evidence

- DAO creation signature
- proposal creation signature
- commit signature
- reveal signature
- execute signature
- screenshot or recording of the guided flow
- operator notes on pain points and blockers

## Repository Updates After Pilot

Once a real pilot starts, update:

- `docs/pilot-program.md`
- `docs/trust-package.md`
- `docs/launch-trust-packet.generated.json`
- `docs/launch-trust-packet.generated.md`

## Honest Boundary

This repository contains the onboarding procedure and the simulation material.

It does not fabricate a signed pilot customer or a completed production rollout.