The Bioregional Intelligence Dashboard
Instruments of bioregional listening, not central control.
What the Dashboard does
Six capabilities, all bound to the sovereignty firewall.
Each capability is named so a foundation officer can read what the Dashboard makes visible without losing the boundary that makes the visibility honest. Each capability is bound to the sovereignty firewall at the architecture layer; nothing on the surface bypasses the layer beneath.
Capability 01
Bioregional sensing
Listening to ecological, cultural, and social signals as they move through a bioregion over time. Aggregate signal is surfaced with explicit stewardship-circle consent; raw community data never leaves the bioregion without circle-level review. The instrument attunes to what the ground is saying; the ground decides what is heard beyond it.
Capability 02
Flow Fund deployment ledger
Every dollar deployed through Kinship Earth, transparent and queryable. The same ledger that has tracked roughly $370K across thirty-plus bioregions since October 2024, woven into the Dashboard so foundation officers underwriting the work can see deployment in close to real time alongside the annual narrative report.
Capability 03
Stewardship-circle convening
Calendars, decision logs, and consent records held for each Flow Fund stewardship circle. The infrastructure that lets a bioregion hold its own governance at human scale, and lets foundation officers see what the circle has consented to share without ever seeing more than that.
Capability 04
Cross-bioregion learning
Pattern surfacing across activations without flattening local difference. The federation pattern Colombia Regenerativa demonstrates at twelve territories, made queryable for the bioregions that come next; learning travels along kinship, with the originating circle’s permission carried through every transit.
Capability 05
Foundation-officer site-visit support
Quarterly auditable views into a specific bioregion’s work, scoped to whatever the stewardship circle has consented to share with that visitor. The reporting cadence mirrors what /regeneration already names: quarterly deployment ledger, annual narrative report, site visits welcome at any active bioregion.
Capability 06
Protocol-cycle status
Where each bioregion sits in the five-phase loop: SENSE, SEE, ACTIVATE, CELEBRATE, REGENERATE. Real-time visibility into the depth of practice rather than the velocity of motion; the count of full cycles is the depth metric the Dashboard surfaces, not a throughput proxy borrowed from elsewhere.
Data sovereignty architecture
Four structural commitments, enforced at the architecture layer.
These are not policy promises. They are structural commitments enforced at the data-architecture layer; the Dashboard cannot do what the architecture does not permit, and the architecture is built before the surface. A foundation officer reading this can take the four commitments at full weight rather than discount them as language.
01
Each bioregion's data is held by its stewardship circle, not the platform
Bioregional data lives where bioregional governance lives. The platform is the federation surface; it is not the custodian of community-held data. The commitment is enforced at the data-architecture layer rather than at the policy layer, which means the platform cannot become the custodian by accident or by drift.
02
The dashboard surfaces aggregate signal with explicit community consent
Aggregate signal is shareable across the federation only when the originating stewardship circle consents to share it. Consent is per-signal, per-period, per-audience; the default posture is closed and consent opens each surface deliberately rather than by default.
03
No raw community data leaves the bioregion without circle-level review
Any external request for raw community data passes through the Flow Fund stewardship circle for review before the data leaves the bioregion. The review is logged. The default is decline; deliberate consent is the exception, recorded as such.
04
Foundation officers see what stewardship circles have consented to share
Foundation officers underwriting catalytic capital see what the bioregion has chosen to make visible. The view honors the sovereignty firewall; the firewall is precisely what makes the view trustworthy on the receiving side.
Build status
The Dashboard MVP ships in Stage 2.
The Dashboard MVP is scheduled in Stage 2, moving from spec to beta to production along the same cadence the /use-of-funds page reads in line-item form. Production scope lands at M18 inside Stage 4 of the deployment horizon, alongside the Capital Pipeline mobilization that surfaces investable opportunities to aligned LPs. Until the MVP arrives, this page describes the design commitment the build will deliver; nothing on the Dashboard surface is shipped ahead of the architecture that holds it.
Source: use-of-funds page, Stage 2 and Stage 4 milestones. Marcus financial model, 2026-05-14, build cadence.
Read deeper
The bioregions, and the boundary.
The bioregions page names the three pilots the Dashboard is built to serve. The sovereignty page reads the boundary the Dashboard architecture is held against. Read whichever serves the conversation you are ready to have next.