# escales · gigs / network / pricing

*Port calls — each gig is a stopover; each owes a* droit de port *(harbor due = your fee).*

**Not a booking app — strategic memory** that compounds into two payoffs:

1. **Pricing oracle.** Log every inquiry's *droit de port*: `{org, type, region,
   fee_asked, outcome}`. After ~a dozen entries it stops being a diary and starts
   answering "what should I ask for a venue like this, here?" The recent
   *"went with the house DJ for budget"* decline is data point #1 — calibrate, don't sting.
2. **Flotille graph.** The network of budding artists = the #1 growth engine. Track
   collabs ↔ gigs ↔ who-opened-which-door in [`flotille.yaml`](flotille.yaml).

## Relationship to the site (don't duplicate)

The ParVagues site already holds the gig map:
`~/Work/Web/www/next/content/lives/{year}/{slug}.md` (+ `tracks.json` setlists +
`ontology/events.yaml`). `escales` is a **sidecar keyed by gig slug** that adds only
what the site lacks and shouldn't publish:

- **`fee_asked` / `outcome`** — PRIVATE. → `escales.yaml` is **gitignored**.
- **`real_gig`** — in-person/public/bookable vs stream/online/corporate (needs PLN's call).
- **`coplayers`** — who else was on the bill → flotille edges.

## Gig enrichment (scanner, TODO)

For each gig, fetch from its event page (`ctaURL` / poster URLs):
- **poster / flyer images** → reuse in site media & `phare`
- **co-artists / lineup** → flotille graph
- **venue, time, organizer** → confirm/enrich ontology
Store images under the site's `public/images/parvagues/lives/{year}/{slug}/`.
Respect source terms; cache locally; PLN confirms which gigs to enrich.

## Files

- `escales.example.yaml` — committed schema/template (anonymized).
- `escales.yaml` — **gitignored**, real ledger incl. private fees.
- `flotille.yaml` — committed network graph (collaborators are already public).
