Learn from how the field uses the maps.

The pre-scaling trap language helped our board understand why funding evidence alone is not enough. We need to fund the infrastructure that lets evidence emerge.

The loop was useful when we translated it into our local context. The map worked best as a conversation starter, not as a final truth.

Pattern: maps are most useful when paired with a prompt: what does this loop look like in your geography?

Community accountability stewards should be explicit. They are not just local organizations; they hold memory, legitimacy, and feedback power.

We also need translators across investor language, indigenous governance language, and systems-change language.

Potential map update: add a stewardship/memory role between local backbone and field intelligence infrastructure.

Field intelligence infrastructure feels ready: many people are mapping pieces, but nobody can see the whole field.

Financial backbone functions also need a working group, especially around how grants, guarantees, and patient investment coordinate.

We should form around energy plus readiness: enough actors, clear need, and a concrete next artifact.

The handbook helped name dynamics we feel but rarely get funded to explain. We need a shorter version for community-facing conversations.

I used the leverage points to review our portfolio. It exposed that we fund projects but not backbones.

Pattern: readers want a translation layer: board-ready, practitioner-ready, and community-ready versions of the same intelligence.

Need: mapping and translation support for a regional capital ecosystem.

Offer: fund one synthesis sprint if there is a local partner and clear community governance.

Match possibility: pair the funder with a local backbone before any capital design work starts.