# Closing Circle + Product Discussion — Synthesis

**TNN 2026 Cohort Retreat — "What are we leaving with?"**
**Thursday morning close**

> Source: closing-circle transcript. Two prompts: (1) what are you leaving with / paying attention to, and (2) what would you hand someone who wasn't here, and what would they do with it. The second prompt doubled as the product/outputs spec.

---

## The frame

The closing did two things. It named what shifted, and it handed over a product backlog. The second prompt worked exactly as designed.

## What they're leaving with

- **Re-centered on focus and mission.** The seven components reaffirmed the identity question from the go-around (Sp3).
- **Bridging, and caring for the bridges.** Co-signed by more than one voice (Sp3, Sp7).
- **"We know what we need."** A plain statement of agency (Sp4).
- **A deeper commitment to these people,** and peace with what's still unresolved (Sp4).
- **Home base.** Permission to keep leaning in through a life or structural change (Sp5, picking up Christina's earlier home-base line).
- **One person already translating it:** moving his housing org from providing a house to providing a neighborhood (Sp6). The agency-and-neighborhood thread becoming operational in a real org.
- **Joy and belly laughs,** and the sense that people here care deeply about who they accompany (Sp7).

The relational close landed where it aimed: identity steadier, ambiguity tolerable, the group worth returning to.

## The build list (what they'd hand someone who wasn't here)

This is the room specifying the recommendations package. Rough priority order:

1. **Asset map of each org.** What you do, strengths and weaknesses, resources, programs, where you could collaborate (Sp4). The most-named artifact, and the one the slide already promised.
2. **A shared offerings database.** What each org offers, made available to each other's people, so collaboration can route across the network (Sp8). A survey to populate it was already flagged.
3. **A one-page definition of TNN.** The simplest reminder of what they're after, the seven components included, for themselves first and outsiders second (Sp3). The "orientation, not overwhelm" artifact.
4. **A funder-facing neighborhood-work draft.** For Duke, Lilly, judicatory leaders, Katie's Foundation: what we mean by the work, the challenges, the opportunities, why neighborhoods. A working draft the group reacts to (Sp7).
5. **A community ground-truthing version.** The same or a variant for TNN folks who weren't in the room, and for about five people from each context, to react and pull their constituencies into the co-creation (Sp7).
6. **Facilitator meta-reflections.** What George, David, and other non-facilitating observers noticed over the weekend (Sp7).
7. **A bench inventory.** What each person is genuinely good at, and who in their context holds things not represented in the room (Sp8).
8. **The economic-security reframe.** Free time and economic security as preconditions for co-creation, not the goal. A framing to carry into the neighborhood work (Sp10).

## The principle George added (the load-bearing one)

An asset map of capability is half the artifact. The other half is commitment. The failure mode, named directly: networks catalog what people have, then find the resource unavailable when they reach for it. The fix is to capture what each member is committed to give, concretely (the ten hours, not the willingness), and to tie "what you get and what you give" to the grant so it holds.

That maps onto the declared-versus-functional distinction. The asset map is the declared system. The commitment layer is the functional one. Building the survey without the commitment field would reproduce the exact gap C4C spends its time finding in other people's systems.