YouTube2Text

HOA Diverted My Irrigation Water to Their Lake — Then the Ditch Company’s Gate Logs Exposed It — Transcript

by HOA LAND WARS · 6,680 words · 1,057 segments · language en · Watch on YouTube

Full transcript

  1. 0:00The first time I knew something was
  2. 0:01wrong, Clare Voss was standing beside
  3. 0:04the diversion gate in a crimson red
  4. 0:06blazer while an HOA contractor adjusted
  5. 0:08the hardware that controlled water
  6. 0:10flowing toward my ranch. My irrigation
  7. 0:12ditch was already running lower than it
  8. 0:14should have, but the decorative lake
  9. 0:16inside the subdivision was rising fast.
  10. 0:19I started photographing the gate, the
  11. 0:21water line, and the time. What I did not
  12. 0:23know yet was that every adjustment had
  13. 0:26already been recorded. My name is Grant
  14. 0:28Ellison. I am 56 years old and I run
  15. 0:31cattle on a dry country property that
  16. 0:33depends on scheduled irrigation water to
  17. 0:35keep pasture productive through the
  18. 0:37hottest part of the season. When my turn
  19. 0:39comes, I need that water moving through
  20. 0:41the lateral ditch and into the fields
  21. 0:43where it was assigned. A main irrigation
  22. 0:45ditch runs along the eastern edge of the
  23. 0:47valley. Smaller laterals branch off from
  24. 0:50it at controlled turnouts. One feeds my
  25. 0:53ranch. Another serves land farther north
  26. 0:56near Fair Haven Crossing, an upscale
  27. 0:58subdivision built around landscaped
  28. 1:00common areas and a decorative lake. For
  29. 1:03years, the arrangement caused no
  30. 1:05trouble. The ditch company published
  31. 1:07delivery schedules. Gates were adjusted
  32. 1:10as water moved from one account to the
  33. 1:12next. I tracked my start times, watched
  34. 1:14the flow at my turnout, and moved water
  35. 1:16across the pasture according to the same
  36. 1:18routine every summer. Clare Voss became
  37. 1:21president of the Fair Haven Crossing HOA
  38. 1:23the previous year. She was 43, polished,
  39. 1:27sharp, and easy to spot near the ditch
  40. 1:30because she almost always wore red. That
  41. 1:33afternoon, it was a fitted crimson
  42. 1:34blazer, black trousers, and dark shoes
  43. 1:37that looked out of place beside
  44. 1:39steelgate hardware and dusty ditch
  45. 1:41banks. I had seen HOA crews maintaining
  46. 1:44the lake shoreline and common area
  47. 1:46landscaping before. None of that
  48. 1:48interested me as long as their work
  49. 1:50stayed inside their own system. What
  50. 1:52caught my attention that day was the
  51. 1:54sound of metal. I had driven toward my
  52. 1:57turnout because the flow at the ranch
  53. 1:59had dropped more quickly than expected.
  54. 2:01My delivery window was still active, yet
  55. 2:04the water entering my lateral looked
  56. 2:06weak. Wet marks showed higher on the
  57. 2:08ditch wall than the current level. That
  58. 2:10was not normal for the middle of a
  59. 2:12scheduled run. I followed the ditch
  60. 2:14upstream near the split toward Fair
  61. 2:16Haven Crossing. A contractor was leaning
  62. 2:18over the gate mechanism with a wrench
  63. 2:20and a long metal handle. Clare stood
  64. 2:23several yards away with a black folder
  65. 2:25under one arm, watching the work. The
  66. 2:27contractor changed the gate position.
  67. 2:30The sound of rushing water changed
  68. 2:31almost immediately. More water pushed
  69. 2:34toward the branch leading north. Less
  70. 2:37continued toward my side. I did not know
  71. 2:39exactly what authority the contractor
  72. 2:41had, and I did not want to turn a water
  73. 2:44problem into a shouting match before I
  74. 2:46understood what had happened. So, I took
  75. 2:48out my phone. First, I photographed the
  76. 2:51gate from far enough back to show both
  77. 2:53channels. Then, I photographed the gate
  78. 2:55stem, exposed threads, locking hardware,
  79. 2:58and direction of flow. I took another
  80. 3:00image that included Clare, the
  81. 3:02contractor, and the turnout in the same
  82. 3:04frame. Then I recorded a short video of
  83. 3:07the water moving past the split. The
  84. 3:10difference between the two branches was
  85. 3:11visible. The branch toward Fair Haven
  86. 3:14Crossing carried a stronger current. The
  87. 3:16branch toward my ranch looked reduced.
  88. 3:18Clare noticed what I was doing. Her
  89. 3:21posture stiffened. She shifted the black
  90. 3:23folder against her side and watched me
  91. 3:25with irritated focus, as if the
  92. 3:27paperwork in her hand should settle the
  93. 3:29issue. I kept documenting. The ditch
  94. 3:32bank was dry enough that recent changes
  95. 3:34in water level left clear marks. I
  96. 3:37photographed those, too. Then I drove
  97. 3:40back toward the ranch. At my turnout,
  98. 3:42the flow had dropped even farther. I
  99. 3:45placed a measuring rod at the point I
  100. 3:47normally use to monitor depth and
  101. 3:49photographed the reading. I wrote down
  102. 3:51the time in a notebook I kept in the
  103. 3:53truck. The pasture nearest the turnout
  104. 3:56was still green, but the soil farther
  105. 3:58out had already started drying under
  106. 3:59several days of heat. One missed hour
  107. 4:02would not ruin it. A badly reduced
  108. 4:04delivery over the rest of the cycle
  109. 4:06could. That was the part outsiders
  110. 4:09sometimes missed about irrigation. The
  111. 4:11value was not just in water existing
  112. 4:13somewhere in the system. The timing,
  113. 4:15volume, and destination mattered. A
  114. 4:18ranch could sit near a full ditch and
  115. 4:20still lose a crop if the assigned flow
  116. 4:22never reached the right turnout during
  117. 4:24the scheduled window. I checked my
  118. 4:26delivery schedule again. My account was
  119. 4:29still active. The printed time block had
  120. 4:31not ended. I had no notice of a
  121. 4:33shutdown, maintenance warning, or
  122. 4:35reduced service. Nothing in my paperwork
  123. 4:38explained why the flow had changed. Late
  124. 4:41that afternoon, I drove past the road
  125. 4:44bordering Fair Haven Crossing. The
  126. 4:46decorative lake was visible through an
  127. 4:48opening between landscaped trees. Its
  128. 4:50water line looked high. Fresh water was
  129. 4:53moving through an inlet near the south
  130. 4:54end, sending a light ripple across the
  131. 4:57surface. around it. The HOA common area
  132. 5:00looked almost unnaturally green against
  133. 5:02the dry hills beyond the subdivision. I
  134. 5:05stopped where I could see the lake
  135. 5:07without entering HOA property and took
  136. 5:09another photograph. The image had been
  137. 5:11taken less than an hour after the
  138. 5:13contractor adjusted the diversion gate.
  139. 5:16That did not prove the water in the lake
  140. 5:18was mine. It proved only that two things
  141. 5:21were happening at the same time. My
  142. 5:23ranch flow had dropped. The HOA side
  143. 5:26flow had increased. I needed more than
  144. 5:29coincidence.
  145. 5:31I needed to know what the ditch company
  146. 5:32believed the gate position should have
  147. 5:34been during my delivery window. Before
  148. 5:37sunset, I went back one more time to the
  149. 5:39turnout. The contractor was gone. Claire
  150. 5:42was gone. The gate remained in the new
  151. 5:45position. I photographed it again from
  152. 5:48the same angle I had used earlier. That
  153. 5:50gave me a clear sequence for the
  154. 5:52afternoon. The final image showed one
  155. 5:54detail I had missed while everyone was
  156. 5:56standing there. A small metal
  157. 5:58identification plate was bolted to the
  158. 6:00gate assembly. It carried a turnout
  159. 6:03number and a ditch company asset code. I
  160. 6:06zoomed in until both were readable. That
  161. 6:09number was more useful than Claire's
  162. 6:10folder, more useful than the HOA lake,
  163. 6:13and more useful than any argument I
  164. 6:15could have had beside the ditch. It gave
  165. 6:18me a specific control point and if the
  166. 6:20ditch company tracked adjustments at
  167. 6:22that control point, there should be a
  168. 6:24record showing exactly when someone
  169. 6:26changed it. The next morning, I stopped
  170. 6:29treating the problem like a strange
  171. 6:30water reading and started treating it
  172. 6:32like a failed delivery. My first job was
  173. 6:35to eliminate anything on my own property
  174. 6:37that could explain the shortage. I
  175. 6:40walked the lateral from the ranch
  176. 6:41turnout to the first pasture check
  177. 6:43structure. The headgate was fully open.
  178. 6:45The channel was clear enough to carry
  179. 6:47normal flow, and none of the banks had
  180. 6:49slumped into the ditch overnight. Water
  181. 6:52was reaching the ranch. It simply was
  182. 6:54not arriving in the volume my scheduled
  183. 6:56run required. That sent the problem
  184. 6:58upstream. The timing made it urgent. My
  185. 7:02cattle were supposed to rotate onto the
  186. 7:03upper pasture after this irrigation
  187. 7:05cycle. The winter feed acorage beside it
  188. 7:09was also due for water. If I lost enough
  189. 7:11of the delivery, I would not just be
  190. 7:13looking at dry grass. I would have to
  191. 7:15change grazing plans and possibly
  192. 7:18replace feed I had expected to produce
  193. 7:20myself. I drove into the upper pasture
  194. 7:23instead of spending another hour beside
  195. 7:25the ditch. The difference was already
  196. 7:27visible from the truck. Grass closest to
  197. 7:30the lower irrigated ground still held
  198. 7:32good color, but the higher section had
  199. 7:35begun taking on a duller cast under the
  200. 7:37heat. I walked far enough into the field
  201. 7:39to press a soil probe into several
  202. 7:41places. Moisture remained deeper down,
  203. 7:44yet the top layer was drying faster than
  204. 7:46it should have during an active run.
  205. 7:49That gave me a practical deadline. The
  206. 7:51field was not ruined. It was still
  207. 7:53recoverable, but the missing water had
  208. 7:56started costing me time.
  209. 7:58I changed the cattle rotation that
  210. 8:00morning and kept the herd off the upper
  211. 8:02section. That bought the pasture a
  212. 8:04little protection, but it also turned
  213. 8:06the shortage into an operational problem
  214. 8:08I could no longer ignore. Back at the
  215. 8:10truck, I pulled out my irrigation
  216. 8:12schedule. My account was still inside
  217. 8:15its assigned delivery window. There was
  218. 8:17no maintenance notice, no shortened run,
  219. 8:20and no indication that my turn had been
  220. 8:22moved. I checked the time against the
  221. 8:24notes from the previous afternoon. The
  222. 8:26contractor had adjusted the diversion
  223. 8:28gate while my account was active. My
  224. 8:31turnout had weakened afterward. That was
  225. 8:33enough to justify looking beyond the
  226. 8:35ranch. I drove upstream again, but this
  227. 8:38time I did not stop first at the main
  228. 8:40diversion gate. I continued along the
  229. 8:43public ditch road toward a small
  230. 8:44measurement structure the company used
  231. 8:46farther down the branch serving my
  232. 8:48property. Water passed through it, but
  233. 8:50the current looked noticeably weaker
  234. 8:52than I was accustomed to seeing during a
  235. 8:54full run. That observation gave me
  236. 8:57something more useful than another
  237. 8:58photograph of dry grass. The shortage
  238. 9:01existed before the water reached my
  239. 9:03ranch turnout. Whatever had happened was
  240. 9:05upstream of my private irrigation
  241. 9:07system. I recorded the time and
  242. 9:09location, then continued toward the
  243. 9:11diversion. Nobody was there. The gate
  244. 9:14still sat in the position the contractor
  245. 9:16had left it. The northern branch carried
  246. 9:19visibly more water than mine, but I did
  247. 9:21not stand there documenting the same
  248. 9:23scene again. I already had that.
  249. 9:26Instead, I looked at where the northern
  250. 9:28channel went. The ditch followed the
  251. 9:30edge of the Fair Haven Crossing
  252. 9:32development before disappearing behind
  253. 9:34landscaped BMS and a row of trees. I had
  254. 9:37always known that branch served the
  255. 9:39subdivision area. I had never needed to
  256. 9:42care exactly how. Now I did. I drove to
  257. 9:45a public road crossing farther north
  258. 9:47where the channel passed through a
  259. 9:49culvert. Water moved strongly beneath
  260. 9:51the road. On the other side, the branch
  261. 9:54continued toward Fair Haven Crossing.
  262. 9:57For the first time, I could physically
  263. 9:59follow the route instead of simply
  264. 10:00looking at two water levels and assuming
  265. 10:03they were related. The discovery did not
  266. 10:05prove anyone had taken my allocation. It
  267. 10:08did establish that the same control
  268. 10:10point I had watched being adjusted could
  269. 10:12reduce the branch toward my ranch while
  270. 10:14feeding the channel that continued
  271. 10:16north. That was a much better question
  272. 10:18to carry into the next stage. When I
  273. 10:21returned home, I stopped trying to
  274. 10:23estimate what the pasture might lose. It
  275. 10:26was too early for that. I concentrated
  276. 10:28on preserving the timeline instead. My
  277. 10:31scheduled delivery was active when the
  278. 10:33gate changed. The reduced flow was
  279. 10:35measurable upstream of my ranch. The
  280. 10:37northern branch remained strong after
  281. 10:39the adjustment. The control point had a
  282. 10:42ditch company asset number attached to
  283. 10:44it. Those facts were enough. I spent the
  284. 10:47rest of the afternoon moving cattle and
  285. 10:49changing my pasture plan around the
  286. 10:50water I actually had rather than the
  287. 10:53water I had expected. That practical
  288. 10:56adjustment bothered me more than Clare's
  289. 10:58reaction at the gate. I could handle
  290. 11:00somebody being irritated that I
  291. 11:01photographed a contractor. What I could
  292. 11:04not absorb casually was losing part of a
  293. 11:07scheduled irrigation run and
  294. 11:08reorganizing my ranch around a decision
  295. 11:11I had never authorized.
  296. 11:13By evening, the upper pasture was still
  297. 11:15holding. The winter feed acreage was
  298. 11:17still salvageable. But I had ruled out
  299. 11:20the explanation that worried me first.
  300. 11:22The failure was not inside my ranch. The
  301. 11:26weak flow already existed before the
  302. 11:28water reached my turnout, and the ditch
  303. 11:30carrying the stronger share continued
  304. 11:32north toward Fair Haven Crossing. The
  305. 11:34next useful discovery came from
  306. 11:36following the water instead of watching
  307. 11:38the grass. The branch toward Fair Haven
  308. 11:41Crossing disappeared behind landscaping
  309. 11:43near the subdivision, but it did not
  310. 11:45vanish underground for long. A public
  311. 11:48road curved along the southern
  312. 11:49perimeter, and from there I could see
  313. 11:51where the ditch crossed beneath the
  314. 11:53pavement and reappeared near the HOA
  315. 11:55common area. I drove the route slowly.
  316. 11:59The channel passed behind a line of
  317. 12:00ornamental trees, crossed another
  318. 12:03service road, and eventually fed a
  319. 12:05concrete inlet structure near the
  320. 12:07southern end of the decorative lake.
  321. 12:10That was the physical connection I had
  322. 12:12been missing. The branch controlled by
  323. 12:15the diversion gate did not merely run
  324. 12:16somewhere in the direction of Fair Haven
  325. 12:18Crossing. It reached the lake. Fresh
  326. 12:21water was entering when I arrived. The
  327. 12:24lake itself looked unusually high for
  328. 12:26that point in the dry season. A row of
  329. 12:29pale shoreline rocks gave me a rough
  330. 12:31visual reference, but I did not spend
  331. 12:33the afternoon photographing them from
  332. 12:35every angle. I already knew what the
  333. 12:37bigger discovery was. I could trace the
  334. 12:40water from the diversion structure to
  335. 12:41the HOA inlet. Now the investigation had
  336. 12:44a route. A property management vehicle
  337. 12:47was parked near the common area service
  338. 12:49lane. Two workers were checking the
  339. 12:51shoreline equipment while Clare Voss
  340. 12:53stood near the inlet with a black
  341. 12:55folder. Her red blazer made her easy to
  342. 12:58identify from the public side of the
  343. 12:59road. I took one wide photograph that
  344. 13:02captured the inlet, the lake, and the
  345. 13:04maintenance activity. Then I put the
  346. 13:06phone away. Watching the lake rise was
  347. 13:09not going to tell me who had authority
  348. 13:11to change the gate. I needed to
  349. 13:13understand why the HOA had been working
  350. 13:15on the water system at the exact time my
  351. 13:17delivery weakened. A little later,
  352. 13:20another maintenance truck arrived
  353. 13:21carrying equipment used around the lake
  354. 13:23edge. The crew inspected the inlet
  355. 13:26structure and a line running toward the
  356. 13:28landscaped common area. Nothing about
  357. 13:30the scene looked like an emergency.
  358. 13:33There was no broken pipe flooding the
  359. 13:34road, no damaged bank, and no visible
  360. 13:37condition that would explain an urgent
  361. 13:39need to override another irrigation
  362. 13:41customer. That did not mean no
  363. 13:43legitimate maintenance issue existed. It
  364. 13:46meant the physical scene was not going
  365. 13:48to answer the authorization question for
  366. 13:50me. I left Fair Haven Crossing and drove
  367. 13:53directly back to the upstream control
  368. 13:55point. The hardware had not moved again.
  369. 13:58More importantly, the identification
  370. 14:00plate was still clear enough to read
  371. 14:02from the ditch bank. I copied the asset
  372. 14:04number into my notebook. That number
  373. 14:06gave me a way to stop thinking in terms
  374. 14:08of my ranch versus their lake. The ditch
  375. 14:11company would not organize its records
  376. 14:13around either of those descriptions. It
  377. 14:15would organize them around accounts,
  378. 14:17turnouts, control points, and delivery
  379. 14:19windows. That was the language I needed.
  380. 14:23Before contacting the company, I checked
  381. 14:25one more thing. I drove to another
  382. 14:28public crossing farther downstream on
  383. 14:30the ranch branch. The flow there was
  384. 14:32weak, too. That confirmed the same
  385. 14:35shortage at a second point outside my
  386. 14:37property. It also meant I could stop
  387. 14:39revisiting the pasture every few hours,
  388. 14:42looking for dramatic deterioration. The
  389. 14:44pasture would show consequences later.
  390. 14:47The water system was showing the cause.
  391. 14:49Now, back home, I laid out only the
  392. 14:52information that advanced the problem.
  393. 14:54My delivery schedule established when my
  394. 14:56account should have been receiving
  395. 14:58water. The upstream observations showed
  396. 15:00the shortage existed before the ranch
  397. 15:02turnout. The diversion structure showed
  398. 15:05where the flow could be split. Following
  399. 15:07the northern branch showed that it
  400. 15:09reached the Fair Haven Crossing Lake,
  401. 15:11and the asset number identified the
  402. 15:13exact control point where the change had
  403. 15:15occurred. The sequence was finally
  404. 15:18specific enough to investigate. I did
  405. 15:20not need another image of Clare. I did
  406. 15:23not need another photograph of grass
  407. 15:25losing color. I needed to know whether
  408. 15:27the ditch company had ordered the gate
  409. 15:29adjustment, whether someone outside the
  410. 15:31company had requested it, and what
  411. 15:33account was active when the hardware
  412. 15:35moved. The next morning, the water at my
  413. 15:38ranch had improved slightly. Not enough
  414. 15:40to recover the lost portion of the
  415. 15:42delivery, but enough that I could keep
  416. 15:44the immediate pasture problem under
  417. 15:46control. That gave me room to focus on
  418. 15:48the records. I gathered my account
  419. 15:51number, delivery schedule, turnout
  420. 15:53identifier, and the gate asset code.
  421. 15:56Then I added the time of the contractor
  422. 15:58adjustment from my phone metadata. Those
  423. 16:01were the details that could be checked
  424. 16:02against an operating system. As I drove
  425. 16:05toward the ditch company office, Fair
  426. 16:07Haven Crossing disappeared behind me.
  427. 16:10For 3 days, the dispute had looked like
  428. 16:12a rancher watching his pasture dry while
  429. 16:14a subdivision kept a lake full. That was
  430. 16:17no longer the useful version of the
  431. 16:19story. The useful version had a control
  432. 16:21point. It had an asset number. It had an
  433. 16:25active delivery window. And somebody had
  434. 16:28changed that gate while my water was
  435. 16:30supposed to be moving toward the ranch.
  436. 16:32The ditch company office did not look
  437. 16:34like the place where a property dispute
  438. 16:36would turn. It looked like every small
  439. 16:38irrigation office I had dealt with for
  440. 16:40years. a gravel lot, a low metal
  441. 16:43building, maps on the wall, schedules
  442. 16:46taped near a dispatch desk, a dry erase
  443. 16:49board covered with turnout numbers,
  444. 16:51delivery windows, and field notes. That
  445. 16:54ordinary setting was exactly what I
  446. 16:56needed. I brought the folder with my
  447. 16:58account number, the turnout ID, the
  448. 17:00photographs, and the delivery schedule.
  449. 17:03The first thing I wanted to establish
  450. 17:04was simple. Had my water delivery been
  451. 17:07changed by the company? My account
  452. 17:09showed the same window I had been
  453. 17:11working from. No cancellation, no
  454. 17:14emergency interruption, no scheduled
  455. 17:17maintenance block, no notation showing
  456. 17:19that my delivery had been voluntarily
  457. 17:21transferred or postponed. That
  458. 17:23eliminated one explanation.
  459. 17:26The next step was tracing the turnout.
  460. 17:28The asset code on the metal plate
  461. 17:30matched a control point in the company's
  462. 17:32network. That control point split flow
  463. 17:35between the lateral serving my ranch and
  464. 17:37a branch running toward the Fair Haven
  465. 17:39crossing area. The map itself did not
  466. 17:42accuse anyone of anything. It simply
  467. 17:44showed where the water could go. I
  468. 17:47compared that map with the photographs
  469. 17:48from the first afternoon. The location
  470. 17:51matched. The gate I had photographed was
  471. 17:54the correct control point. Then I
  472. 17:56started looking at the operational
  473. 17:58entries tied to that asset. The company
  474. 18:01tracked adjustments because different
  475. 18:03accounts received water at different
  476. 18:04times. Field personnel needed to know
  477. 18:07when gates were opened, reduced, reset,
  478. 18:10or checked. I did not receive the full
  479. 18:13history all at once. At first, I saw
  480. 18:16only enough to confirm that the gate had
  481. 18:18not remained in its normal scheduled
  482. 18:19position. An adjustment had been entered
  483. 18:22during my delivery window, then another.
  484. 18:25The timing stopped me. The first entry
  485. 18:28landed close to the period when I had
  486. 18:30noticed the ranch flow weakening. A
  487. 18:32later entry fell near the time I
  488. 18:34photographed the stronger current moving
  489. 18:36toward Fair Haven Crossing. That did not
  490. 18:39yet tell me who requested the change. It
  491. 18:41did not tell me how much water had been
  492. 18:43redirected, but it proved something I
  493. 18:46had not been able to establish from the
  494. 18:47field alone. The gate had been
  495. 18:50intentionally moved. I wrote the times
  496. 18:52down. Then I compared them with the
  497. 18:54metadata from my phone.
  498. 18:56The first photograph of Clare and the
  499. 18:58contractor beside the diversion
  500. 19:00structure had been taken shortly after
  501. 19:02one of the recorded adjustments. My
  502. 19:04turnout measurement came later. The lake
  503. 19:06photograph came after that. The sequence
  504. 19:09tightened. What had looked like separate
  505. 19:12observations now began fitting around
  506. 19:14specific operational events. I asked
  507. 19:17myself whether that could still be
  508. 19:18routine system balancing. It could, at
  509. 19:22least in theory. That was why I kept
  510. 19:25going. The ditch company also tracked
  511. 19:27which account was supposed to be
  512. 19:29receiving water during each delivery
  513. 19:31period. My account remained active
  514. 19:33through the same hours. There was no
  515. 19:35notation showing that my allocation had
  516. 19:38ended before the gate was changed. That
  517. 19:41mattered more than the appearance of the
  518. 19:42lake. The schedule and the adjustment
  519. 19:45record were now overlapping. Water
  520. 19:47assigned to my account was still in its
  521. 19:49delivery window when the control point
  522. 19:51changed. I went back through the
  523. 19:54previous week's entries to understand
  524. 19:56what normal looked like. The pattern was
  525. 19:58different. During ordinary deliveries,
  526. 20:01the gate changed when one account ended
  527. 20:03and another began. The timing followed
  528. 20:06the schedule. The entries I was looking
  529. 20:08at did not fit that pattern as neatly.
  530. 20:10They sat inside my active window. That
  531. 20:13was the first part of the company record
  532. 20:15that made me uncomfortable in a way the
  533. 20:17photographs had not. A photograph can
  534. 20:19capture a moment. An operating schedule
  535. 20:22shows what should have been happening at
  536. 20:24that moment. I returned to the ranch
  537. 20:26that afternoon and checked the turnout
  538. 20:28again. The flow had improved slightly,
  539. 20:30but not enough to make up for the
  540. 20:32earlier shortage. The upper pasture had
  541. 20:35lost more color. The winter feed acreage
  542. 20:38was showing visible stress across a
  543. 20:39wider section. I photographed those
  544. 20:42areas from the same marked positions.
  545. 20:44That gave me a third day of comparison.
  546. 20:47I was starting to see the economic side
  547. 20:49of the problem taking shape. If the
  548. 20:52water returned immediately, I might lose
  549. 20:54growth. If the delivery remained short,
  550. 20:57I could lose part of a cutting. The
  551. 20:59damage was still developing. The record
  552. 21:02trail was developing faster. Later that
  553. 21:04day, I drove past Fair Haven Crossing
  554. 21:07again. Clare was near the lake with two
  555. 21:09people I had not seen before. One wore a
  556. 21:12property management badge. The other
  557. 21:14carried rolled site drawings.
  558. 21:16Clare still wore red. This time the
  559. 21:19blazer was easy to spot from the road.
  560. 21:21Even though she stayed well inside the
  561. 21:23HOA common area, nobody was working at
  562. 21:26the diversion gate. Nobody was moving
  563. 21:29equipment. The tension had shifted.
  564. 21:32The problem was no longer happening only
  565. 21:34beside the ditch. It had entered
  566. 21:36offices, account records, and
  567. 21:38maintenance files. I did not approach
  568. 21:41them. I took one wide photograph showing
  569. 21:44the lake and the active inlet. Then I
  570. 21:47left. That evening, I rebuilt the
  571. 21:50timeline on paper. My irrigation
  572. 21:52delivery started. The gate was adjusted.
  573. 21:55My turnout flow dropped. The HOA side
  574. 21:58branch strengthened. The lake rose. The
  575. 22:01company recorded another adjustment.
  576. 22:04My delivery window remained active. The
  577. 22:07pieces were no longer floating
  578. 22:09separately. They were beginning to form
  579. 22:11one continuous sequence, but there was
  580. 22:14still a missing line. The operational
  581. 22:16entries showed when the gate moved. They
  582. 22:19did not yet tell me what direction each
  583. 22:21adjustment represented in measurable
  584. 22:23terms, who authorized it, or whether the
  585. 22:25Fair Haven crossing branch received more
  586. 22:27flow as a result. For that, I needed the
  587. 22:30more detailed gate history, not the
  588. 22:33schedule, not the summary entry, the
  589. 22:36actual control log, the one tied to the
  590. 22:38asset number. I had photographed on the
  591. 22:40first afternoon. That was the record
  592. 22:43that could turn a suspicious sequence
  593. 22:44into something much harder to explain
  594. 22:46away. The detailed gate log changed the
  595. 22:49dispute from suspicion into sequence. It
  596. 22:52was tied to the same asset number I had
  597. 22:54photographed on the diversion structure,
  598. 22:56and unlike the short operational
  599. 22:58summary, it showed each recorded
  600. 23:00adjustment in order. The first entry
  601. 23:03fell inside my irrigation window. The
  602. 23:05gate had been moved away from the
  603. 23:07position that normally supported my
  604. 23:09delivery. The second entry showed
  605. 23:11another change less than an hour later.
  606. 23:14That adjustment increased flow toward
  607. 23:15the Fair Haven crossing branch. I read
  608. 23:18the times again. Then I pulled up the
  609. 23:21photographs from my phone. Clare and the
  610. 23:23contractor had been standing beside the
  611. 23:25gate during that same period. The photo
  612. 23:28metadata did not match the log to the
  613. 23:30exact second, but it did not need to.
  614. 23:33The sequence was close enough to connect
  615. 23:35what I had seen to what the operating
  616. 23:37record showed. A contractor was
  617. 23:39physically adjusting the gate. The
  618. 23:41company log recorded an adjustment at
  619. 23:43that control point. My ranch flow
  620. 23:46dropped afterward. The HOA side branch
  621. 23:49strengthened. The lake rose for the
  622. 23:52first time. All of those pieces belong
  623. 23:54to the same timeline. The log contained
  624. 23:57more than timestamps. Each adjustment
  625. 24:00entry included a field note indicating
  626. 24:02the direction of the change. One entry
  627. 24:05reduced the opening serving my lateral.
  628. 24:07Another increased the setting on the
  629. 24:09branch feeding toward Fair Haven
  630. 24:10crossing. That was the part I had been
  631. 24:13waiting for. The issue was no longer
  632. 24:15whether someone had touched the gate.
  633. 24:17The record showed what the adjustment
  634. 24:19did. I compared those settings with
  635. 24:21prior delivery cycles. During normal
  636. 24:24operation, my account received a
  637. 24:26stronger opening through most of its
  638. 24:28scheduled window. The branch toward Fair
  639. 24:31Haven Crossing was not supposed to
  640. 24:32receive that kind of increased flow. At
  641. 24:35the same time, the current cycle was
  642. 24:37different. My opening had been reduced
  643. 24:40before my delivery period ended. The
  644. 24:42northern branch had been increased.
  645. 24:45The timing lined up with the photographs
  646. 24:47of Clare, the contractor, and the rising
  647. 24:49lake. I still did not assume that meant
  648. 24:52Clare personally controlled the ditch
  649. 24:54company. She did not. The gate log
  650. 24:57described operation, not motive.
  651. 25:00So I looked for the request trail. The
  652. 25:02company kept notes when outside parties
  653. 25:04asked for adjustments related to
  654. 25:06maintenance, access, or shared
  655. 25:08infrastructure. One entry referenced a
  656. 25:10service request connected to Fair Haven
  657. 25:12Crossing. The request was logged shortly
  658. 25:15before the first adjustment. It
  659. 25:17described a lake level maintenance
  660. 25:19concern near the subdivision's common
  661. 25:21area. That wording mattered. It
  662. 25:24connected the HOA's concern about its
  663. 25:26lake to the exact control point that
  664. 25:29governed part of my scheduled delivery.
  665. 25:31The contractor had not simply wandered
  666. 25:33to the wrong gate. Someone had asked for
  667. 25:36an adjustment associated with Fair Haven
  668. 25:38Crossing. The gate had then been moved.
  669. 25:42The branch toward the lake received more
  670. 25:44flow. My ranch received less. The
  671. 25:47company record did not show any
  672. 25:49corresponding notation authorizing a
  673. 25:51reduction to my irrigation account. That
  674. 25:54gap was important. The system showed a
  675. 25:56reason for increasing water toward the
  676. 25:58HOA. It did not show a reason for taking
  677. 26:01water away from me during my active
  678. 26:03window. I placed the service request
  679. 26:05beside the delivery schedule. The timing
  680. 26:08over overlapped. Then I placed both
  681. 26:10beside my first turnout reading. The
  682. 26:12reduction at the ranch followed the gate
  683. 26:14change. By then, the evidence had
  684. 26:17stopped depending on how full the HOA
  685. 26:19lake looked. The lake was still useful
  686. 26:21visually, but the gate log was stronger.
  687. 26:24It showed control. It showed timing and
  688. 26:28it showed direction. I returned to the
  689. 26:31field that afternoon with a copy of the
  690. 26:33relevant entries. The pasture stress had
  691. 26:35become easier to see from a distance.
  692. 26:38The higher section of grass had dulled
  693. 26:40further. The winter feed acorage still
  694. 26:42had recoverable growth, but the mist
  695. 26:45water had already affected how evenly
  696. 26:47the field was holding color. I
  697. 26:49photographed the same marked positions
  698. 26:51again. Those images would matter later
  699. 26:53when I had to calculate loss. For now,
  700. 26:56the more important change was
  701. 26:58institutional. The ditch company had
  702. 27:00begun reviewing who had requested the
  703. 27:02Fair Haven crossing adjustment and what
  704. 27:04authorization had been checked before
  705. 27:06the gate was moved. That was the first
  706. 27:09sign that the issue was no longer being
  707. 27:11treated as a minor field complaint.
  708. 27:14Clare appeared again near the HOA lake
  709. 27:17that evening. She stood beside the
  710. 27:19property management employee I had seen
  711. 27:21earlier, still in the crimson red
  712. 27:23blazer, but the scene was quieter than
  713. 27:25before. No contractor was touching the
  714. 27:28diversion hardware. No one was directing
  715. 27:31water. The inlet into the lake had
  716. 27:33slowed. I photographed the shoreline
  717. 27:35from the same roadside point. The water
  718. 27:38was no longer climbing at the rate I had
  719. 27:40seen during my delivery window. That
  720. 27:43image did not prove the cause by itself.
  721. 27:45The log already did more than the
  722. 27:47photograph ever could. The strongest
  723. 27:49part of the record was that it existed
  724. 27:51independently of my interpretation. The
  725. 27:54company needed those entries to operate
  726. 27:56the ditch. The timestamps, asset code,
  727. 27:59adjustment direction, and service
  728. 28:01request all existed because the system
  729. 28:03had to track where water was being sent.
  730. 28:05When I lined everything up, the path was
  731. 28:08clear enough to follow. My account was
  732. 28:10active. A Fair Haven crossing service
  733. 28:13request was entered. The gate was
  734. 28:15adjusted. My lateral was reduced. The
  735. 28:18HOA side branch was increased. My ranch
  736. 28:21flow dropped. The lake rose.
  737. 28:25That was the evidence payoff I had been
  738. 28:27looking for from the beginning. But it
  739. 28:29still left one question unresolved. Fair
  740. 28:32Haven Crossing had a lake. It had
  741. 28:34landscaping. It had a maintenance
  742. 28:37concern. None of that answered whether
  743. 28:39the HOA had any right to use water that
  744. 28:42was already scheduled to my ranch
  745. 28:44account. The gate log showed what
  746. 28:46happened. The allocation records would
  747. 28:48have to show whether they had any
  748. 28:49authority to do it. The allocation
  749. 28:52records answered the question the gate
  750. 28:53log could not. The HOA owned the lake.
  751. 28:57It did not own my irrigation delivery.
  752. 29:00That difference sat at the center of
  753. 29:02everything. The ditch company's account
  754. 29:04records showed my ranch as the active
  755. 29:06delivery account for the window when the
  756. 29:08gate had been changed. The turnout
  757. 29:10serving my property was tied to that
  758. 29:12account and the scheduled volume had
  759. 29:14been assigned before Claire's service
  760. 29:16request ever appeared in the system.
  761. 29:18Fair Haven Crossing had its own water
  762. 29:20related maintenance needs. It had
  763. 29:22landscaping. It had a decorative lake.
  764. 29:26It had infrastructure connected to the
  765. 29:28same broader ditch network. What it did
  766. 29:30not have was a record transferring my
  767. 29:32scheduled allocation into its control. I
  768. 29:36went through the account history
  769. 29:37carefully. There was no approved
  770. 29:39exchange, no temporary assignment, no
  771. 29:42written transfer, no emergency override
  772. 29:45giving the HOA priority over my ranch
  773. 29:48delivery. The records did not show any
  774. 29:50arrangement allowing Fair Haven Crossing
  775. 29:52to take water from my active window
  776. 29:55simply because the lake level was low.
  777. 29:57That was the legal reality I had been
  778. 29:59looking for. Owning the receiving pond
  779. 30:01did not create a right to whatever water
  780. 30:03could be made to flow into it. The water
  781. 30:06moving through the ditch system was
  782. 30:07tracked by delivery account and
  783. 30:09allocation. During those hours, that
  784. 30:12account was mine. The distinction became
  785. 30:14even clearer when I compared the
  786. 30:16delivery map with the HOA property map.
  787. 30:19Fair Haven Crossings common area sat
  788. 30:21north of the diversion point. My ranch
  789. 30:24turnout sat on a separate branch. The
  790. 30:26system served both areas, but the
  791. 30:28branches were not interchangeable just
  792. 30:30because they shared infrastructure
  793. 30:32upstream. That mattered because Clare's
  794. 30:34position had always rested on the
  795. 30:36practical fact that the HOA maintained
  796. 30:38the lake. The allocation records dealt
  797. 30:41with a different question. Who had the
  798. 30:43right to receive the scheduled water at
  799. 30:45that time? The answer was much narrower,
  800. 30:48my ranch. I also checked whether the HOA
  801. 30:52had any standing agreement with the
  802. 30:53ditch company that could complicate the
  803. 30:55issue. There were records for normal
  804. 30:57lake maintenance deliveries and common
  805. 30:59area irrigation periods. Those
  806. 31:02deliveries had their own windows,
  807. 31:04their own entries, their own operating
  808. 31:07instructions. None of them overlapped
  809. 31:09with a general right to alter my
  810. 31:11allocation. That removed another
  811. 31:13possible explanation. The lake did have
  812. 31:16legitimate water access, just not
  813. 31:18through my active delivery. The service
  814. 31:21request tied to Fair Haven Crossing
  815. 31:23began to look different once placed
  816. 31:25beside those records. It had described a
  817. 31:28lake level concern. The contractor
  818. 31:30responded at the control point. The gate
  819. 31:33was moved. The HOA side branch
  820. 31:36increased. My lateral was reduced, but
  821. 31:39the request itself did not create the
  822. 31:41authority to reassign water already
  823. 31:43scheduled to another account. That was
  824. 31:46the central mistake.
  825. 31:48Someone treated a maintenance request as
  826. 31:50if it could override an allocation. The
  827. 31:52records did not support that. By then,
  828. 31:55the ditch company had also started
  829. 31:57reviewing its own internal process. The
  830. 31:59question was no longer limited to why
  831. 32:01the gate moved. It became how an outside
  832. 32:04maintenance request reached the point
  833. 32:06where a contractor could change a
  834. 32:08control setting without verifying the
  835. 32:10active account. That procedural failure
  836. 32:13mattered because it explained how the
  837. 32:15diversion became possible. It did not
  838. 32:18change who was supposed to receive the
  839. 32:19water. I went back to the ranch after
  840. 32:22reviewing the allocation file. The upper
  841. 32:25pasture had stabilized somewhat after
  842. 32:27flow was restored. The winter feed
  843. 32:29acreage was still uneven. Some sections
  844. 32:32had recovered color. Others had lost
  845. 32:35enough growth that I could see the
  846. 32:36difference from the fence line. I
  847. 32:38photographed the same marked positions
  848. 32:40again. The damage was no longer
  849. 32:42developing as quickly, but it was
  850. 32:44measurable. That was important for what
  851. 32:47came next. The property side of the
  852. 32:49dispute was mostly settled. The water
  853. 32:52had been assigned. The gate had been
  854. 32:54adjusted. The diversion had been logged.
  855. 32:57The HOA request had been identified. The
  856. 33:00delivery account showed who should have
  857. 33:02received the flow. What remained was
  858. 33:04value. How much production had I
  859. 33:06actually lost? How much could be
  860. 33:08supported by records instead of
  861. 33:10frustration. I went back through
  862. 33:12previous irrigation cycles and compared
  863. 33:14similar heat periods. The same pasture
  864. 33:17had held more growth when the full
  865. 33:19delivery arrived on time. The winter
  866. 33:21feed acreage had produced more
  867. 33:23consistently under normal watering. I
  868. 33:26was not interested in claiming every dry
  869. 33:28blade of grass as damage. that would
  870. 33:30weaken the case. I needed a reasonable
  871. 33:32estimate tied to the acreage and the
  872. 33:34missed delivery period. The ditch
  873. 33:37company records helped there, too.
  874. 33:39Because the active window and gate
  875. 33:41adjustments were documented, the
  876. 33:42shortage had a defined beginning and
  877. 33:44end. That gave me a time period to
  878. 33:47compare against crop and pasture
  879. 33:48performance. Clare appeared one more
  880. 33:51time near the lake before the allocation
  881. 33:53review was complete.
  882. 33:55She stood beside the property management
  883. 33:57employee, red blazer bright against the
  884. 33:59pale shoreline. This time there was no
  885. 34:02contractor at the gate. No wrench, no
  886. 34:05adjustment. The lake level was lower
  887. 34:08than it had been during my scheduled
  888. 34:09run. The HOA landscaping remained green,
  889. 34:13but the inlet was no longer pushing the
  890. 34:15same volume. I photographed the scene
  891. 34:18from the roadside. The image was less
  892. 34:20dramatic than the first one. That was
  893. 34:22fine. The important part was already in
  894. 34:25the records. The legal twist was not
  895. 34:27that Fair Haven Crossing had no right to
  896. 34:29any water. It did. The twist was that
  897. 34:32its legitimate water rights did not
  898. 34:34include mine. The HOA could maintain its
  899. 34:38lake with water allocated to its own
  900. 34:40account. It could not convert a
  901. 34:42maintenance concern into control over a
  902. 34:44delivery already assigned to my ranch.
  903. 34:46The gate log showed the diversion. The
  904. 34:49allocation records showed why it was
  905. 34:51unauthorized. Those two pieces finally
  906. 34:54answered both halves of the dispute.
  907. 34:56What happened and who had the right to
  908. 34:59the water? The only unresolved question
  909. 35:01was what the documented shortage had
  910. 35:03cost me. The final stage of the dispute
  911. 35:06was less dramatic than the first
  912. 35:07afternoon at the gate. It was also more
  913. 35:10important. By then the central questions
  914. 35:13had been answered. My irrigation account
  915. 35:15had been active. The diversion gate had
  916. 35:18been adjusted during that window. The
  917. 35:20branch toward Fair Haven Crossing had
  918. 35:22received more flow. My ranch delivery
  919. 35:25had been reduced. The gate log recorded
  920. 35:28the change. The allocation records
  921. 35:30showed that the water scheduled during
  922. 35:32those hours belonged to my delivery
  923. 35:34account. What remained was damage. I
  924. 35:38started with the pasture. The sections
  925. 35:40closest to the turnout had recovered
  926. 35:42reasonably well once normal flow
  927. 35:44returned. Farther west, the stress had
  928. 35:46lasted longer. The winter feed acreage
  929. 35:49showed the clearest difference. Growth
  930. 35:51was thinner and less even than
  931. 35:53comparable sections from previous
  932. 35:54irrigation cycles. I measured the
  933. 35:57affected acreage and compared it with my
  934. 35:59own production records. I did not use
  935. 36:01the highest yield from a good year. I
  936. 36:04used conservative numbers from recent
  937. 36:06comparable conditions. The goal was not
  938. 36:08to inflate the claim. It was to make the
  939. 36:11loss difficult to dismiss. The shortage
  940. 36:13had a documented start. The restoration
  941. 36:16had a documented time that gave me a
  942. 36:19defined period of reduced delivery. The
  943. 36:22field photographs showed how the pasture
  944. 36:24changed during that period. The
  945. 36:26historical records showed how the same
  946. 36:28acreage normally performed when it
  947. 36:30received the scheduled water. The ditch
  948. 36:33company's records filled in the
  949. 36:34operational gap between those two
  950. 36:36points. That made the damage calculation
  951. 36:38much cleaner. Fair Haven Crossings
  952. 36:41insurer became involved. The
  953. 36:43contractor's insurance representative
  954. 36:45did too. The ditch company reviewed its
  955. 36:48own role separately because the
  956. 36:50adjustment had occurred through
  957. 36:51infrastructure under its control. Nobody
  958. 36:54needed a dramatic confrontation by then.
  959. 36:56The records had narrowed the dispute too
  960. 36:58far. The HOA had made a service request.
  961. 37:02The gate had been changed. The scheduled
  962. 37:05allocation had not been transferred. My
  963. 37:08ranch had received less water. The
  964. 37:10pasture had suffered measurable loss.
  965. 37:12The final financial resolution covered
  966. 37:15the reasonable value of the documented
  967. 37:17agricultural damage and the additional
  968. 37:19costs tied directly to the interrupted
  969. 37:22irrigation cycle. There was no enormous
  970. 37:25settlement, no fantasy penalty, no
  971. 37:28sudden courtroom victory. I recovered
  972. 37:31what the records supported. That was
  973. 37:33enough. The procedural changes mattered
  974. 37:36more. The ditch company changed how
  975. 37:39outside maintenance requests were
  976. 37:40handled at shared control points. A
  977. 37:43contractor could no longer adjust a
  978. 37:45turnout simply because a nearby customer
  979. 37:47reported a maintenance need. The active
  980. 37:50delivery account had to be checked
  981. 37:52first. Any requested change that could
  982. 37:54affect another customer's scheduled
  983. 37:56water required direct verification
  984. 37:58before the hardware was moved. The
  985. 38:01control gate itself received a clearer
  986. 38:03operating tag tied to the account
  987. 38:05schedule. Access to the adjustment
  988. 38:07mechanism was restricted. The contractor
  989. 38:10also received a revised procedure for
  990. 38:12fair haven crossing. HOA staff could
  991. 38:15report lake level concerns. They could
  992. 38:17request legitimate water service. They
  993. 38:20could schedule maintenance through their
  994. 38:21own account. They could not direct a
  995. 38:24field contractor to alter a shared
  996. 38:26diversion point without the ditch
  997. 38:28company confirming the active delivery.
  998. 38:30That distinction was now written down.
  999. 38:33Clare remained president of Fair Haven
  1000. 38:35Crossing. I saw her several times after
  1001. 38:38the claim was resolved. The red blazer
  1002. 38:41was still easy to recognize, but I never
  1003. 38:43again saw her standing beside that gate
  1004. 38:45while someone adjusted it. That was the
  1005. 38:48change I cared about. The next
  1006. 38:50irrigation cycle arrived several weeks
  1007. 38:53later. I drove to the turnout before the
  1008. 38:55scheduled start. The gate position
  1009. 38:58matched the company's operating plan.
  1010. 39:00The control hardware was secured.
  1011. 39:03The identification plate was clean and
  1012. 39:05readable. When my delivery began, the
  1013. 39:07flow at the ranch turnout rose steadily.
  1014. 39:10I measured it at the same point I had
  1015. 39:12used during the dispute. This time, the
  1016. 39:14reading was where it should have been.
  1017. 39:17Water moved through the lateral and
  1018. 39:18spread across the pasture. The higher
  1019. 39:21ground darkened as moisture reached it.
  1020. 39:23The winter feed acreage took water
  1021. 39:25evenly. I drove past Fair Haven Crossing
  1022. 39:28later that afternoon. The decorative
  1023. 39:30lake sat lower than it had during my
  1024. 39:32stolen delivery window, but it was still
  1025. 39:35healthy. The landscaping around it
  1026. 39:37remained green. Nothing had collapsed.
  1027. 39:40Nothing had been ruined. The HOA simply
  1028. 39:43had to use the water available to its
  1029. 39:45own account. That was the quietest part
  1030. 39:47of the whole story. The conflict had
  1031. 39:50never required one side to lose
  1032. 39:52everything. It required the system to
  1033. 39:54stop treating my allocation as available
  1034. 39:56whenever somebody else wanted more. The
  1035. 39:59photographs from the first afternoon
  1036. 40:01remained in my phone. Clare beside the
  1037. 40:03gate, the contractor on the hardware,
  1038. 40:06the stronger flow moving north, my
  1039. 40:08reduced turnout, the rising lake. But
  1040. 40:12those images were not what finally
  1041. 40:13settled the matter. The gate logs showed
  1042. 40:16the adjustments. The allocation records
  1043. 40:19showed who was entitled to the delivery.
  1044. 40:21The field records showed what the
  1045. 40:23shortage cost. Together they turned a
  1046. 40:26suspicious drop in water into a
  1047. 40:27documented sequence. I had started with
  1048. 40:30one question. Why was my ranch running
  1049. 40:32dry while the HOA lake kept filling? The
  1050. 40:36answer turned out to be buried in
  1051. 40:37ordinary operating records. A gate had
  1052. 40:40been moved during my scheduled delivery.
  1053. 40:43The water had been redirected. And once
  1054. 40:45the ditch company's own log showed when
  1055. 40:47and how it happened, Fair Haven Crossing
  1056. 40:50could no longer treat the shortage as
  1057. 40:51just another summer irrigation

About this transcript

This page contains the full transcript of HOA Diverted My Irrigation Water to Their Lake — Then the Ditch Company’s Gate Logs Exposed It by HOA LAND WARS, generated from the public captions YouTube serves with the video. The transcript has 6,680 words across 1,057 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.