Manifest Field Ops

# Manifest Field Ops Runbook
 
**Purpose:** Convert event/conference conversations into scoped work mapped to execution plan IDs.
 
---
 
## Scope Boundary
 
- Phase 1 execution remains `US->CA` for SHIP + TRADE.
- Do not commit to Phase 2/3 features during field conversations.
- Any new request must map to an existing plan ID (or create one) before execution.
 
---
 
## Capture Template
 
Use one row per conversation:
 
| Company | Contact | Type (partner/customer/investor/competitor) | Signal | Plan ID (`P7-A/B/C/D` or `No plan ID`) | Next action | Owner | Due |
|--------|---------|-----------------------------------------------|--------|-----------------------------------------|-------------|-------|-----|
 
---
 
## 48-Hour Closeout
 
1. Deduplicate conversation rows.
2. Update `P7-A` partner pipeline with ranked targets and intro paths.
3. Update `P7-B` competitor brief draft with deltas and response implications.
4. Select at most one `P7-C` adapter spike candidate and define go/no-go criteria.
5. Update `P7-D` corridor model backlog if conversation implies new corridor demand.
6. Add summary entry in `docs/SESSION_LOG.md`.
 
---
 
## Claims Discipline
 
Before using numbers externally:
 
1. Mark claim as `Validated`, `Projected`, or `External/volatile`.
2. Attach source and date.
3. If unverified, treat as projected.