storm-capture register · bound register page

Track Nonpotable Storm Capture and Overflow into One Initially Empty Barrel

A full barrel cannot collect the next shower just because its brochure capacity looks generous. Carry remaining headroom from storm to storm and distinguish potential runoff, captured water and spill under a clearly stated no-draw-off scenario.

1 · Storm code | rainfall mm | contributing roof m² | modeled runoff fraction

FIRST-LOAD

HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.

Data note: The storm-capture register processes Storm code | rainfall mm | contributing roof m² | modeled runoff fraction locally. Starter/sample selection and Run compute in this tab; no input is sent by the calculator. A local draft may be saved; explicit state-link sharing or optional external AI formatting can disclose inputs. Use non-sensitive labels.

Perspective: Before: each shower seemed to reuse the whole barrel. After: sequential headroom separates potential runoff, captured volume and overflow.

2 · Read the storm-capture register

Nonpotable collection-volume scenario only, not water-quality, drainage-design or installation advice. Do not drink untreated roof runoff; ask a qualified installer about overflow routing, maintenance and local collection requirements.

Paid layer: storm-capture register filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one complete unwatermarked storm-capture register run in the app
three labeled samples and unlimited article-demo calculations
complete result text and a user-triggered input-state link

What $4 one-time adds

unlimited subsequent storm-capture register app calculations after a local convenience signal
print the storm-capture register with visible assumptions and its safety boundary
CSV of the displayed L modeled overflow and row workings; conditional estimate uses your manual-retyping minutes
five local reading summaries (headline/count/time), not saved full inputs or cross-device backups

HYPOTHESIS / PROTOTYPE: $4 is a proposed one-time price for filing the storm-capture register, not a current sales offer. No measured time saving or buyer demand is claimed. The optional manual-retyping baseline above estimates one export’s retyping budget only; it does not change the calculation or guarantee savings.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

Before using the storm-capture register

One millimeter of rainfall over one square meter corresponds geometrically to one liter before collection losses. Multiply that by an explicitly supplied runoff fraction from zero through one. Use contributing horizontal collection area under your chosen verified convention, not sloping roof surface area without checking its relationship to rainfall. Rows are storms in chronological order. The barrel begins empty, there is no draw-off, evaporation, leak, first-flush deduction or connection limit between rows, and usable capacity is the volume available to this model rather than necessarily the advertised container size. Water is treated as nonpotable. The calculation cannot determine contamination, mosquito protection, foundation drainage or whether a collection installation is permitted.

Boundary and sources

Method: Potential runoff is rainfall × area × fraction in liters. Captured volume is the smaller of that inflow and remaining capacity. Overflow is inflow minus captured volume. Reduce headroom by captured volume before processing the next row. The register keeps all three quantities so cumulative spill cannot be confused with total rainfall or available drinking supply.
All sample records, dates, quantities and labels are invented. No outside policy, contract, rate, clock offset, measurement or accessibility standard is represented as verified.
Google’s official pricing documentation, fetched 2026-10-01, says AI Studio is free in available regions. Optional formatting may require a Google account; manual local entry requires none. Limits can change and free-tier content may be used to improve products. Do not send private records.

Mechanism: competence-autonomy-loop

Optional AI formatting, never the calculation

Manual entry completes this storm-capture register for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.

Format only these fictional or non-sensitive notes for a storm-capture register. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string", "string"]}], "setting": "string"}. The columns are Storm code | rainfall mm | contributing roof m² | modeled runoff fraction; the setting is Usable barrel capacity (liters). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.

An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.