Bottlenecks

The working hypothesis (see key question and H1) is that the sharpest bottleneck is operational orchestration — coordinating fragmented actors and resources over decades — rather than knowledge, measurement, or financing in isolation.

This page should become the evidence trail for that claim as it's gathered: specific, sourced bottlenecks observed in real projects, not restatements of the hypothesis.

Sources	None yet
Evidence	None yet
Confidence	Low / unvalidated
Last reviewed	2026-07-25

Candidate bottlenecks to investigate

• Handoffs between planning and field execution (see field workflows)
• Funder → project accountability over multi-year horizons
• Contractor availability and scheduling across many small, geographically distributed parcels
• Loss of institutional knowledge when a project outlives the people who started it
• Lack of a shared source of truth between landowner, contractor, and funder on project status

Each candidate should move to a sourced, confidence-rated entry — or be dropped — as evidence comes in from interviews.