Turntide Islands

What can maps tell us about drainage near a Duluth garden?

2026-09-28T00:00:00Z

This is an AI-prepared desktop source check for a community question about gardens, watersheds, and rainwater in Duluth. The provider offer request asks for a bounded, reproducible screening before anyone proposes a paid report. No garden organizer has agreed to a site study, and no provider has been selected.

One reproducible map check

The Duluth Community Garden Program's location page embeds a public KML map of garden markers. On 2026-09-28, its Chester Creek Community Garden marker was at longitude -92.0899378, latitude 46.807297. This is a map point supplied by the garden program, not a surveyed garden boundary or confirmation of current site operations.

An intersection query of that point against Minnesota DNR's catchment layer returned one feature: catchment 0204000, named “City of Duluth-Frontal Lake Superior,” with a ver_date value of 10/31/2023. The layer is DNR Watersheds - DNR Level 08 - All Catchments, originated by the Minnesota DNR Division of Ecological and Water Resources, Watershed Delineation Project; its published metadata gives publication date 11/01/2023 and attribution requirements. This locates the program's marker in a mapped broad catchment. It does not show which nearby surface, pipe, or roof drains toward the garden.

What a useful screening still needs

The City has a completed stormwater management plan covering watershed and sewershed characteristics. Its newer GIS service directory lists watershed, elevation, and storm-system folders, but unauthenticated queries to those folders returned Token Required on 2026-09-28. An older City utility map service responded publicly and lists storm-system layers; its currency, completeness, terms, and fitness for this question have not been established. A provider should verify accessible elevation and imagery, garden boundaries, storm infrastructure, local flow paths, and the City's relevant plan findings before interpreting upstream relationships.

A catchment intersection is not a surface-flow model, hydrologic review, water-volume estimate, or permission to redirect runoff. The actual drainage path, utilities, ownership, site conditions, and potential harm require appropriate field and professional review before any intervention is considered.

Evidence and next decision

Evidence state: conceived question with one reproducible public-data

intersection. No completed garden-scale simulation, human source review, field observation, trial, or witnessed adaptation outcome.

Work selection: offers are open

for a bounded feasibility slice. That request does not award work or authorize spending.

Public use: this record uses public source material and paraphrases the

question. It does not republish a member's Discord words or treat a Discord post as consent.

To improve it, join Turntide and bring a source or a general observation to #question-quarry. A steward must ask separately before publishing a member's words or a site-specific observation.

Turntide Islands work and products

2026-09-27T00:00:00Z

Turntide Islands is a community for responding to climate weirding through conversation, shared knowledge, and practical work. These paths have different statuses. Joining the community does not enroll anyone in a paid product or a future program.

Participate now

The active public doorway is the Turntide Islands Discord. New arrivals follow the established #dock welcome and #channel-visas role selection. Read how to join before entering. Members can discuss questions, sources, projects, and place-based observations. The community-programming intake invites proposals; a gathering is confirmed only when a human organizer schedules it in Discord Events.

Knowledge Vault

Turntide's Discord has Knowledge Vault spaces for serious threading, briefings, archival work, and receipts. The intended product is durable, source-grounded knowledge that people can find and reuse beyond a chat thread. The public record does not yet offer a browsable collection of admitted practice guides or a paid vault subscription. Ordinary Discord participation does not grant consent to republish a member's words. Bring a source or question to the community; any public rescue of conversation needs separate provenance and consent.

The first public practice question gives a source trail, an evidence state, and a way to contribute without treating a chat message as publication permission. It is an agent-prepared research note, not a completed local trial or a member contribution.

The Duluth garden drainage record checks one garden-program map point against a public watershed layer and names what that intersection cannot answer. A provider request is open for a bounded screening; no work has been awarded.

Signals and public publishing

The rain-garden record shows one working route for a relevant signal: a cited public source can frame a community question, then a reviewer can check its meaning and limits in the Knowledge Vault before the public record changes. It links NOAA precipitation frequency estimates as possible United States design context. No location-specific estimate or observed storm has been admitted for this question. General news intake does not substitute for local observations or a site protocol.

Published pages can be followed through the site's RSS feed, Atom feed, and JSON feed. These feeds carry public site pages, including the rain-garden record; they do not syndicate Discord conversation or license member contributions. A reader can follow the public work without joining a paid product.

Proof of Adaptation

Proof of Adaptation is a proposal to develop and test local practices with evidence that distinguishes an idea, simulation, field observation, and replication. There is no active field-trial or token program on this site. The proposal becomes a product only as real protocols, results, and governance decisions are admitted and published.

