The rule still prints $500 a day.

The river, right now

Read from the USGS OGC API by this service and classified against the minimum in force for today's date. Not a number anybody typed. If a gage cannot be read this says so and shows nothing, because a river reporting no data is not a river running at zero.

The season so far

Every 15 minute reading USGS published for this gage over the window, with the minimum in force drawn as it actually behaves. The rule STEPS on the days the schedule changes. A reading within 10 cfs of the minimum ON EITHER SIDE is treated as near-threshold and points at field verification rather than an order; the shaded band marks the 10 cfs above the line, because below it the reading is already below the minimum and the chart says that by position.

Where the curtailed rights divert

Points of diversion from the Board's own CalWATRS layer, joined to the rights named in the operative order's Attachment A. Owner names are not requested and are not held. The compliance gage is drawn as a triangle.

Every right the order names

Five years of curtailment administration

What the Board decided, beside what this engine computes

Classify a gage reading

Allocation Core, on the Board's own rights table

The same recommendation, spoken

Chirp 3 HD reads the recommendation aloud. The words are composed from what the Allocation Core computed, never from anything a caller types, and the transcript is printed below because a spoken claim that cannot be read back cannot be checked. The reason for a second channel is in this project's own evidence: reviewers of machine drafts submitted 35 to 45 percent of the erroneous ones entirely unedited, and hearing a figure is a different act from seeing it.

Ask the corpus a question

Five years of Board orders and addenda, searched by meaning rather than by keyword with gemini-embedding-001. "When was curtailment lifted because the measurement itself turned out to be wrong" shares no words with the addendum that answers it. Every response counts what was searched and names what could not be. The rights tables inside these documents are parsed exactly elsewhere in this system and are deliberately not indexed here, along with every owner name.

One traversal of the agent fleet

Every other control on this page calls a domain function directly. This one runs the ADK graph itself, Gage Sentinel to Allocation Core to Order Scribe to Herald, and reports which member produced each part. The node names below are read from ADK's own attribution rather than from the order the answers arrived in, because a retried node emits twice and position would then credit the wrong member.

Approval queue, signed by a named officer

What this is showing

The default is the reading behind Scott Addendum 7: 48.7 cfs on 20 July 2025, against a 50 cfs July minimum at Fort Jones. The flow schedule is bounded by date PERIOD rather than by month, so Scott changes on 24 June and Shasta on 25 March and 16 September. Ask for a 2021 Shasta date and it refuses, because that era's table has not been verified against a primary source and answering from the readopted one would mark the Board wrong for following the rule that was actually in force.

The reading you type is labelled unsourced: this console classifies a value you supply and never contacts USGS.

The signature is the beat the rest exists for. 23 CCR 875(b) assigns the determination to the Deputy Director and 875(b)(2) assigns health, safety and livestock determinations to the Executive Director, so the wrong officer's signature is not a lesser signature, it is none. An approval is bound to the exact bytes reviewed: the digest travels out with the draft and must come back with the decision, which is what makes a stale draft impossible to sign by accident. A draft that failed its guards is queued as UNVERIFIED and can still be signed, but only by naming every finding being overridden, because 875(b)(3) preserves that discretion and a signature against findings nobody saw is not an exercise of it. The queue lives in the serving process and says so: no database is wired.

The ledger is the artifact that makes a signed order reviewable: for any single right an official can follow why it landed where it did and under which subdivision. Deterministic facts and judgment inputs are shown apart on purpose. 23 CCR 875(b) vests the determination in a named human official and 875(b)(3) preserves the discretion to decline, to narrow, or to suspend, so the second set is surfaced and never resolved here. The rights come from the Attachment to Addendum 6; the Scott table has not been ingested, so asking for Scott refuses rather than answering from an empty list.