Reported transfer filings
Captured, normalized, and ready for source review.
Water-market record surface
Water SignalsSouth Platte launch market
Water Signals turns scattered Colorado water-right records into a source-linked market surface for brokers, investors, and diligence teams tracking reported activity in the South Platte.
Live surface
Captured, normalized, and ready for source review.
Records that warrant deeper diligence from the original filing.
Every surface item preserves the public-record trail.
Identity fields, decreed uses, and flow/volume references are normalized from the reported source record before delivery.
The surface highlights source modification timing, district context, and record continuity so teams can decide what to review next.
Conflicting or incomplete fields are held in a review state instead of being presented with false confidence.
Access model
Firms are provisioned directly. Once invited, users enter by magic link and accept the current information-only terms before they can use the platform.
Basin Flow
A rolling view of reported South Platte activity with timing, geography, and identity cleaned into a single surface.
Source Trail
Every item remains anchored to the underlying public record so diligence starts from the filing, not from a summary.
Signal Discipline
Unclear records are labeled for review instead of being translated into confident market conclusions.
Surface architecture
The product is designed as a market-facing information layer: readable enough for quick scanning, disciplined enough to keep the source record at the center of every decision workflow.
Inside the feed
WDID, case numbers, structure references, county, and source timing aligned into one object.
Incomplete records are held in a review state instead of being converted into false certainty.
Daily alerts and weekly summaries preserve context while still staying readable on a trading or diligence cadence.
Legal frame
Governs permitted use, limitation of liability, verification duties, and account controls.
Explains the business contact data we collect and how it is used to operate the beta.
Explains that reported records are presented for review and do not replace source verification.
Sets expectations for a limited beta product, service changes, and support boundaries.