# LOI redlines — pilot type index

Legal-ready **Letter of Intent** drafts with annotated customer redlines and NADIR fallback positions.

**Disclaimer:** These are non-binding templates for negotiation. Have counsel review before signature.

## Variants

| Variant | File | Pilot package | Typical buyer |
|---------|------|---------------|---------------|
| **Design partner · Fleet shadow** | [`design_partner_fleet_loi.md`](design_partner_fleet_loi.md) | Amazon Logistics | Fleet safety, last-mile ops |
| **Repair network · Glass QA** | [`repair_network_glass_loi.md`](repair_network_glass_loi.md) | Safelite | QA, calibration ops, fleet accounts |
| **MSO · Collision evidence** | [`mso_collision_evidence_loi.md`](mso_collision_evidence_loi.md) | Caliber Collision | Regional ops, DRP, insurer relations |

## How to read redlines

Each document uses this convention:

| Marker | Meaning |
|--------|---------|
| **Standard text** | NADIR proposed language |
| `> **CUSTOMER REDLINE (typical):**` | Language customers or their counsel often request |
| `> **NADIR POSITION:**` | Our acceptable fallback or counter |
| `[Bracket placeholders]` | Fill before sending |

## Related

- Master template: `NADIR_DOCUMENTATION/09_execution_plans/loi_template.md`
- Exhibit A per package: `pilots/{name}/loi_exhibit_a.md`
- Export to PDF: `python scripts/generate_pilot_pdf.py --pilot amazon-logistics --sections loi_exhibit_a.md`

## Machine-readable

[`redline_config.json`](redline_config.json)

## LOI demo v2 (email-ready package)

End-to-end dry-run for outreach attach lists:

```bash
python scripts/nadir_loi_demo.py --v2 --skip-api --company "Safelite" --copy
```

Produces `VISUALS_RECORDS_ASSETS/demo_data/loi_demo_v2/loi_demo_v2.json` with:

- `replay_summary` from week-1 CSV manifest
- `pilot_metrics.json` for Exhibit A
- `email.subject`, `email.body`, `email.attachments[]` for Gmail paste