Tidepool

Tidepool is a related directed-yield pool being developed by Causeway Services. Its proposed membership and governance process is separate from the Turntide community. Its separate public status page records that the governing specifications remain drafts, the published roster and cycle lists are empty, and no public admission or routing action is available. Turntide membership is not Tidepool membership; this page does not solicit funds or admission requests.

Other proposed offerings

Community discussions and technical records also describe automated climate signal intake, locality answers, contributor knowledge markets, and union media placements. These are distinct proposals and experiments, not a single available bundle or the route used by the public practice record above. The settlement account explains why a proposal and an operating offer must be kept separate.

Where could a rain garden help, and what would we need to check?

2026-09-27T00:00:00Z

This is Turntide's first public, source-linked practice question. It was prepared by an AI assistant from the linked public sources, without copying member conversation. A human has not reviewed a site or agreed to a trial.

The question

Where does rain run off a roof or paved surface in your area, and could a rain garden safely receive some of it? A useful local answer needs to identify the runoff source, the receiving area, soil and drainage conditions, the route of overflow, nearby buildings and utilities, maintenance responsibility, and applicable local rules. Do not post an exact home address or another person's location to answer it.

What the sources support

The US Environmental Protection Agency's green infrastructure guide describes rain gardens as shallow planted areas that collect and filter stormwater runoff. Its rain garden resource index points to regional guides for siting, design, installation, and maintenance. EPA labels that resource index as general information that is no longer being updated, so a local guide and current local rules still need checking. Those sources support considering a rain garden as a stormwater practice. They do not establish that a particular property is suitable or that a Turntide installation has reduced flooding.

A measured result elsewhere

The US Geological Survey's Gary, Indiana study monitored a City Hall parking-area intervention before and after construction of a central rain garden over sandy soil during the spring, summer, and fall of 2016–18. USGS reports that the share of study-area precipitation discharged to the sewer fell from about 25 percent before construction to 2 percent after, an estimated 80.3 percent reduction in stormwater discharged to that sewer. The study measured that site and intervention; it does not predict the effect of a different garden, soil, or storm. In a separate USGS project account, green infrastructure over clay soils in Detroit showed little stormwater-volume reduction. These findings make soil and drainage conditions part of the local question. They are external field evidence, not a Turntide field outcome.

Rainfall evidence still needed

For a United States site, NOAA's Precipitation Frequency Data Server can provide Atlas 14 precipitation frequency estimates and uncertainty for a selected location. An estimate can help frame a design question; it is not a record of a storm at the site or proof that a proposed garden can safely receive runoff. A local answer still needs an observed drainage path, site conditions, an appropriate local design guide, and a human decision about any trial. No location has been selected and no rainfall estimate has been calculated for this Turntide question. Share only a broad locality in public Discord; discuss exact site details privately with a consenting organizer if a trial is proposed.

Evidence and outcome

Turntide evidence state: conceived, with external guidance and monitored

field evidence from other sites linked. No Turntide simulation, field trial, or independent replication is recorded.

Source check: the linked EPA, NOAA, and USGS pages were read on 2026-09-27.
Vault work: the source trail in `#receipts`,

rainfall-source update, USGS field-study receipt, and agent-prepared reading path in `#vault-briefings` link back to this record. Neither is a human review or a field result.

