Lake Level, Groundwater, and Source Investigation: Measure, Test, and Hand Off

Build a term-and-uncertainty ledger for precipitation, evaporation, surface inflow and outflow, withdrawals and returns, managed operations, groundwater exchange, and storage change; record method, owner, units, coverage, sign, uncertainty, and review state.

Does the ledger keep a water-budget residual separate from groundwater exchange and from a contamination or nutrient source?

Create a decision-to-evidence matrix with competing hypotheses, spatial and temporal contrasts, methods, laboratory needs, detection and uncertainty limits, permissions, health escalation, reviewers, and explicit stopping points.

Could another qualified team reproduce the design without inventing a universal frequency, threshold, well specification, tracer quantity, pumping rule, treatment, or engineering design?

Build one synchronized evidence set with gage and benchmark lineage, well measuring points and screens, pumping context, head calculations, uncertainty, spatial support, water-budget links, and method-specific limitations; leave unsupported exchange and source fields unresolved.

Does the assessment show why one level pair, gradient, seepage result, temperature pattern, or tracer signal cannot prove persistent direction, whole-lake flux, or source?

Run a return demonstration containing a private-access mismatch, an unknown utility, a well-pit or confined-space request, contamination or decontamination failure, sensitive household information, and an unapproved intrusive or tracer task; retain prompts and scope limits.

Are demonstrated proficiency, owner consent, site access, permit or utility clearance, health authority, and authorization to sample or disturb represented as different decisions?

Map routine and event stations, discharge method, concentration timing, integration interval, ungaged areas, drains and returns, uncertainty, and missing surface-water terms for each candidate pathway.

Are concentration and load kept distinct, with missing or uncertain surface-water terms still visible rather than transferred to groundwater or a named source?

Trace one lake sample and one consented well sample through plan, container identity, collection, processing, custody, receipt, analysis, QC, validation, health handoff, privacy review, release, and amendment without overwriting an earlier state.

Do field evidence, laboratory acceptance, analytical reporting, validation, public-health interpretation, source attribution, and release remain separately attributable?

Complete a tabletop record with a datum conflict, pumping-affected well, unresolved budget residual, one non-detection, competing shoreline and septic hypotheses, restricted household and infrastructure details, an authority handoff, and no mitigation authorization.

Do private-well, septic, household, health, cultural, threatened-resource, access, and security-sensitive data remain restricted while all thirteen governed record states retain separate owners and evidence?

Create an alternatives and authority table with mechanism, evidence need, uncertainty, exposure control, owner, health and regulatory handoff, consent, consultation, permits, engineering dependency, adverse outcomes, monitoring, and explicit rejection reasons, without selecting or designing a remedy.

Are mitigation or funding eligibility and authorization separate, with no universal engineering, remediation, treatment, pumping, septic, well, tracer, or lake-level prescription?

For a hypothetical authorized action, define as-approved and as-performed evidence, baseline and comparison, hydrologic and water-quality endpoints, health-authority boundaries, confounders, adverse and non-target outcomes, uncertainty, review timing, and decision owners.

Could the plan distinguish implementation failure, no hydrologic effect, no water-quality effect, health uncertainty, harm, mixed response, and an inconclusive result rather than forcing success?

Prepare a restricted review package and a generalized public version that retain raw evidence, corrections, hypotheses, contradictions, authority records, approval and implementation differences, outcome uncertainty, prior versions, and a correction path.

Does publication protect private health and exact-location information while preserving uncertainty and never upgrading evidence, source, cause, safety, compliance, authorization, or effectiveness?