The problem
Cedar Lake research brings together dam records, agency correspondence, competing explanations and missing data. The public project separates regulatory questions from the question of how upstream structures affect lake inflow. Its purpose is to help readers follow the record without treating an unresolved explanation as an established result. [1]
The contribution
The work presented here is evidence organization and public communication. The published project credits evidence coordination to Dot Dominus, LLC. This case study describes that project’s documented method; it does not attribute every research, engineering or software task to Michael personally. [2]
How the record was organized
1. Give claims visible evidence labels
The site distinguishes verified, reported, disputed, unknown and requested information. Those labels describe the available support. The structure gives a reader a way to see where sources agree, where they conflict and where a specific record is still needed. [1]
2. Separate file counts from unique evidence
The OWRB production review’s “Archive control” section describes the August 31, 2026 response to Inquiry 3078: 103 PDFs, representing 86 unique files after duplicate control. Its September 3 review of Inquiry 3090 describes a separate 29-PDF response; all 29 matched files in the August 31 production. These response-specific file counts are not cumulative project record totals. They are published review findings, not counts recomputed for this portfolio. [2]
3. Make a negative finding reproducible
For the September 3 Inquiry 3090 response, the review describes extracted text and full-page OCR across 131 pages, checked against eleven requested Cedar Lake Dam (OK11073) record categories. It reports that responsive records were not located within that delivered set. The page count and categories belong to this response review, not the cumulative project inventory; the finding does not establish everything the agency holds. [2]
The result and its limits
The public artifact brings a structure register, chronology, records review and outstanding questions together. Its practical value is a navigable source trail. The record still does not quantify the upstream dams’ effect on lake inflow or establish legal liability. This is an ongoing information project, not an engineering certification or a claim that the dispute is resolved. [1] [2]
What this demonstrates
The transferable skill is turning a mixed document collection into questions a reader can investigate: identify the item, show its source, explain the check and keep the unanswered part visible. That same discipline is useful in support documentation and operational reviews.
Sources and scope
[1] Cedar Lake Evidence Project — public information architecture, evidence labels and open questions. Reviewed November 5, 2026.
[2] OWRB production review — see “Archive control” for the August 31 Inquiry 3078 file counts and the Inquiry 3090 review for the September 3 response, page count and eleven-category search scope. These historical response reviews are distinct from a cumulative project inventory and are not a fresh agency or document audit.