Impact is the umbrella for ALCUB3’s altruistic work: public-interest systems, field deployment, publication, and partner programs that people can inspect, question, and use. Water Pulse is one visible program surface inside the lane, not the definition of it.
Impact brings programs, methodology, publications, and partnerships into one mission-led public-interest lane so people can understand the work, inspect the method, and follow it as it grows.
The hub should let people enter through mission, evidence, field sensing, or partnership motion without confusing the lane. Water Pulse should stay visible here as one concrete program surface inside a broader public-interest architecture.
Start here if you want to understand how Impact defines public-interest work, evidence thresholds, caveats, and deployment discipline.
Field sensing, watch surfaces, and visible-change work that make the basin legible without pretending the observatory is the whole mission.
Use the partner surface when the work needs institutional alignment, implementation ownership, and a path from mission narrative to operating program.
One current public program surface. Use it when you want to see how the mission behaves as a real interface and not just an umbrella statement.
Impact needs concrete programs where the system becomes legible in public. Water Pulse is one of those visible surfaces right now. Keep it present, but subordinate it to the larger mission so the hub can expand into future public-interest programs without a rewrite.
The public-facing water surface. Use this when you want the concrete interface, not just the lane narrative.
The sensing and monitoring side of the current water program. This is where basin visibility, anomaly watching, and change detection become inspectable.
Impact needs a real records layer even before the first full publication cycle arrives. Use placeholder slates now so the hub already behaves like a living program, not a static campaign.
The framing essay for why Water Pulse matters, how it fits under Impact, and what the mission umbrella is supposed to hold beyond any one program.
Reserved for the first mission report: basin health snapshot, model confidence notes, and operating implications for public partners.
Reserved for the first inspectable methodology publication so the trust case is visible before the archive gets large.