nx_vizsla_venue.nx

nx_vizsla_venue.nx -- NISHI VIZSLA VENUE PIPELINE: coordinate finding + hiring buildings. Operator 2026-07-07: "coordinating the finding and hiring of buildings". The deal-pipeline pattern (nx_vizsla_deal precedent) applied to venue hire: REQUIREMENTS -> CANDIDATES -> additive STAGE history (found/contacted/quoted/visited/booked/rejected, latest-by-date wins, nothing destroyed) -> integer FIT SCORE vs the requirement -> a BOOKED venue emits the exact calendar EVENT line so the hire lands on the group calendar (composes nx_vizsla_calendar's load format -- the bridge is data, not a fork). Records (load <file> <prefix> [segid], additive + CID-idempotent): REQ <event> <capacity> <budget_cents> <date> <start_min> <dur_min> -> "req:" VENUE <event> <vid> <capacity> <cost_cents> <contact> <name> -> "ven:" STAGE <date> <event> <vid> <found|contacted|quoted|visited|booked|rejected> -> "stg:" Command: board <prefix> <event> per candidate: latest stage + fit score = cap_ok*50 + within_budget*30 + ((budget-cost)*20)/budget (cheaper = better, integer) with over_budget/too_small flags; sorted score desc / cost asc / vid. best = top non-rejected. A booked venue emits VIZSLA-VEN-BOOKED + VIZSLA-VEN-CAL-LINE "EVENT venue-<event> <date> <start> <dur> <name>". Loud-fail: missing REQ, unknown event, bad stage word, bad numbers/dates. Score weights 50/30/20 are the documented v1 model (single place, swap for CONF rows when multi-event tuning is real -- rule 11 exception documented, not buried). spec: knowledge/research/2026-06-22-vizsla-sclass-roadmap.md license_tier: ORIGINAL