nx_vizsla_calendar_conflict_gate.nx

nx_vizsla_calendar_conflict_gate.nx -- VIZSLA R-CAL.2 gate: conflict detection (overlap scan across the expanded occurrences + single events) is gate-proven against construction-known fixtures with HAND-COMPUTED overlaps (oracle in THIS header). 100% sovereign: self-writes fixtures via the organ's syscalls, forks the organ, greps stdout. fixture (seg-7001), single EVENTs + one DAILY RRULE: meeting 06-22 09:00 +60 -> [540,600) call 06-22 09:30 +30 -> [570,600) after 06-22 10:00 +30 -> [600,630) (back-to-back with meeting/call -- MUST NOT conflict) lunch 06-22 12:00 +60 -> [720,780) solo 06-23 09:00 +60 -> [540,600) (different day) standup 06-22 09:15 +30 DAILY x1 -> [555,585) (a RECURRING occurrence that overlaps meeting AND call) W1 conflicts 06-22..06-22 (sorted meeting/standup/call/after/lunch) => meeting x standup [555,585)=09:15-09:45 ; meeting x call [570,600)=09:30-10:00 ; standup x call [570,585)=09:30-09:45 (after is adjacent -> NO clash) => occurrences=5 conflicts=3 W2 conflicts 06-23..06-23 => only solo => occurrences=1 conflicts=0 (no false positive) Rows: 1 conflict-load 6 records -> new=6 seg-7001 2 conflict-overlap-events meeting x call line exact (two single events) 3 conflict-recurring meeting x standup line exact (the RRULE occurrence participates) 4 conflict-three-way standup x call line exact 5 conflict-verdict occurrences=5 conflicts=3 (adjacency 'after' counted but NOT a clash) 6 no-conflict-other-day W2 occurrences=1 conflicts=0 (day isolation, no false positive) 7 conflict-determinism W1 byte-identical twice 8 loud-fail-bad-date conflicts from=2026-13-99 => exit 1 [negative control] Evidence: VIZSLA-CAL-CONFLICT-GATE -> stdout + knowledge/status/vizsla_gate.log; exit 0 iff 8/8. spec: knowledge/research/2026-06-22-vizsla-sclass-roadmap.md license_tier: ORIGINAL