Most population-segmentation strategy treats a flat 18–40% of any group as persuadable, everywhere, regardless of place. Trust Window asks a different question: not who, but when — whether a community's position on a specific ask is still forming or already settled. It's the entry point for almost everything else in the Lab conceptually. It's a concept, not yet a scored instrument — we can explain what it means and why it matters without yet attaching a validated number to when a given window opens or closes.

Descent is what makes the multi-scale reads on this page more than a marketing claim. A finding at the city level gets tested against its own neighborhoods; a neighborhood finding gets tested against the parcels inside it. Where the pattern holds across scales, we trust it more. Where it breaks, that's information too — it usually means the city-level number was masking real variance underneath.

Everything downstream of the initial trust read eventually asks some version of this question. Community Readiness is where we formalized it: a measured readiness state for a specific behavior or ask, read before outreach begins. Stated plainly: the instrument does not observe engagement after outreach launches — it doesn't verify in real time that a program is landing. That's a distinct, unbuilt capability, not something we're claiming here under a softer description.

Once we understand readiness and can zoom to the right scale, we can identify which relational channels — not individual people — a community already trusts. This is a structural, tract-level read: it tells you where relational engagement will outperform an institutional channel. It does not name or count specific individuals. Identifying the actual people who carry trust in a given place is real, qualitative fieldwork that follows from this read — a separate, deliberate step, not something the instrument itself outputs.

Civics Engine is where the readiness and pathways tools stopped being decision tools for a single client and became an ongoing practice — nonpartisan civic-participation work, grounded in the same trust read used everywhere else on this page.

Once we could reliably identify the floor — the tracts most structurally disconnected from institutional trust — we built a standing practice around it. This is the throughline across the Lab: most of what follows — health integration, food systems, land use, project finance — ends up touching a disinvested community somewhere in its scope, and this is the practice area that holds that lens.

Dark Spots are geographies where our read finds a structural disconnect between institutions and the community they're meant to serve. Put plainly: our instrument reliably finds the floor — the places most disconnected — even where it can't yet rank every place in between by degree. A Dark Spot finding describes a resolution failure in how that place has been engaged, not a fixed property of the place itself.

Media ROI maps expected engagement return across channels and geographies, so outreach effort is prioritized by where the structural read shows room to move — instead of spread evenly across a footprint out of caution, or concentrated only where it's easiest to buy attention.

This practice area grew out of early work on the ground around addiction recovery: the people and organizations a community already trusts for one kind of service — recovery support, say — are very often the same trust network serving maternal health, chronic care, or elder and child services. Sequencing integrated services in trust order, instead of by program calendar, is the core idea here.

A natural extension of Trust as Medicine: understanding how food moves efficiently through a community's existing trust network, rather than around it. Still in R&D — an active area of exploration, not yet a packaged practice area.

This traces directly back to our original purpose — finding people and places with a genuine proclivity toward nature and stewardship — applied here to building partnerships across regenerative-farming supply chains at the community level.

Once trust could be read at neighborhood scale, land use questions started to look different: a conservation or restoration thesis is stronger when it accounts for how the people around that land actually behave and what they trust, not just the ecological facts on the ground. This thesis is what connects our insurance and project-finance work below back to the original behavioral read.

This practice area is where Community Readiness meets actuarial thinking: giving insurers and impact financiers a way to talk about the resilience of the community behind a policy or a bond, not just the traditional tables. It's active work — ongoing conversations and mapping with insurance and finance partners — and it's also where our most ambitious R&D instrument, Survivability, is headed if and when it's fully built out.

Where This Shows Up

• Milwaukee — we've mapped the watershed and proposed how a resilience-bond readiness read could work. This is active, in-progress scoping, not a delivered score built into the bond structure.
• Shoreline restoration — early outreach exploring how community readiness intersects with coastal resilience financing.
• Insurance partners — the partnership conversations where Survivability, as an actuarial instrument, is the aspiration we're building toward.

Where this actually stands, matter-of-factly: these are active, in-progress partnerships and proposals, not delivered case studies. The instrument this practice area aspires to — Survivability — is still in R&D.

Best Use of Place is built from two genuinely independent reads: a classifier-based read of a community's values, and a separate, tract-based profile of its civic pillars. Cross-referencing the two tells a developer, lender, or economic-development team what a given community will steward long-term, and what a proposal will have to reckon with — not where a project will meet the least resistance. That's a deliberate distinction: this tool is diagnostic, not a map for finding the path of least consent.

It's a practice area, not a single decision tool, because it serves several audiences at once: project finance, infrastructure, community development financial institutions, economic development offices, and community mobilization efforts all draw on the same underlying read.

This reads a snapshot, not a trend — it doesn't yet show a place changing over time. That capability requires two reads taken apart, and we don't have a matched pair anywhere in the database yet.

Where Trust in Places is geography-first, Trust-Based Development is organization-first: for a funder network, a coalition, or a forum whose "community" is a collection of people and institutions rather than a place. Sun Valley Forum is the current proving ground, and we're hopeful about extending the model to other convenings. Grouped here with Trust in Places as a prototype — both are genuinely promising and both are still being built out into full practice areas.

This is the delivery layer: strategy, message design, and stakeholder engagement, sequenced by what the trust reads find rather than by an institution's default channel or calendar. It runs across every practice area above — civics, health, land use, development — as the services and innovations arm that turns a read into an actual engagement.

Everything above stays at the level a partner or funder needs to evaluate the work. For people who want the full technical record — the canonical appendix, the science behind the read, and the investor-facing materials — that sits behind one password-protected tier inside Lab at Work, not scattered across separate requests.

Survivability is the most ambitious instrument in the Lab: a way to actually price whether a community-facing investment will survive contact with the community it's meant to serve. It's real R&D, actively informing our implementation-insurance work above, but it isn't a delivered score anywhere yet — including in our Milwaukee scoping, which remains mapped and proposed, not underwritten.

The newest thread in the Lab. Still early enough that we're not ready to describe the application in detail publicly — check back as this develops.