Community outcome: [the question was posted in #question-quarry on

2026-09-27](https://discord.com/channels/1184863861065658419/1396155279208484997/1553932671808307200). An invitation for a human source-review lead or gathering host was posted in #mainland. A source-review request in `#archive-desk` now has a specific USGS study-check follow-up, and observation invitation in `#garden-grove` now point to this record. No human source review, local answer, accepted host, or session is recorded here yet.

Field outcome: unknown. No before-and-after observation has been

submitted or witnessed.

Help improve this record

Join Turntide, choose Questions and research in Discord's onboarding, and complete the #dock welcome. Then bring a source or a general, non-identifying observation to #question-quarry. Say what you observed, what you infer, and what remains unknown. Mentioning the research bot sends that question to NVIDIA inference for a reply in Discord; ordinary posts are not sent there by this service. A source link can be evaluated without copying your words into this site. If your own words or field observation would be useful in a public revision, a steward must first ask what may be published, how you want to be credited, and whether a location should be generalized. Posting in Discord alone gives no publication permission. A proposed trial needs its own human organizer, site-specific protocol, and witnessed result before this record's evidence state can change.

Turntide Islands Events and Community Programming

2026-08-29T00:00:00Z

Turntide Islands welcomes practical questions, source checks, field observations, and human-hosted gatherings. Join the Discord and complete the established #dock welcome first. You can contribute asynchronously; a question or field note does not require a scheduled meeting.

Current knowledge work

The open rain-garden question in `#question-quarry` asks where runoff could safely go and what would need checking. Its public source and evidence record is still at the question stage. Bring a source or a general, non-identifying observation to that Discord thread. Say what you directly observed, what you infer, and what you do not know; a broad locality, date, and conditions can help when safe to share. Do not post an exact home address or another person's private details. You may also start a different practical question in #question-quarry or discuss gardening in the established #garden-grove topical channel. Choose Gardening and land care during Discord onboarding to enter it.

Stewards can link source trails in the Knowledge Vault's #receipts and bring material worth preserving to #archive-desk. A public revision that uses a member's words or observation requires a separate agreement on what may be published, credit, and location detail. Posting in Discord alone does not grant that permission. Zelo can prepare an AI reply when explicitly mentioned in #question-quarry; people decide what sources hold up and whether a finding or practice has actually been witnessed.

Propose a gathering

For a synchronous event, post in #mainland with:

the purpose and desired outcome;
two possible start windows and your timezone;
expected length and participation format;
accessibility needs or accommodations;
whether you are willing to host, co-host, or are requesting a host.

A human must accept responsibility before a meeting is scheduled. Discord's Events list is authoritative for confirmed date, time, voice channel, and RSVP state. Zelo may explain this process and route proposals, but does not volunteer, host, moderate, or send automatic reminders on a person's behalf.

What happens after

Confirmed gatherings receive a named human organizer, reviewed reminder plan, and closeout. A closeout can record what happened, unanswered questions, useful links, and whether anything should be rescued into the public knowledge record. Ordinary conversation is not automatically copied into an archive or analytics cohort.

Governance

2026-08-29T00:00:00Z

Turntide Islands describes governance as a set of accountable, typed records rather than a charter that can silently drift from practice. An office is a standing normative form, distinct from any current holder; admissions, recognition, and witnessed records determine what can be claimed about its operation.

A public distinction

The governance record makes a deliberate distinction between present facts and declared direction. A planned DAO, token, office, or market is not treated as already built merely because it is described. This is the same fail-closed discipline that guides the settlement's technical records.

Direction of travel

The public governance document proposes that influence over a future trial slate be connected to witnessed contribution rather than speculative purchase. It also requires a clear human boundary: an automated system may have a declared office and accountable scope, but it cannot stand in for a human member's care, consent, or responsibility.

For the practical context behind this direction, see Proof of Adaptation and the settlement.

Turntide Islands

2026-08-29T00:00:00Z

Turntide Islands is a public-facing record of a community building practical, local climate-adaptation knowledge. It treats a community as more than its chat surface: its durable work is a settlement of published records, explicit admissions, and accountable decisions.

The work begins with a simple problem: useful knowledge about adaptation is fragmented, hard to verify, and rarely funded. Turntide Islands is developing a way to collect, test, and share that knowledge without presenting future plans as present facts.

Join the conversation

The community meets on Discord. To meet people, ask a question, or follow the work as it develops, join Turntide Islands. This invitation leads to the community's #dock arrival channel.

New arrivals first read the established welcome in #dock and react with its designated emoji. That verification opens the next step: #channel-visas, where people can choose topical communities through the established emoji and self-assigned-role flow. #dock is an arrival surface, not a general project or discussion channel. Participation does not create a commercial obligation, and sharing a message is not consent to have it resold, profiled, or copied into an automatic cohort. The active social surface is for learning together; there is no public token sale, paid membership, or operating field-trial program being offered here.

Read how to join and what to expect.

The community-programming intake is open for gathering hosts, practical questions, member projects, and place-based field notes.

The first public practice question asks where a rain garden could help and what evidence a local answer would need. Its sources and unknowns are visible; it does not claim a Turntide field result.

Explore the work and products to see what is available now and what is still being developed, including the Knowledge Vault, Proof of Adaptation, and Tidepool.

What is here

The settlement explains the public account of how Turntide

Islands holds itself accountable.

Proof of Adaptation describes the proposed

evidence-and-work loop for local practice.

Events and community programming records active invitations and

distinguishes intake from confirmed human-hosted gatherings.

Governance distinguishes standing commitments from future

directions.

Work and products connects the community, its knowledge work,

and related offerings with their current status.

A source-linked practice question starts the

public knowledge record with an explicit evidence state.

Join Turntide Islands

2026-08-29T00:00:00Z

Turntide Islands meets in Discord. Start by joining the Turntide Islands server; the invitation opens at #dock, the community's arrival channel.

What to expect now

This is a community for practical, local climate-adaptation learning. You can read, introduce yourself, ask a question, share an observation, and help make useful knowledge easier to find and evaluate. In #dock, read the established welcome and react with its designated emoji. Once verified, use #channel-visas to choose topical communities through the existing emoji and self-assigned-role flow. This is an established community journey; it is not a generic bot template, and #dock is not a general discussion channel. Discord's onboarding offers Questions and research, which opens #question-quarry for practical questions and source review, and Gardening and land care, which opens #garden-grove for garden observations and land questions. You can choose both. If you explicitly mention the research bot there, your question goes to NVIDIA inference for a reply in Discord. The channel notice explains that boundary. Ordinary discussion does not enter that reply flow.

The current experience is a social and learning space. Public participation is not enrollment in a paid program, a token offer, a commercial contract, or a promise of access to future work. Proposed governance, proof-of-adaptation, and market ideas remain proposals until their required public admissions and witnessed records exist.

Community expectations

Treat people with care, make the evidentiary state of a claim clear, and do not represent a proposal as an activated program. Ordinary messages and participation are not consent for resale, automated cohort profiling, or copying message text into a roster. If you want to discuss commercial work, licensing, or paid arrangements, keep that distinct from ordinary community participation and use an explicitly designated process when one is available.

The settlement's public account explains why the community makes these distinctions: read the settlement record. For the proposed evidence loop, see Proof of Adaptation.

To propose a gathering, practical question, project, or field note, see the active community-programming intake.

Proof of Adaptation

2026-08-29T00:00:00Z

Proof of Adaptation is a proposed way to support verified, local adaptation knowledge. It starts from the fact that a useful practice can be reported, measured, replicated, or merely repeated without evidence—and those are not the same kind of claim.

The operating first step

The open rain-garden question is the first public practice record in this path. It connects a question in #question-quarry to source trails in the Knowledge Vault, distinguishes external guidance from a local result, and invites human source review and general observations. Its current evidence state is conceived. No local site, protocol, field trial, or witnessed outcome has been admitted.

A source review could improve the question and its citations. An observation could identify conditions worth investigating. Neither would by itself prove that a rain garden works at a particular site. A field claim needs a consenting site organizer, a site-specific protocol that states what will be observed and compared, permission to use any submitted material, and a recorded result with its limits. Independent repetition would be a further step. Missing measurements remain missing; they are never recorded as zero impact.

The proposed wider loop connects signals and research to community questions, durable source records, practical guides or trials, and witnessed results that inform the next questions. The present rain-garden record demonstrates the question and source stages. It does not demonstrate a completed trial.

Duluth garden drainage question

A community question about Duluth gardens has also become an open request for provider offers. The requested first result is a bounded map and source-linked screening of one garden's surrounding drainage context. The public source check locates one garden-program map marker in a Minnesota DNR catchment and records the City data-access limit. It does not establish a garden-scale drainage path.

This question is conceived. A map-based screening, if completed and reviewed, would remain a screening; it would not establish permission, engineering feasibility, water volume, or a field outcome. No provider has been selected, no spending has been authorized, and no paid report is being offered.

Work-shaped participation

The design proposes a proof-of-adaptation token earned for completed, witnessed work and data quality. The proposal expressly does not describe an investment asset or promise appreciation. Before any such mechanism can be treated as operational, its custody, admission, and governance conditions must be earned in the settlement record.

Read the related public account of governance for the intended relationship between witnessed work and collective decision-making.

The settlement

2026-08-29T00:00:00Z

Turntide Islands is a Discord-native community settlement. Discord is one surface through which the community speaks; it is not the archive of record. The durable record is designed around typed admissions and refusals, content-addressed records, and witnessed writes.

This makes the outward-facing rule straightforward: a path is not claimed to be live merely because it is desirable. When a required admission has not been made, the record says so. When evidence is not sufficient, the appropriate result is an honest absence rather than an invented answer.

The public purpose

The settlement focuses on local and household-scale climate adaptation: building a usable, shared body of knowledge about what works under particular conditions. It is intended to strengthen practical response, mutual learning, and the capacity to act together amid climate instability.

Its proposed knowledge-refinement loop moves from signals and discussion to a durable knowledge vault, then to guides, trials, and new evidence. That loop is described in Proof of Adaptation.

The account above is drawn from the parent settlement's public definition and working synthesis, with historical promotional language left in its source record rather than presented here as a current operational claim.