Executives and Practitioners

A New Paradigm for Sovereign Digital Coordination

Traditional centralized digital systems are increasingly characterized by fragmented data, significant vulnerabilities to fraud and exploitation, and a critical erosion of trust in institutions. These systems often disempower individuals, disregard privacy, and fail to provide effective, equitable coordination, particularly in crisis scenarios. The Has-Needs protocol emerges as a groundbreaking, sovereignty-centered digital coordination framework designed to address these systemic failures by shifting control and verifiability to the individual and community.

At its core, Has-Needs re-architects digital interaction around user-owned “personal receipt-chains”—cryptographically secured, objective records of all activities and agreements. This design replaces conventional global consensus mechanisms with “peer-receipt and sovereign verification,” ensuring inherent data minimization and making the individual the atomic unit of data control. Complementing this is a “biomimetic network topology,” specifically the “Jitterbug topology,” which provides an attack-resistant and perfectly verifiable foundation, structurally preventing the core problems of legacy systems and enabling cryptographically verifiable legal evidence.

This architectural shift yields profound benefits across multiple domains. It establishes architectural privacy and resilience against systemic fraud by replacing gameable reputation with verifiable transaction histories. Furthermore, Has-Needs introduces an anti-extractive economic model that fundamentally revalues historically undervalued “first-class economic assets” such as time, care work, and Indigenous labor, making them visible and trackable within community-driven frameworks. In crisis mapping and disaster response, the protocol facilitates human-centered, self-organizing resource allocation, promoting trauma-mitigating logistics and offering a sustainable funding model without upfront costs.

The Has-Needs protocol represents a foundational shift towards more ethical, efficient, and equitable digital coordination. Its emphasis on individual sovereignty, verifiable interactions, and community control over data offers a compelling solution to pervasive trust and privacy challenges. Organizations and stakeholders concerned with data governance, humanitarian aid, fraud prevention, and the development of truly decentralized, prosocial economic systems should explore Has-Needs as a blueprint for building resilient digital infrastructure that aligns technological advancement with human dignity and collective well-being.

A Human-as-Base-Unit Architecture for Disaster Response, Governance, and Community Coordination

The Problem in One Paragraph

Since the mid-1990s, the practical infrastructure of everyday life — data, identity, coordination, value exchange — has been rebuilt around a fiat-denominated, commodified human. People are managed from the top down, their data owned by platforms and agencies, their needs interpreted by intermediaries, their sovereignty treated as a compliance afterthought. In disaster, this frame fails visibly and catastrophically: 95% of after-action reports document situational awareness (SA) failure as the proximate cause of response breakdown; emergency managers burn out and leave the profession; supply chains waste hundreds of millions on mismatched resources; and the people most acutely affected are systematically excluded from the systems meant to help them. These are not implementation failures. They are frame failures.

The Has-Needs Proposition

Has-Needs inverts the frame. It treats the human as the base unit of value — the sovereign source of data about their own needs, capacities, and trust relationships — and builds coordination architecture upward from there rather than downward from institutions.

The result is a system where:

Situational awareness is distributed to the people who actually have it, rather than filtered through command hierarchies that collapse under load.
Data sovereignty is structural, not a policy layer — your information belongs to you and travels with you on your terms.
Agency is emergent — the act of using the system is itself an act of self-determination, not a request submitted to an authority.
Prosocial effects arise automatically — not from designed incentives but from the architecture’s foundational logic.

The Efficiency Case (Summary)

Every current disaster response system has the same documented failure modes, in the same after-action reports, after every major event:

Failure Mode Documented Cost Has-Needs Response
SA / communications collapse $7.5B+ per LA-scale event Distributed citizen-sourced SA; no central bottleneck
Supply chain waste $150M+ per major event Real-time needs-and-haves ledger; demand visible before commitment
Volunteer mismatch $5M+ per major event Every volunteer’s haves declared; matching pre-sorted
Post-event data reconstruction $50M+ per event Continuous real-time ledger with provenance; no reconstruction needed
Interop / coordination tax $20M+ per event Sovereign data belongs to person, not agency; shared semantics by design
Emergency manager turnover $30M+ annually sector-wide Eliminates the unstructured tasks that generate burnout
Has-Needs does not require new infrastructure. It rides mesh networks, existing smartphones, and whatever communications substrate exists. It supports self-organizing systems that already emerge in disasters — the Sandy bulletin boards, the Harvey Facebook groups, the Katrina neighbor networks — giving them the structured, sovereignty-preserving layer they were improvising toward.

The Prosocial Case (Summary)

Has-Needs produces twelve documented prosocial effects as emergent properties of participation — not as designed features, incentive programs, or add-on interventions:

Personal needs met through collective behavior — collective visibility produces individual outcomes without central redistribution.
Layered community autonomy and privacy — sovereignty is structural; a neighborhood can share internally without exposing data upward.
Redemption — the bidirectional ledger reveals that everyone has something to offer, reorganizing self-concept in ways that protect against PTSD and social withdrawal.
Adjustable personal trust — granular, user-controlled trust tiers maintain participation from the most vulnerable people, whose needs are most likely to go unmet under current systems.
Anonymous need/resource matching — removes stigma barriers to declaration of need without removing the match; increases prosocial contagion.
Safe AI — AI operates within the sovereign frame the human has declared; it cannot optimize against an objective function the human never consented to.
Situation-dependent metrics — the system measures what the situation declares is important, making it impossible to optimize for the wrong outcome.
Governance accountability — every resource commitment and flow is logged in the sovereign ledger; accountability is architectural, not aspirational.
Direct participation and democratization — asynchronous, low-barrier participation means the decision about what is needed and available is made by the people who have and need things.
Asynchronous parallel recovery — recovery starts when people start declaring, not when the recovery plan is published.
Portable dignity — your record of participation and contribution travels with you across displacement and resettlement, on your terms.
Solution-based meetings of strangers — needs matching across group boundaries structurally produces Allport’s four contact conditions every time, counteracting xenophobia through direct positive experience at scale.
None of these are features. They are what happens when you build from the human up.

The Funding Model

Has-Needs charges a 5% fee on the total realized savings from using the system. The fee is:

Delayed — assessed after the event closes, once the ledger is settled.
Zero upfront cost — no budget appropriation required before a crisis.
Auditable — the sovereign ledger is the record of value delivered compared to similar historical events.
Self-justifying — 5% of efficiency value is a fraction of the waste and overhead it replaces.
A single mid-scale deployment (population ~500K) fully funds the project on first activation.
A single medium scale deployment generates $2–5M — sufficient to fund two years of operations and international expansion.

The Theoretical Foundation

Has-Needs is not just an application. It is a theory of human-centered coordination — one that meets the contemporary criteria for “good theory”: it is problem-laden (built to solve specific, documented failures), plausible (its mechanisms echo known structures in cognitive science, economics, and systems theory), multi-aimed (it explains current failures, predicts outcomes under its own framework, and unifies trauma-informed practice, governance, and resource logistics), and pluralist (it works across methodological traditions and scales).

The agency restoration it produces during disaster is not a side effect — it is the most direct intervention available against peritraumatic PTSD, which research identifies as driven primarily by loss of agency, not by injury or loss alone. A governance and resource coordination architecture that produces mental health outcomes as an emergent property of use, at mass scale, at the moment it matters, is something that does not currently exist in any other form.

What Makes Has-Needs Unique

Every existing platform — mutual aid apps, government emergency portals, humanitarian data systems, supply chain tools — treats data sovereignty as a compliance layer added after the architecture is already established. The prosocial and efficiency benefits described above cannot be added as layers to existing systems. They can only emerge from a foundation built on the human as base unit.

Has-Needs is that foundation.

“Efficiency and human dignity are not in tension here — they are the same thing. A system that treats humans as the base unit of value is more efficient precisely because it stops wasting resources on the overhead of treating them as anything else.”

Built on a Foundation of Theory and Practice

When Dr. Dan Diamond — the physician who directed the Mass Casualty Triage Unit at the New Orleans Convention Center during Hurricane Katrina — heard the Has-Needs pitch, his response was immediate: “I’ve been asking for this for 30 years.”

When Dr. William B. Miller Jr. — the evolutionary biologist who originated Cognition-Based Evolution — encountered the architecture, he stated that he had never seen an analog to CBE in social systems, but understood it instantly and became an enthusiastic endorser.

These are not endorsements. They are category statements. Thirty years of documented professional need from the physician who witnessed the most studied disaster coordination failure in American history. And immediate recognition from the scientist whose life’s work describes exactly what Has-Needs instantiates — because no one had ever built it before.

Dr. William B. Miller Jr. Architect of Living Systems

Dr. William B. Miller Jr. is a physician and evolutionary biologist whose body of work constitutes the scientific foundation for the Has-Needs architecture. He is the originator of Cognition-Based Evolution (CBE) a peer-reviewed theoretical framework establishing that all cells are cognitive agents: they perceive, assess uncertain information, and deploy resources accordingly.[1][2] Evolution, in Miller’s framework, is not random variation selected from outside; it is the yield of continuous, non-random, self-referential problem-solving by sovereign biological units at every scale of life.

Miller has developed CBE across seven books published with leading academic and trade presses. His peer-reviewed work appears in Progress in Biophysics and Molecular Biology, and his framework is recognized as a significant contribution to evolutionary theory’s “Third Way” the growing body of research that extends beyond the Modern Synthesis to account for the cognitive and cooperative dimensions of biological systems.[3][4] His 2023 Cognition-Based Evolution: Natural Cellular Engineering and the Intelligent Cell (Routledge) is the definitive technical statement of the theory.[5] His 2024 Bioverse: How the Cellular World Contains the Secrets to Life’s Biggest Questions (Simon & Schuster) presents the same framework for a broader audience.[6]

The relevance to Has-Needs is structural, not metaphorical. CBE establishes three non-negotiable features of resilient biological systems: sovereign agents who assess their own local information; cooperative exchange as the coordination mechanism; and emergent complexity as the outcome of aggregate interactions, not central design.[1][2] Has-Needs instantiates all three. The Sovereign Being is the cell. The Has/Need/Working triplet is the cell’s state assessment. The receipt chain and emergent ontology are the organism’s memory and pattern recognition. The Jitterbug network topology is the self-healing, locally-aware tissue of a living system.

When Dr. Miller said he had never seen an analog to CBE in social systems, the significance of his immediate endorsement was precise: Has-Needs is not an application of his theory — it is the first instantiation of it in human-built systems. That statement, from the architect of the theory, is the strongest possible scientific endorsement the Has-Needs architecture can receive.

Dr. Dan Diamond The Expert in Real-World Crisis

Dr. Dan Diamond is a physician, disaster responder, and leadership researcher with thirty years of front-line experience in the world’s most severe humanitarian crises. He holds the rank of MD and FAAFP, serves as Clinical Assistant Professor at the Elson S. Floyd College of Medicine at Washington State University, and is the founder and former Director of the nation’s first state-affiliated medical disaster response team.[7][8]

His ground-level credentials are unmatched. Dr. Diamond served as Director of the Mass Casualty Triage Unit at the New Orleans Convention Center during Hurricane Katrina — the single most documented failure of centralized disaster coordination in American history.[9][10] He was among the first physicians on the ground after the Haiti earthquake and Typhoon Hainan in the Philippines. He has been recognized with the President’s Volunteer Service Award, the American Red Cross Real Hero Award, and the Washington State Governor’s Award of Excellence.[7][8]

What separates Dr. Diamond from other disaster medicine credentials is the question he came home from Katrina asking: “Why is it that some people don’t become victims?”[11] That question became the research program documented in his book Beyond Resilience: Trench-Tested Tools to Thrive Under Pressure[12] — a framework for understanding what enables individuals and teams to become “Thrivers” rather than passive victims, even when institutional infrastructure has completely collapsed. His answer centers on agency, connection, and the perception that one’s actions matter — the exact psychological properties that Has-Needs is architecturally designed to preserve and strengthen.

When Dr. Diamond said “I’ve been asking for this for 30 years,” the weight of that statement is specific. He did not ask for it as an abstract aspiration. He asked for it from the floor of the Convention Center, surrounded by people whose needs were invisible to the coordination systems that were supposed to serve them. The fact that he recognized the answer immediately — and that it took 30 years for anyone to build it — is the most precise statement available of both the depth of the problem and the uniqueness of the solution.

The Synthesis

The combination of these two advisors is the intellectual architecture of Has-Needs in human form.

Dr. Miller provides the “how”: the biological principles that explain why sovereign, cooperative, locally-intelligent systems produce resilience and why top-down, centrally-coordinated systems produce brittleness. His work answers the question every technical reviewer will ask: why is this architecture right?

Dr. Diamond provides the “why” and the “who”: thirty years of documented evidence that the systems Has-Needs is designed to replace have failed, repeatedly and predictably, at the worst possible moments — and the first-hand knowledge of what the people inside those failures actually needed. His work answers the question every funder and institutional partner will ask: why does this matter, and for whom?

Together they give Has-Needs something no feature comparison or efficiency metric can substitute: a claim that is simultaneously true from the deepest level of biological science and from the floor of the most studied disaster response failure in American history.

Sources
[1] Miller, W.B. Jr., “Biological information systems: Evolution as cognition-based information management,” Progress in Biophysics and Molecular Biology, 2018. https://pubmed.ncbi.nlm.nih.gov/29175233/
[2] Miller, W.B. Jr., The Third Way of Evolution contributor profile. https://www.thethirdwayofevolution.com/people/view/william-b.-miller-jr
[3] Miller, W.B. Jr., Center for Humans & Nature contributor profile. https://humansandnature.org/william-b-miller-jr/
[4] Open Library, William B. Miller Jr. author page. https://openlibrary.org/authors/OL7687613A/William_B._Miller_Jr.
[5] Miller, W.B. Jr., Cognition-Based Evolution: Natural Cellular Engineering and the Intelligent Cell, Routledge, 2023. https://www.taylorfrancis.com/books/mono/10.1201/9781003286769/cognition-based-evolution-william-miller
[6] Miller, W.B. Jr., Bioverse: How the Cellular World Contains the Secrets to Life’s Biggest Questions, Simon & Schuster, 2024. https://www.simonandschuster.com/books/Bioverse/William-B-Miller/9781633887992
[7] Diamond, D., Faculty Bio, American Association of Physician Leaders. https://www.physicianleaders.org/faculty/bio/dan-diamond
[8] Diamond, D., Speaker profile, All American Speakers. https://www.allamericanspeakers.com/celebritytalentbios/Dan+Diamond/442696
[9] Diamond, D., official website. https://www.dandiamondmd.com
[10] Diamond, D., TEDxSeattle speaker profile. https://tedxseattle.com/speakers/dan-diamond/
[11] Diamond, D., Leadership page. https://www.dandiamondmd.com/leadership
[12] Diamond, D., Beyond Resilience: Trench-Tested Tools to Thrive Under Pressure. https://www.thriftbooks.com/w/beyond-resilience-trench-tested-tools-to-thrive-under-pressure_dan-diamond/10765797/

Why a Human-as-Base-Unit Architecture Outperforms Every Current Disaster Response Model — and Funds Itself

Part 1 — The Root failure: Situational Awareness

Situational awareness (SA) failure is not one of many problems in disaster response — it is the documented proximate cause of most response breakdowns. A systematic review of 302 articles and after-action reports found that inadequate or failed communications and connectivity appeared in 95% of after-action reports reviewed, with analysis and visualization failures appearing in 35% and interoperability failures in 35%. The technologies currently in use were consistently found not adequate for obtaining SA, limiting speed, efficiency, and effectiveness of response.

This is not a bandwidth problem. It is a shared meaning and interoperability problem: agencies are physically co-located but still operating from different, incompatible operational pictures.

The 2025 LA fires made this concrete. The McChrystal Group after-action report found that the county’s response was not defeated by a single catastrophic failure but by a cascade: a dispatch system nearly 40 years old, over 900 sheriff vacancies, digital alerts failing due to power outages and inconsistent cellular coverage, and first responders unable to share information due to “unreliable cellular connectivity, inconsistent field reporting methods, and the use of various unconnected communication platforms.” The LAPD’s parallel after-action report documented that LAPD and LAFD personnel were physically working from the same command post but failed to “collectively establish a unified command structure or identify shared objectives, missions, or strategies.” Flames advanced at 300 yards per minute while incident commanders had no shared operational picture.

Has-Needs addresses this at the root. When citizens declare their needs, haves, location, and status in real-time, they provide continuous, locally grounded, attentionally relevant information without requiring relay chains, interpretation layers, or centralized aggregation. The fuzz around situational awareness is eliminated not by better command software but by making the humans in the situation the primary data source.

Part 2 — The Legacy Dependency That Keeps Failing

The National Emergency Communications Plan has documented the same core finding since Katrina, 9/11, and every major event since: “The near total failure of regional communications degraded situational awareness and exacerbated problems with agency coordination, command and control, logistics, and search and rescue operations.”

This is not a new finding. It is the same finding, repeated after every major disaster, because the structural dependency on single-channel radio infrastructure and centralized dispatch has not changed. The attempted solution — hiring more experts, building more simulation infrastructure, standing up more platforms on incomplete data — compounds the problem rather than solving it. It deepens reliance on centralized, brittle systems rather than distributing SA to the people who actually have it.

Has-Needs does not replace incident command, radios, or dispatch. What it does is eliminate the specific class of failure these reports document: the command structure’s dependence on a small number of single-channel, centralized information flows that collapse under load. Has-Needs provides a parallel, distributed, citizen-sourced SA layer that functions on mesh networks, existing smartphones, and whatever communications substrate exists — without requiring new towers, new dispatch software, or expanded data staff.

Research on mesh networking for disaster communication demonstrates that users across large geographic regions can communicate without cellular coverage, power, or pre-existing infrastructure using only Wi-Fi-equipped handheld devices. Has-Needs is designed to ride on exactly this substrate: the data structure is sovereign, minimal, and portable — not dependent on a centralized database that must be operational for anything to function.

Part 3 — The Data Gap and Downstream Distortions

UNDRR’s 2023 analysis found that disaster impact data is “fragmented, disjointed, and incomplete,” systematically biased toward insured and reported losses, and that municipalities, national governments, and NGOs collect incomparable data that cannot be aggregated meaningfully. In practice, more than 90% of disaster losses go uncounted — particularly for low-income, uninsured, and historically marginalized populations.

The consequence is not just a reporting problem. It is a funding and policy distortion: response systems are optimized for the visible fraction of damage rather than actual need, and preparedness investments for the next event are built on fundamentally flawed baselines. The GAO and PNNL have both documented that the “gap assessment problem” — we don’t know what we have, what’s needed, or what’s been provided — is endemic to current disaster response architectures. Municipalities routinely spend millions per event on post-hoc damage surveys, loss estimation studies, and needs assessments — work that reconstructs information that should have been captured in real-time.

Has-Needs generates event metrics as a byproduct of its normal operation. Every need declared, every have offered, every match made, and every transaction completed is a data point with provenance, timestamp, and sovereign consent. The data gap is not filled by a post-hoc survey or an insurer’s loss model — it is filled continuously, in real-time, by the people experiencing the event. Situation-dependent metrics become natural: you measure what the situation requires (reunification velocity, supply gap by geography, unmet medical need density) rather than what your legacy reporting tool happens to capture.

Part 4 — The Coordination Tax

Supply Chain: Waste at Scale

Post-Katrina, FEMA ordered 211 million pounds of ice in a single week. Approximately 60% was unnecessary — a direct consequence of asymmetric information about where the need actually was. Relief organizations, operating without demand visibility, repeatedly served the same affected regions while others went unserved. Research on humanitarian supply chains finds that “effort duplication worsens the scarcity of relief resources” — a finding replicated across every major disaster studied. The waste across all consumables (water, MREs, generators, medical supplies) in a single large-scale event runs into the hundreds of millions of dollars.

Has-Needs’ continuous needs-and-haves ledger is a structural solution: real-time demand visibility eliminates the guesswork that produces both over-supply in one location and zero supply in another.

Volunteer Coordination: The Spontaneous Volunteer Problem

After Hurricane Harvey, volunteers from different organizations worked on the same house simultaneously while other sites had no one. Untrained individuals arrived at shelters in large numbers because “we need volunteers” was broadcast with no structured needs-matching. The Points of Light Foundation estimates the value of volunteer time at $28.54/hour. In a major event with 10,000 volunteers misallocated by even four hours each, that is over $1.14 million in lost volunteer value — per event, before counting the coordination staff time consumed managing the resulting chaos.

In a Has-Needs architecture, the spontaneous volunteer is no longer noise — they are the primary input. Every volunteer’s haves are declared, every need is visible, matching is pre-sorted.

Interoperability: A Trust and Semantic Failure, Not Just Technical

Current interoperability efforts treat the problem as CAD-to-CAD system integration. But the literature consistently identifies that even when technology is compatible, “inter-agency factors like trust, communication, collaboration, and standardization” prevent effective coordination. The cost of not having interoperable systems — “such as duplicated efforts and inefficient responses — can be far greater in the long run” than the cost of implementing interoperability. That avoided-cost calculation is computable per event, per jurisdiction, per response type, using existing after-action documentation.

Has-Needs addresses this at a deeper level: sovereignty-respecting shared semantics mean that agencies can share situational information without requiring they trust each other’s data governance, because the data belongs to the person who declared it, not to any agency.

Municipal Message Efficiency: The Nonprofit and Voluntary Organization Gap

A North Carolina legislative audit found that a majority of nonprofit volunteer organizations did not know the defined roles and responsibilities of participating agencies, and that agencies did not know what nonprofits could provide. Has-Needs’ intra-municipal message efficiency comes not from removing communication steps but from making capability-and-need visibility continuous — no formal agreements, no training cycles, no pre-negotiated MOU language required before anyone knows what anyone else has or needs. When information networks prove reliable and useful, they are reinforced and prioritized.

Supporting Self-Organizing Systems That Already Work

NSF-funded research on Hurricane Sandy identified that citizen-based emergent groups — Occupy Sandy, People’s Relief, Red Hook Initiative — organized through Facebook, Twitter, and blogs and provided aid before FEMA or Red Cross could reach affected communities. These groups self-organized, created points of distribution, coordinated volunteers, and distributed resources through informal lateral structures while official response was still scaling up — using improvised, inadequate tools and still outperforming the formal system in the early critical window.

Has-Needs is the structured layer those improvised systems were trying to be: a sovereignty-respecting, structured needs-and-haves matching architecture that supports exactly that self-organizing pattern without requiring it to be improvised from scratch each time.

Part 5 — The Human Cost: Burnout and Talent Drain

Emergency management has a documented and worsening workforce crisis. Research across state and local agencies found 12-hour-plus days as routine, work environments described as “emotionally taxing and physically grueling,” and a “brain drain” of experienced personnel leaving for higher-pay, lower-intensity jobs. A 2026 mixed-methods study identified high levels of concern regarding “overall lack of funding and resources, risk of burnout, underrepresentation of minority groups in leadership, and lack of standardization” as the defining challenges of the current workforce.

Burnout research is specific about the mechanism: workload significantly increases burnout, and the correlation between high burnout and intention to leave “underscores the urgent need for interventions to prevent a potential drain of experienced personnel, which could significantly impair emergency response capabilities.” The COVID-19 pandemic’s multi-year activation produced a demonstrable wave of turnover that left agencies structurally understaffed going into the 2025 LA fires. Emergency manager PTSD and compassion fatigue rates are themselves documented costs; the chaos load is not incidental to the job description — it is the job description, under current system design.

The tasks that produce burnout are precisely the tasks Has-Needs eliminates: fielding unstructured information requests from the public, manually aggregating situational data, managing the consequences of system brittleness under load, and repeatedly rationalizing failed infrastructure projects to leadership. The efficiency gain for emergency managers is not incidental — it is a structural consequence of moving situational awareness to a distributed architecture where citizens are productive inputs rather than noise sources.

Part 6 — What Has-Needs Replaces, Structurally

Current System Problem	Has-Needs Structural Response
SA collapse under load	Distributed citizen-sourced SA; no central bottleneck
Single-channel radio / legacy dispatch dependency	Rides mesh, smartphone, any substrate; no new infrastructure required
Supply mismatch and waste	Real-time needs-and-haves ledger; demand visible before commitment
Spontaneous volunteer chaos	Every volunteer’s haves declared; matching pre-sorted by system
Interoperability as trust and semantic failure	Sovereign data belongs to person, not agency; shared semantics by design
Post-event data reconstruction costs	Full-fidelity real-time ledger with provenance; no reconstruction needed
Municipal / nonprofit coordination gap	Continuous capability visibility; no MOUs required to see capacity
Emergency manager burnout and talent drain	Eliminates the specific unstructured tasks that generate burnout load
Self-organizing systems using improvised tools	Has-Needs is the structured layer those systems were trying to be
Doomed simulations on incomplete data	Citizen-sourced data is real-time ground truth; models built on it are valid

Part 7 — The Monetization Argument: 5% Fee on Demonstrated Savings

The Fee Model

Has-Needs charges a 5% fee on the total realized savings compared to similar events before deployment. The fee is delayed: assessed and collected after the event closes, once the ledger of completed matches is settled.

This structure means:

Zero cost to adopt. No budget line needed pre-event. No procurement cycle required before a crisis.
Zero cost during the crisis. The fee triggers only on demonstrated, ledger-verified value delivered.
Fully auditable. The ledger is the sovereign record. Every match, transaction, and declared value is already timestamped and provenance-tracked by design.
Self-justifying. If Has-Needs saves $10M in resources, the fee is $500K — a fraction of what the same coordination would have cost through manual processes, failed infrastructure contracts, or post-hoc data reconstruction.
Incentive-aligned. Has-Needs only earns when resources are successfully saved. No saving, no fee. No history of expenditures for disaster, no fee. This provides a built-in sliding scale aligning with ethical tenets of the project.

Cost / Funding Analysis

Cost Center	Current Documented Cost (per major event)	Avoided Cost with Has-Needs (conservative)	5% Fee Yield
Situational Awareness (SA) / Communications failure	$7.5B+ (LA fires: economic loss attributable to SA breakdown)	$6.75B (90% avoidable with distributed SA)	$337M
Supply chain waste	$150M+ (FEMA ice alone + consumables)	$90M (60% of mismatch eliminated)	$4.5M
Post-event data reconstruction	$50M (damage surveys, needs assessments, loss estimation)	$45M (continuous ledger eliminates most)	$2.25M
Volunteer coordination waste	$5M (10K volunteers × 4 hrs × $28.54/hr + coordinator time)	$4M	$200K
Interop / coordination tax	$20M+ (duplication, failed contracts, consultant fees)	$15M	$750K
Manual incident response overhead	$5M/yr per mid-size agency	$3.5M (78-min faster resolution × frequency)	$175K
Emergency manager turnover	$30M+ sector-wide annually	$20M (burnout load reduction)	$1M
Total (single large-scale event)	$7.76B+	$6.93B+	$346M+

Note: LA-scale economic loss figures are conservative. Total economic losses from the 2025 Eaton and Palisades fires are estimated at $135–150B; the SA/communications failure attribution represents the fraction directly linked to coordination breakdown documented in after-action reports.

Deployment-Scale Revenue

Mid-scale municipal deployment (population ~500K, moderate event):

Conservative resource value saved through platform: $20–50M
5% fee: $1–2.5M
This range fully funds Has-Needs development, deployment, and first full operational year.

Large-scale deployment (LA-scale event):

Resource value saved: $500M–$1B+
5% fee: $25–50M
Sufficient to fund full project operations for a decade and support international expansion.

Counter to Typical Objections

Objection	Response
“Why would municipalities pay?”	They are already paying far more in waste, failed contracts, and turnover. The fee is a fraction of documented avoided costs — calculable from their own after-action reports.
“Why delayed payment?”	Removes all adoption friction. No budget appropriation required before the event. The fee comes from the efficiency gain, not a new line item.
“Why 5%?”	Below the transaction cost of almost any alternative coordination mechanism (broker fees, consultant fees, procurement overhead) and well below the waste percentage it replaces.
“What if they don’t want to pay after?”	The ledger is the record of value delivered. Every matched need and completed transaction is timestamped and provenance-tracked. The fee is a percentage of a documented ledger, not an invoice for a promise.
“What about jurisdictions with no budget?”	Delayed fee model means they deploy at zero upfront cost. The fee is collected from the efficiency gains and avoided waste the system itself generates.

Conclusion: Efficiency Is the Entry Point

Every prosocial benefit of Has-Needs — agency restoration, portable dignity, xenophobia reduction through direct experience, governance accountability, community autonomy — is real and supported by research. But efficiency is the entry point for every buyer: municipal emergency managers, federal agencies, NGOs, and insurers all speak the language of avoided cost.

Has-Needs does not ask them to believe in a philosophy. It asks them to read their own after-action reports, identify the cost centers that appear in every one, and compare those costs to a 5% fee on demonstrated, ledger-verified value delivered. The case closes itself.

The deeper truth is that efficiency and human dignity are not in tension here — they are the same thing. A system that treats humans as the base unit of value is more efficient precisely because it stops wasting resources on the overhead of treating them as anything else.

Why Every Existing System Is on the Same Side of the Wrong Paradigm

This document does not compare Has-Needs to its competitors on features. Feature comparison is the wrong frame — and accepting it concedes the most important argument before the conversation begins. This document establishes the paradigm difference first, names the specific systems that share the failing paradigm, and shows precisely how each system’s architectural failure mode is a direct consequence of the assumption it shares with every other system in the field.

The Paradigm, Not the Product

In 2019, Harvard Professor Shoshana Zuboff named the dominant logic of the digital economy: surveillance capitalism — “the unilateral claiming of private human experience as free raw material for translation into behavioral data,” which is “then computed and packaged as prediction products and sold into behavioral futures markets.”[1][2] Every major platform, from Google to Facebook to Amazon, operates on this logic. The user is not the customer. The user is the raw material.

What is less widely recognized is that every major disaster response, emergency management, and humanitarian coordination platform operates on the same logic. The affected person is not the primary information source. They are a data subject — someone about whom data is collected by enumerators, sensors, damage assessors, and after-action reports. The data flows upward to institutions that own it, analyze it, and act on it at their discretion. The person who experienced the event has no chain entry, no receipt, no visibility into what was decided about them or whether anyone received their report.

This is not a criticism of individual platforms or their designers. It is a structural observation about a shared architectural assumption: that coordination requires an institution at the center that owns the data. Every system listed in this document accepts that assumption. Has-Needs rejects it at the protocol level. That is the entire competitive distinction, and it produces all the specific capability differences that follow.

The Named Systems

Palantir Gotham / Foundry — The Surveillance Architecture at Scale

Palantir has become the dominant data analytics platform for federal emergency response and homeland security. In February 2026, the Department of Homeland Security struck a $1 billion purchasing agreementwith Palantir, further deepening the federal government’s structural dependency on the company’s infrastructure.[3][4] Palantir’s CEO explicitly defends the company’s surveillance technology as its core product offering.[5]

Palantir’s emergency management offering — Foundry for emergency preparedness, response, and recovery — aggregates datasets from multiple agencies, creates integrated situational pictures, and enables cross-government coordination through a centralized analytics layer.[6] It is technically sophisticated and genuinely useful for the institutions that operate it.

The architectural failure is categorical, not qualitative. Palantir’s model requires institutions to bring their data to Palantir’s platform — which means the data belongs to Palantir’s infrastructure, not to the people whose experience generated it. A survivor’s location, medical need, and family situation become rows in a dataset that Palantir processes for its institutional clients. The survivor has no chain entry. They cannot see what was decided about them. They cannot correct a wrong record. They cannot take their data when the event is over. And crucially: they have no agency in the system at all. They are the subject, not the actor.

The business model confirms the architecture: Palantir’s revenue comes from institutions — DHS, FEMA, defense agencies — not from the people those institutions nominally serve. The incentive is to maximize institutional dependency, not to empower survivors. A $1 billion agreement with DHS is the logical conclusion of this model, not an aberration.[3][4]

D4H / WebEOC / Veoci — The Centralized Common Operating Picture

D4H and its equivalents (WebEOC, Veoci, NC4) are the dominant incident command and emergency operations center platforms at the municipal and state level. Their core offering is the Common Operating Picture — a centralized, cloud-based single source of truth for incident commanders, updated in real time by response personnel.[7][8]

The Common Operating Picture is the right solution to the coordination problem these systems are designed to solve. The problem is that they define the coordination problem as an institutional problem: how do incident commanders share information with each other? The answer is a centralized database that authorized personnel update and query.

What this architecture cannot do is accept input from the people most directly affected. The affected citizen is not a node in D4H’s network. They are an object to be tracked, not an actor who can update their own status, declare their needs, or see what is being done about them. The Working state visibility chain in Has-Needs — “Your need is accepted, assigned to Field Team 7, awaiting equipment” — has no analog in any Common Operating Picture platform, because the platform’s users are responders, not survivors. When cellular networks overload and dispatch systems reach capacity, the Common Operating Picture goes dark — because all its information sources are centralized, and centralized information sources fail at scale under exactly the conditions that produce demand for them.

Esri / ArcGIS — The Geodata Institution

Esri holds the dominant position in humanitarian geospatial data. The UN Office for the Coordination of Humanitarian Affairs (OCHA) signed an enterprise agreement with Esri in 2023, centralizing all humanitarian administrative boundary data into ArcGIS Enterprise and automating sharing across field offices.[9][10] The explicit design goal is a “single authoritative source” managed by OCHA — a centralized SQL geodatabase that all field mapping activities depend on.[9]

This is the geospatial expression of the same paradigm. “The owner of the item is always responsible for that item” — the ArcGIS training documents state this explicitly.[11] Data in an ArcGIS environment belongs to the organization that holds the enterprise account, not to the people whose locations and needs the data describes. The centralized geodatabase is an institutional asset. When the institution loses access — power failure, network outage, institutional collapse — the data disappears with it.

Has-Needs’ geospatial layer is structurally inverse: location is always homomorphic encrypted, owned by the individual, never stored in a central repository, and the mapping layer emerges from sovereign declarations rather than from institutional collection. There is no geodatabase that a power failure can take offline.

KoboToolbox — The Extractive Open Source Model

KoboToolbox is the most widely deployed open-source humanitarian data collection platform, used by UNHCR, the World Bank, and hundreds of NGOs for needs assessments, protection monitoring, and incident reporting.[12][13] Its open-source status and humanitarian mission make it the most sympathetic system to compare — and the architectural failure is therefore the most instructive.

UNHCR’s own Terms of Use are precise about what KoboToolbox is: “a platform for digital data collection” in which “UNHCR Kobo is not intended for long-term data storage.” Data collected in UNHCR Kobo “will be stored in Amazon Web Services (AWS) servers located in Ireland.” Partners are advised to move data to “a secure data storage platform within one year.”[14] The person whose needs were assessed owns none of this. The enumerator fills out the form. UNHCR owns the server. AWS holds the data. The affected person has no access, no receipt, no chain entry, and no way to know what was recorded about them or whether it was accurate.

More fundamentally: KoboToolbox is a data collection tool, not a coordination tool. It moves data from people to institutions. It does not coordinate resources. It does not match needs to offers. It does not create accountability chains. It produces datasets from which institutions make decisions — which means it is upstream infrastructure for the same institutional decision-making model that Has-Needs replaces entirely.

A recent academic analysis of digital solidarity platforms found the same structural pattern replicated even in nominally cooperative systems: “emancipatory rhetoric often co-exists with data monopolies, assetisation tactics and legal clauses that reproduce extraction.” One platform examined stated that “data belongs to citizens” in one section while specifying in another that “data obtained with user consent is owned by the city and consortium firms.”[15] The paradigm persists even when the stated intent is to reject it, because the architecture was never changed.

What Has-Needs Is Not Competing On

Every system above competes on the same axis: how efficiently can an institution aggregate, analyze, and act on data about affected people?That competition has a logical conclusion: the institution with the most data, the most processing power, and the most sophisticated analytics wins. Palantir’s $1 billion DHS agreement is where that competition ends up.

Has-Needs is not competing on that axis. It is answering a different question: what if the affected person is the primary information source, the owner of the data, and the agent of coordination — and institutions are participants in that network rather than its operators?

That question produces different answers to every downstream problem:

Problem	Surveillance Paradigm Answer	Has-Needs Answer
Situational awareness	Aggregate sensor and report data to central dashboard	Sovereign Beings declare their own state continuously
Needs matching	Institutions assess needs and deploy resources	Direct bilateral matching between Sovereign Beings
Accountability	Audit trails owned by the institution	Bilateral receipts owned by both parties
Privacy	Data governance policies	Architectural: data cannot leave without consent
Resilience	Redundant infrastructure	No central infrastructure to fail
Survivor agency	Service recipient interface	Sovereign participant in coordination

The distinction is not that Has-Needs is better at what Palantir does. It is that Has-Needs makes most of what Palantir does unnecessary — because the problem it solves was created by the architecture Palantir inherited.

The Specific Institutional Argument

For institutional buyers evaluating Has-Needs against their current vendors, the argument is not “replace Palantir with Has-Needs.” It is simpler: Has-Needs provides the data layer that your current vendors cannot reach. Palantir can analyze whatever data it receives. D4H can coordinate whatever responders are logged in. ArcGIS can map whatever datasets are uploaded. None of them can get pristine, real-time, self-reported data from the people inside the event because their architecture makes that person a data subject rather than a data source.

Has-Needs provides exactly that layer. It does not compete with institutional analytics platforms; it feeds them data that their current architecture is structurally incapable of producing. And it does so at no upfront cost, with a fee model that only activates on verified savings, which means the institutional buyer is not choosing between Has-Needs and their current vendor. They are adding a layer of capability that their current vendor cannot provide, at zero risk to their existing infrastructure, that basically amounts to receiving pristine data requests and having local resources matched to needs in the form of self-organized and pooled requests.

Sources
[1] Zuboff, S., Harvard Gazette interview, “Surveillance capitalism is undermining democracy,” March 2019. https://news.harvard.edu/gazette/story/2019/03/harvard-professor-says-surveillance-capitalism-is-undermining-democracy/
[2] Wikipedia, “Surveillance capitalism.” https://en.wikipedia.org/wiki/Surveillance_capitalism
[3] Wired, “DHS Opens a Billion-Dollar Tab With Palantir,” February 2026. https://www.wired.com/story/department-homeland-security-ice-billion-dollar-agreement-palantir/
[4] Reuters, “Palantir CEO defends surveillance tech as US government contracts boost sales,” February 2026. https://www.reuters.com/world/europe/palantir-ceo-defends-surveillance-tech-us-government-contracts-boost-sales-2026-02-02/
[5] The Hill, “Palantir courts major federal contracts — and controversy,” January 2026. https://thehill.com/policy/technology/5667232-palantir-trump-administration-surveillance/
[6] Palantir, “Emergency Preparedness, Response & Recovery,” product overview. https://www.palantir.com/assets/xrfr7uokpv1b/1EE4kLUXymcHCQ68Xo2OzQ/8cbc5cc985ff4c3cddffdeb292c2967a/Emergency_Preparedness__Response___Recovery.pdf
[7] D4H, “How to Harness the Power of D4H for Effective Emergency Management,” 2019. https://www.d4h.com/no/blog/how-to-harness-the-power-of-d4h-for-effective-emergency-management
[8] D4H, Emergency Management Software product page. https://www.d4h.com/emergency-management-software
[9] Esri, “Enterprise GIS Unifies Workflows for UN’s Humanitarian Aid Coordinators,” January 2026. https://www.esri.com/about/newsroom/arcnews/enterprise-gis-unifies-workflows-for-uns-humanitarian-aid-coordinators
[10] Esri, “Effective Humanitarian Response Requires Integrated Systems,” February 2026. https://www.esri.com/en-us/industries/blog/articles/effective-humanitarian-response-requires-integrated-systems
[11] Esri, ArcGIS Humanitarian Response Webinar transcript, December 2018. https://www.youtube.com/watch?v=R0yK4ji5k2Y
[12] KoboToolbox / JDC, “Joint Initiative Announced to Enhance KoboToolbox,” 2022. https://www.kobotoolbox.org/blog/joint-initiative-announced-to-enhance-kobotoolbox-for-data-collection-and-analysis-in-displacement-contexts/
[13] KoboToolbox / UNHCR Ukraine, “How UNHCR is using KoboToolbox,” December 2022. https://www.kobotoolbox.org/blog/how-unhcr-is-using-kobotoolbox-to-support-the-needs-of-people-affected-by-conflict-in-ukraine/
[14] UNHCR Kobo Terms of Use, August 2024. https://im.unhcr.org/kobosupport/terms_of_use/
[15] Policy Review, “Governance, technology, and the limits of digital solidarity economies,” February 2026. https://policyreview.info/articles/analysis/governance-technology-limits-digital-solidarity

Why a Living-Systems Design Is the Only Architecture That Survives Contact With Reality

An evidence-anchored account of why the Has-Needs architecture is not metaphorically biological, it is structurally identical to the coordination mechanisms that have sustained life for 3.8 billion years, and why that fact matters for every deployment scenario the system will face.

The Core Claim

Has-Needs does not borrow inspiration from biology. It instantiates the same structural principles that biology discovered under selection pressure over deep time: sovereign agents, local information, stigmergic coordination, and emergent complexity with no central planner. The case for this is not philosophical — it is architectural. Every failure mode of current humanitarian and governance systems maps precisely to the places where their designs diverge from these principles, and every unique capability of Has-Needs maps to the places where they converge.

Cognition-Based Evolution: The First-Principles Foundation

Dr. William B. Miller Jr.’s theory of Cognition-Based Evolution (CBE), published in peer-reviewed work and developed across seven books including the 2023 Cognition-Based Evolution: Natural Cellular Engineering and the Intelligent Cell (Routledge), proposes a radical reframing of evolutionary biology: all cells are cognitive agents.[1][2] A cell is not a passive executor of genetic instructions — it measures uncertain environmental information, assesses it, and deploys resources accordingly. Evolution is not random variation selected from outside; it is the yield of “continuous non-random self-referential cellular problem-solving.”[1]

The implications for system design are precise. CBE establishes that complex, resilient biological systems — immune systems, neural networks, colonial organisms, ecosystems — are not designed top-down but emerge from the cooperative, information-sharing interactions of sovereign individual units.[3] No cell has a complete map of the organism. No neuron directs the brain. Resilience and intelligence are properties of the network of interactions, not of any central coordinator. When a cell fails, adjacent cells adapt locally; the system self-heals without anyone issuing a repair order.

This is the exact architecture of Has-Needs. The Sovereign Being is the cell. The Has/Need/Working state is the cell’s assessment of its own state in relation to its environment. The Community is the tissue. The receipt chain is the organism’s memory. And the matching network is the immune system — a distributed pattern-recognition apparatus that identifies need and deploys response without a central command.

Stigmergy: Coordination Without Communication

The biological mechanism that makes complex collective behavior possible without central control is stigmergy — coordination through traces left in a shared environment that influence subsequent actions.[4] Grassé identified it in termite colony construction in 1959; subsequent research has established it as a universal coordination mechanism operating across bacteria, insects, neural tissue, and human social systems.[4][5]

The key property of stigmergy is documented precisely: it “enables complex, coordinated activity without any need for planning, control, communication, simultaneous presence, or even mutual awareness.”[4] A termite does not know it is building a nest. It responds to local conditions — the presence of a pheromone trace, a particular substrate — and its action modifies those conditions for the next agent. The nest emerges from the aggregate of locally rational actions, and it is structurally more sophisticated than any individual agent could plan.

In Has-Needs, every receipt is a stigmergic trace. A completed exchange modifies the local information environment — updating the ontology, making a new match pattern available, registering a new Community resource — in ways that guide subsequent exchanges without any agent needing awareness of the whole. The emergent ontology is not designed; it crystallizes from the aggregate of local matching choices exactly as a termite nest crystallizes from aggregate local building choices. The sophistication of the pattern is a property of the interaction history, not of any planner.

Fractal Self-Similarity: The Community Structure

Biological systems are fractal: the same organizational principles repeat across scales.[6] A cell operates by the same information-assessment logic as an organ, which operates by the same logic as an organism, which operates by the same logic as an ecosystem. Self-similarity across scales is not incidental — it is the mechanism by which biological systems remain coherent and adaptive across enormous ranges of complexity and context.[7]

Research on fractal organization in social and ecological systems confirms that “the resilience of social and ecological systems is often tied to their fractal structure” — they adapt to external shocks by redistributing resources and reorganizing at different scales while maintaining overall coherence.[8] Rigid, non-fractal hierarchies cannot do this: a shock that disrupts the central coordinator disrupts everything simultaneously.

The Community entity in Has-Needs is fractal by design. A family is a Community. A block is a Community. A neighborhood, a municipality, a county — each is the identical architecture applied at a different scale, with the same sovereignty guarantees, the same receipt logic, the same matching primitives. Noise is managed by replication, not by rules: when a Community becomes too large or too noisy for its purpose, members create a sub-Community with the same architecture at smaller scale. No new tools, no new governance layer, no new permissions. A county organization’s entire org-chart can be re-instantiated as a Community tree using the identical structural primitive — and every node in that tree maintains full sovereignty with no data flowing upward without explicit consent.[9]

This is categorically different from platform-based community management, which imposes a single taxonomy and governance structure across all scales and resolves noise through rules and moderation. The biological analogue is the difference between a living organism and a machine: the organism self-organizes at every scale; the machine requires external maintenance at every scale.

The Triplet as Minimal Sufficient Signal

Biological information processing operates on the minimal sufficient signal. A cell does not process the entire state of the organism to decide whether to divide — it reads local chemical gradients and responds. CBE formalizes this: “assessment of information precedes biological action,” and the assessment is always local, bounded, and self-referential.[1] The efficiency of biological cognition comes precisely from the minimalism of the signal, not from the sophistication of the processor.

The Has-Needs triplet — [entity, relation, context] with three possible relation states (HAS, NEEDS, WORKING) — is the digital equivalent of this minimal sufficient signal.[9] It contains exactly what is needed for a match and nothing else. This minimalism has a direct and critical consequence for AI processing: structured semantic triplets require orders of magnitude (~85%-95%) less computational effort than natural language processing on unstructured text. Where NLP must parse syntax, resolve ambiguity, infer meaning, and map to a domain model — operations that scale poorly and consume substantial energy — triplet matching performs direct semantic alignment against a pre-structured knowledge graph.[10][11] The AI does not interpret language; it compares structures. The user’s own choices define context, and those choices accumulate into an emergent ontology that progressively improves matching precision without any central taxonomy being imposed.

This is biologically faithful: the organism’s “vocabulary” emerges from the history of its interactions with its environment, not from an external dictionary. The ontology is alive — it evolves as the community’s needs and resources evolve — and it captures cultural and linguistic nuance precisely because it grows from the ground up rather than being translated downward from an institutional data model.[9]

Self-Healing Topology: The Jitterbug Network

Biological communication networks — neural tissue, vascular systems, mycelial networks — are self-healing because every node has only local awareness. A neuron does not need a map of the brain to reroute a signal; it responds to the state of its immediate neighbors. Research on distributed self-healing networks confirms that this local-awareness architecture produces “higher robustness and efficiency than conventional self-healing methods,” and that systems where “nodes have only local knowledge of the networks” can reconstruct connectivity after failures without central routing tables.[12][13]

Has-Needs’ Jitterbug network topology implements this principle directly. Nodes are organized in a biomimetic, regular geometry where each node monitors only its immediate neighbors. Faults are detected and routed around locally — no node needs awareness of the global topology, and no central coordinator is required to issue repair instructions. The network self-heals the same way mycelium self-heals: the living edge of the network routes around dead tissue by finding alternative paths among neighbors.[14] This represents a world-first in autonomous networking.

This infrastructure claim makes every other promise in the Has-Needs suite architecturally honest. The “no central chokepoint” claim in the Sovereign Economics document, the “distributed citizen-sourced situational awareness” claim in the Efficiency document, and the “portable sovereignty” claim in the PTSD document all depend on a network substrate that does not collapse when any node or set of nodes fails. The Jitterbug topology is that substrate, and its resilience is not engineered — it is emergent from local rules, exactly as biological resilience is emergent from cellular rules.

Anti-Fragility: Strengthening Under Stress

Biological immune systems do not merely survive stress — they become more capable in response to it. Exposure to a pathogen produces not just immediate response but lasting adaptive memory; the organism is stronger after the encounter than before.[3] This is the property Nassim Taleb identified as anti-fragility: the system gains from disorder rather than merely tolerating it.

Current engineered disaster response systems are brittle. They are designed for anticipated failure modes and collapse under unanticipated ones — as the LA fires after-action reports document in precise detail.[15] The more novel the disaster, the worse they perform, because their intelligence lives in their design rather than in their operational history.

Has-Needs is anti-fragile by the same mechanism as biological immunity: every exchange adds to the emergent ontology and the receipt graph. The more the network is used — and especially the more it is stressed by novel demands — the richer its pattern-recognition capability becomes. A community that has used Has-Needs through a drought, a flood, and a supply disruption has a more sophisticated matching network than one that deployed it for the first time in an emergency. The system does not just survive repeated use; it improves under it. This property cannot be engineered into a centralized system, because a centralized system’s intelligence lives in its design, which is fixed at deployment. It can only emerge from a system whose intelligence is the aggregate of its operational history — exactly as biological intelligence is the aggregate of evolutionary history.[1][3]

The Meta-Claim: Biology Solved This Already

The problems that have defeated every humanitarian coordination and governance system for the past century — brittle infrastructure, central chokepoints, top-down data extraction, emergent complexity without central planning, sovereignty under stress — are not new problems. They are the problems that life solved under selection pressure over 3.8 billion years.

CBE establishes that the solution involves three non-negotiable architectural features: sovereign agents who assess their own local information; cooperative exchange as the coordination mechanism; and emergent complexity as the outcome of aggregate interactions, not of central design.[1][2][3] Has-Needs instantiates all three. No current humanitarian platform, governance system, or disaster coordination architecture does.

The consequence is not philosophical. It is operational: a system built on the same structural principles as living systems will behave the way living systems behave — resilient under stress, adaptive to novelty, self-healing after damage, and increasingly capable with use. A system built against those principles will behave the way machines behave — efficient within their design envelope, brittle at its edges, and dependent on external maintenance to continue functioning.

Has-Needs is not a better machine. It is a different kind of thing entirely.

Sources
[1] Miller, W.B. Jr., “Biological information systems: Evolution as cognition-based information management,” Progress in Biophysics and Molecular Biology, 2018. https://pubmed.ncbi.nlm.nih.gov/29175233/
[2] Miller, W.B. Jr., Cognition-Based Evolution: Natural Cellular Engineering and the Intelligent Cell, Routledge/Taylor & Francis, 2023. https://www.taylorfrancis.com/books/mono/10.1201/9781003286769/cognition-based-evolution-william-miller
[3] Miller, W.B. Jr., The Microcosm Within: Evolution and Extinction in the Hologenome, Universal Publishers, 2013. https://humansandnature.org/william-b-miller-jr/
[4] Heylighen, F., “Stigmergy as a universal coordination mechanism I: Definition and components,” Cognitive Systems Research, 2016. https://www.sciencedirect.com/science/article/abs/pii/S1389041715000327
[5] Irie, Y. et al., “Stigmergy: A key driver of self-organization in bacterial biofilms,” Open Biology, 2013. https://pmc.ncbi.nlm.nih.gov/articles/PMC3984292/
[6] Adcock, R., “Fractal Intelligence: A Hypothesis of Self-Organization in Natural Systems,” 2024. https://randaladcock.com/2024/09/07/fractal-intelligence-a-hypothesis-of-self-organization-in-natural-systems/
[7] Frontier in Physics, “Fractal approaches to scaling transformations to sustainability,” PMC, 2023. https://pmc.ncbi.nlm.nih.gov/articles/PMC10406776/
[8] Jackson, “The Fractal Organization: How Nature’s Branching Patterns Enable Resilience,” LinkedIn / Taylor & Francis, 2026. https://www.linkedin.com/pulse/fractal-organization-how-natures-branching-patterns-jackson-ph-d–rx8he
[9] Has-Needs Project, “Frame 2: The Technical Narrative — The Living Ecosystem,” internal document, 2026.
[10] LSEO, “Mastering Semantic Triples for Machine Comprehension,” 2026. https://lseo.com/join-lseo/mastering-semantic-triples-for-machine-comprehension/
[11] Seale, T., “How triples power knowledge graphs and AI,” LinkedIn, 2025. https://www.linkedin.com/posts/tonyseale_one-of-the-simplest-yet-most-powerful-ways-activity-7301164277233577985-asm7
[12] Miyata et al., “Distributed Self-Healing for Resilient Network Design in Local Networks,” Frontiers in Physics, 2022. https://www.frontiersin.org/journals/physics/articles/10.3389/fphy.2022.870560/full
[13] Quattrociocchi et al., “Self-Healing Networks: Redundancy and Structure,” PMC/PLOS ONE, 2014. https://pmc.ncbi.nlm.nih.gov/articles/PMC3922772/
[14] Decentralised Self-Healing for Network Topology Maintenance, AAMAS Proceedings / arXiv, 2020. https://arxiv.org/abs/2010.11146
[15] McChrystal Group / LAPD, “Los Angeles Wildfires After-Action Reports,” 2025. (Referenced in EFFICIENCY-has-needs.md)
[16] Protocol Labs, “Advancing IPFS and libp2p Governance,” 2023. https://www.protocol.ai/blog/advancing-ipfs-and-libp2p-governance/
[17] Miller, W.B. Jr., Bioverse: How the Cellular World Contains the Secrets to Life’s Biggest Questions, Simon & Schuster, 2024. https://www.simonandschuster.com/books/Bioverse/William-B-Miller/9781633887992
[18] The Third Way of Evolution, “William B. Miller, Jr.,” contributor profile. https://www.thethirdwayofevolution.com/people/view/william-b.-miller-jr

How the Four Entities, the Receipt Chain, and the Living Network Actually Work

Here is a rigorous, evidence-anchored account of the Has-Needs protocol architecture — the four primitive entities, the receipt-only data model, the novel consensus mechanism, the fractal Community structure, the privacy stack, and the DXOS foundation that makes a 4–6 month build timeline realistic today.

The Architectural Premise

Current digital coordination systems are built on a premise that Has-Needs rejects entirely: that a central authority must own the data in order to coordinate the actors. Banking systems own your financial history. Platforms own your social graph. Emergency management systems own situational awareness. In every case, the authority precedes the coordination, and the person is a data subject rather than a data source.

Has-Needs inverts this at the protocol level. It defines four primitive entities — Sovereign Being, Has, Need, Working — from which all coordination behavior emerges without any central owner. The architecture is not a better database. It is a different kind of thing: a receipt substrate on which coordination becomes a natural property of honest participation, and sovereignty is structurally guaranteed rather than policy-promised.[1][2]

The Four Entities

1. Has and 2. Need

Has and Need are declarations, not requests submitted to an authority. A Has is a Sovereign Being’s signed assertion that it possesses or can offer a resource. A Need is a signed assertion that it requires one. Both are structured as [entity, relation, context] triplets — the minimal sufficient data structure for coordination.[5] The relation is one of three states: HAS, NEEDS, or WORKING. The context is defined entirely by the declaring Being: what the resource is, where, when, under what conditions, and which Community or Communities it is visible to. No external taxonomy is imposed. The ontology — the system’s growing map of what resources exist and how they relate — emerges from the aggregate of human choices about what to declare and what to match, rather than from a schema imposed by a platform or standards body.[5]

3. Sovereign Being

The Sovereign Being is the atomic unit of the protocol. Every person, organization, device, or community node that participates in Has-Needs is a Sovereign Being: a self-owned, cryptographically anchored identity that no external authority issues or revokes. The technical basis is the W3C Decentralized Identifiers (DIDs) specification — globally unique identifiers that entities generate themselves, authenticating via cryptographic proofs rather than third-party registries.[3][4] Unlike most DID implementations, which solve identity and then plug the person into existing extractive rails, Has-Needs makes the Sovereign Being the origin and terminus of all data flows. Nothing moves without a Sovereign Being initiating it, and nothing persists without the initiating Being’s signed consent.

4. Community

Community is the fourth primitive entity — not a governance layer, not a feature, not a moderation tool. It is a structural container that scopes visibility, aggregates resources, and enables collective coordination, with four defining properties. The Community is merely a grouping of consensed individuals.

Entirely malleable. A Community can be created for any purpose — a family, a block, a mutual aid network, a municipality’s emergency operations, an Indigenous nation’s data cooperative — using identical architecture at any scale.[5][14] No new tools, no new permissions, no new primitives are required regardless of scope.

Fractal. The same architecture that governs a family’s resource sharing governs a county’s entire org-chart. A county can be instantiated as a Community tree where every department, sub-department, and working group is a sub-Community, each with its own sovereignty guarantees, each able to share internally without exposing data upward without explicit consent. The fractal property means that a shock to one node does not propagate to all nodes, because no node has privileged access to another node’s data.[14][15] A Community is therefore able to recreate any organizational chart.

Noise-managed by replication, not rules. When a Community becomes too large or too diffuse for its purpose, members do not petition for moderation policy. They create a sub-Community with a smaller, more focused membership — the identical architecture at smaller scale. Noise reduction is an architectural consequence of Community scoping, not an administrative task.[5]

Dissolve-at-will. A Community can be dissolved by its members for any reason, at any time. When a Community dissolves, member chains persist intact. No data is lost; the container is simply no longer active. This makes Community membership a genuinely voluntary association — not a platform relationship that extracts value from exit costs.

Responsiveness In disaster, a self organized collective request is the preferential entity for aid and governance to respond to. This provides prosocial dynamics even in extremis.

Wisdom As a layered and protected entity, the Community is ideal to empower indigenous groups to share and secure their wisdom while still allowing an accountable mechanism for including wisdom in value-exchange transactions.

The Receipt Chain: Not a Ledger, Not a Blockchain

The personal receipt chain is the most important architectural distinction Has-Needs makes, and the most frequently misunderstood. It is not a distributed ledger. It is not a blockchain in any conventional sense.

A conventional blockchain copies a shared ledger of every transaction to every node — an energy-intensive, plutocratic model where influence is proportional to computing power (Proof of Work) or to wealth (Proof of Stake).[7] Has-Needs implements no such global record. Instead, each Sovereign Being maintains their own append-only chain of signed receipts — a personal record of what they have declared, offered, accepted, and completed. Chains do not replicate globally. They replicate only to the parties and Communities that a Being explicitly authorizes.[8]

The receipt chain records what happened, not what someone said about it. There are no ratings, no reviews, no trust scores, and no reputation metrics anywhere in the protocol.[6] Each entry is a cryptographically signed, hash-chained record of an event: a Has declared, a match accepted, a Working state progressed, a completion confirmed by both parties. The bilateral confirmation — where both parties independently write an identical completion entry that produces matching hashes — is the proof of the exchange. A hash mismatch between two parties’ records of the same event is not a reputation penalty; it is a publicly visible discrepancy that any third party or observer can inspect and interpret on their own terms.

This is the architecture’s answer to every legal and jurisdictional question. Has-Needs is a jurisdiction-agnostic evidence substrate. A cryptographically signed, bilaterally confirmed receipt constitutes admissible evidence of an event in virtually any legal system, without Has-Needs mediating, adjudicating, or interpreting that evidence.[9] Each locale processes receipts according to its own legal capacity and conventions. Has-Needs provides the facts; institutions and communities provide the interpretation.

Overlay-Secured Data: Consent as the Access Protocol

Sensitive data — health declarations, financial records, location, cultural knowledge, identity credentials — is never exposed on the raw chain. It is managed through Overlays Capture Architecture (OCA): a schema layer that separates a stable data capture base from interoperable, task-specific overlays that control how data is displayed, shared, and interpreted.[10][11]

Access to sensitive data is granted via revocable, cryptographically signed API keys — not by sharing the data itself. A healthcare provider who needs to verify a medical need does not receive the underlying health record; they receive a zero-knowledge proof that the relevant condition is true, without any additional disclosure.[12][13] The terms of that access are themselves a contract on the Has-Needs network: what is shared, with whom, for what purpose, and for how long. Revoking access is as simple as invalidating a key — the data itself never left the Sovereign Being’s chain.

This is not compliance management. It is something architecturally more powerful: consent-first data access that makes external regulatory compliance a natural property of the system’s normal operation, rather than a layer added after the architecture is already built.

Chain-Hopping: A Novel Consensus Mechanism

Has-Needs introduces a consensus mechanism that does not exist anywhere else in the distributed systems literature: chain-hopping verification, where the integrity of a network of bilateral receipts is continuously verified by traversing the social graph of completed exchanges at every point of contact.[5][7]

Continuous, Omnidirectional Verification

Chain-hopping is not a periodic audit or an on-demand check. It occurs at every potential match, in both directions simultaneously. When a Has is surfaced as a candidate for a Need, both chains vet each other in parallel — the Need-holder’s chain traverses the Has-holder’s exchange history, and simultaneously the Has-holder’s chain traverses the Need-holder’s. This happens across the entire active network, in every direction, continuously and randomly as matches are evaluated. The result is that the verification graph is never static; it is the ambient constant behavior of normal protocol operation, and no single chain can accumulate unverified status without being encountered repeatedly by other chains performing their own vetting.

Critically, the Node Marshall and Persona Manager pass all vetting messages automatically. Vetting traversal cannot be blocked, slowed, or intercepted by any party. A chain that is reachable will be vetted; a chain that attempts to obstruct traversal is indistinguishable from a chain that is unreachable or tampered with, and is treated accordingly.

Two Stopping Conditions

Chain-hopping traversal stops on either of two conditions:

Condition 1: Eight hops of hash-consistent bilateral receipts. The traversal follows the graph of completed exchanges, checking hash consistency at each bilateral record. After eight consecutive hash-consistent hops without encountering a mismatch, the traversal returns trustable. This threshold is grounded in the Watts-Strogatz small-world network model, which establishes that real social networks exhibit high local clustering and short average path lengths — producing the empirically documented small-world property where any two nodes are reachable within a small number of hops.[16][17] Eight is conservative; in healthy community networks, trustabletypically returns within three to five hops.

Condition 2: Prior interaction encountered. If traversal reaches a chain that the verifying node has previously exchanged with directly, it returns trustable immediately. A prior bilateral exchange is already a hash-verified receipt — further traversal is redundant. This condition has a compounding architectural consequence: the longer a Sovereign Being participates, the faster verification completes for any new counterpart, because the probability of encountering a prior interaction within the first few hops grows with exchange history. The network becomes more efficient — not just more trustworthy — with use.

Time-Decay Re-Vetting

Users can configure a time-decay threshold: if the elapsed time since the last direct interaction with a specific chain exceeds the user’s setting, the next encounter triggers a fresh full chain-hop vetting regardless of prior trustable status. This functions as the protocol’s analog to biological immune memory decay — previously verified, but worth re-checking after a long absence. The threshold is a user preference; it is not enforced by the protocol.

UI: The Verification Spectrum

The verification state of every potential match is visible to the user in real time via a color progression:

Brown — chain encountered, vetting not yet initiated or identity unresolved
Red — vetting in progress, trustability unconfirmed
Green — return: trustable received; 8 hops cleared or prior interaction confirmed

The user is never silently protected. They see exactly where in the verification cycle each candidate sits and can make a situational trust decision to proceed at any point in the progression. A user in an emergency matching with a brown or red chain because no green candidates are available makes an informed choice, not a hidden one. The system provides the facts of verification state; the user retains the decision.

The Grey List: Automatic Discrepancy Publication

The Grey List is Has-Needs’ only enforcement mechanism — and it is fully automatic. No human moderator, no administrator, no Has-Needs operator triggers or manages it. It is a consequence of the protocol’s mathematics.

When chain-hopping encounters a hash mismatch — two parties holding conflicting records of the same completed exchange — the discrepancy is published immediately to the Grey List on IPFS, the decentralized storage layer accessible to all nodes. The affected chain entries receive a status: untrustable as of <date> marker applied to all parties involved in the discrepancy, without exception. The system does not adjudicate who is at fault; it records that the records disagree and makes that fact publicly visible.[4][6]

Because the Persona Manager writes identical entries on all party chains simultaneously, a hash mismatch should be mathematically impossible under normal operation. Its presence is near-certain evidence of post-write manipulation. The untrustable status reflects this: it is not a warning or a yellow flag but a structural statement that the chain’s integrity cannot be verified from that point forward.

Resolution is possible in two ways: the transaction can be reversed by both parties writing an identical cancellation entry that reconciles the record, or the discrepancy can be reconciled by identifying and correcting the specific divergent entry with the agreement of all involved parties. Both resolutions produce new receipt entries that document the correction.

Filters: Visibility Mode vs. Quiet Bypass

Every filter in Has-Needs — greylisted chains, chains with unresolved Working states, chains past a time-decay threshold — operates in one of two modes that the user controls:

Quiet bypass: The filtered chain is not surfaced. The user does not see it; matching proceeds as if it does not exist for this query.

Visibility mode: The filtered chain is surfaced, flagged with the specific reason for filtering, and the user decides whether to engage. The user sees the Grey List status, the unresolved Working state count, or the time-decay flag — and makes an informed situational choice.

This is a sovereignty decision at the UI layer. Filters in visibility mode are not a cage; they are a tool for informed decision-making. In a low-resource emergency environment where the only available match is a greylisted chain, visibility mode allows the user to see that chain and proceed with full knowledge of its status. Quiet bypass is for routine operation; visibility mode is for situations where the user wants maximum information.[5][6]

Blind Matching: The Long-Term Honesty Incentive

Has and Need declarations in Has-Needs are sent blind. When the matching engine surfaces a candidate, neither party sees the other’s identity, chain history, or Community affiliations before both independently approve the match. Identity is revealed only after mutual approval, when the communication channel for Working state coordination opens.[5][6]

This design has a structural consequence that replaces the need for a reputation system: long-term behavior in a blind matching environment is self-correcting toward honesty. A party that consistently offers matches and fails to deliver accumulates unresolved Working states — exchanges that entered the commitment stage and never produced a completion receipt. Unresolved Working states are visible in chain-hopping traversal and are a primary filter criterion for most users. A party that misrepresents its Has declarations to attract matches and then fails to deliver will find its Working-state-to-completion ratio deteriorating, its chains increasingly filtered across the network’s visibility-mode displays, and its matching surface progressively contracting — without any moderator or administrator making a judgment. The incentive structure of the protocol makes honest declaration the rational long-term strategy, not an ethical demand.[5]

The Persona Manager: The Sovereign Kernel

The Persona Manager (PM) is the kernel of sovereign identity: the single, formally bounded component through which all identity operations pass, analogous in design principle to a formally verified microkernel like seL4, where the security guarantee derives from the mathematical proof that no operation outside the kernel’s defined specification is possible.[18][19]

The PM’s most critical function is simultaneous identical chain entry. When any transaction event occurs — a Has declared, a match approved, a Working state progressed, a completion confirmed — the PM writes identical entries on all party chains at the same instant. This is the mechanism that makes hash mismatch definitionally fraudulent: if both parties’ entries are written by the same process from the same data at the same moment, any divergence cannot be an error of omission or timing. It is evidence of tampering, with no ambiguity to adjudicate.

The PM is also the system’s self-healing identity layer. If a chain’s hash integrity is compromised for any reason — hardware fault, network interruption, or attempted manipulation — the next Persona Manager that touches that chain automatically provisions a fresh kernel from the canonical chain state. Recovery is architectural, not administrative.

No external process can access or manipulate the PM directly. It is a sovereign kernel that exposes only the interfaces it defines, on terms the user controls. All third-party access to a Sovereign Being’s data flows through the PM’s consent layer — where access grants are themselves receipts on the chain, revocable at any time.

The Node Marshall: Encrypted Coordination

The Node Marshall manages all network operations: node creation, state management, Jitterbug topology routing, and the homomorphic computation layer through which all location-sensitive matching passes.[8] Like the PM, the Node Marshall passes all vetting and coordination messages automatically — it cannot be obstructed, queried externally, or used as a surveillance point by any party.

The Node Marshall enforces the no-aggregate guarantee: there is no single search surface, no index of all Needs in an area, no population-level query that any node or administrator can issue. Needs are matched local-first and specifically — the matching engine surfaces candidates to the declaring Being; it does not expose the declaring Being’s Needs to any searchable database. This is not a policy restriction; it is an architectural consequence of how data is scoped. A Sovereign Being’s declarations are visible only within the Communities that Being has explicitly joined, and there is no cross-Community search layer in the protocol.

Homomorphic Location: Matching Without Disclosure

Location is always homomorphic encrypted in Has-Needs. This is not a privacy setting — it is a protocol invariant. No plaintext coordinates are ever transmitted, stored in a shared location, or visible to any party including the Node Marshall.[20][21]

The mechanism is additively homomorphic public-key encryption applied to spatial coordinates. The Node Marshall computes proximity matching directly on ciphertext: given two encrypted location values, it determines whether they fall within a specified distance threshold without decrypting either value.[22][23] The output is a binary match signal — near or not near — with no intermediate result that could be used to infer actual coordinates.

User location is automated and not subject to distortion. The PM captures location from the device and encrypts it before it enters any coordination pathway. This prevents location misrepresentation and removes the disclosure burden from the user entirely.

Users can filter out geographic areas — for danger avoidance, operational focus, or any other reason — and these filters are also applied on encrypted data. A user specifying a zone to exclude does not expose those coordinates to any party; the exclusion is computed homomorphically against the same ciphertext layer. The result is a matching surface that is proximity-aware but location-blind: the system knows who is near whom for matching purposes, and nothing else.[20][22]

The Smart Contract as Executable Agreement

Working state in Has-Needs is not a status flag — it is an executing smart contract. When both parties approve a match, the agreed conditions become a set of ordered execution steps that run through to completion.[5][24]

Any term of a smart contract can be encrypted with the counterparty’s public key and remain encrypted throughout the contract’s execution. An encrypted contract term still produces a hash-matchable entry: the Persona Manager writes the encrypted term identically on both chains, and the hashes match because the encrypted content is identical — even though neither party can read the other’s encrypted terms, and Has-Needs itself cannot read any of them.[25] This makes privacy-preserving contract execution a first-class feature of the protocol: terms that must remain confidential can be so while still participating in the bilateral integrity guarantee.

Third-party physical escrow integrates naturally into smart contract execution. A trusted agent — an individual, a community organization, a mutual aid hub — can be designated as a physical escrow party for exchanges involving goods or materials. The escrow agent receives the goods and holds them pending transfer. The recipient’s acceptance — recorded as a signed receipt entry on their chain — triggers the completion hash that closes the Working state and unlocks the counterparty’s entry. No central platform or intermediary authority is required: the transfer is complete when the bilateral completion receipts match.[26]

The Emergent Ontology and AI Efficiency

The [entity, relation, context] triplet produces a structural consequence for AI processing that is one of the most significant architectural advantages of the protocol. Standard coordination systems rely on natural language processing (NLP) to extract meaning from unstructured text — operations that scale poorly, consume substantial compute, and introduce systematic errors wherever human language is ambiguous or culturally specific.[27]

Semantic triplets require none of this. A triplet is already structured: the relation type is known, the entity is anchored to a sovereign DID, and the context is a set of explicit key-value assertions defined by the declaring Being.[28] Matching is direct semantic alignment between structured objects — algorithmically equivalent to a graph query rather than a language comprehension task. This reduces the computational effort for matching by orders of magnitude compared to NLP-based approaches.[27][28]

The ontology that emerges from aggregate triplet matching is not designed or imposed. It crystallizes from the history of human matching choices, capturing cultural and linguistic nuance precisely because it grows from the ground up — authored by the people whose reality it describes — rather than being translated downward from an institutional data model.[5] As such, the localized ontology is always culturally appripriate and built up over time into a self-pruning valuable entity.

DXOS Foundation: Build Reality

Has-Needs uses DXOS as its foundational infrastructure — an open-source, production-ready framework for local-first, collaborative peer-to-peer applications built on CRDTs and libp2p.[29][30] DXOS handles the distributed systems complexity that would otherwise require 12–18 months of custom development:

Peer-to-peer networking via libp2p — battle-tested in IPFS’s global content-addressed storage infrastructure[31]
Sovereign identity primitives — users own their keys; no central identity authority
CRDT-based synchronization — Conflict-Free Replicated Data Types guarantee that offline-first editing across disconnected nodes converges automatically when connectivity resumes, with no locking and no central arbiter[32][33]
Encrypted storage — end-to-end encryption by default; data stays with users and communities
Spaces — DXOS’s multi-user collaboration contexts map directly to Has-Needs Communities, including nested spaces for sub-communities

By building on DXOS rather than from scratch, the custom development scope reduces to domain-specific logic: the triplet matching engine, Jitterbug topology implementation, OCA overlay integration, and chain-hopping verification. The result is a realistic 4–6 month build timeline with a team of three engineers at a total development cost well under $500,000 USD — and a system built on infrastructure that is already running in production environments globally.[29][30]

Complete Privacy Stack

The full privacy architecture of Has-Needs is the interaction of five components that each address a distinct attack surface:

Layer	Component	What It Prevents
Identity	Persona Manager	External access, chain manipulation, identity spoofing
Location	HE via Node Marshall	Coordinate disclosure, location aggregation, proximity inference
Data	OCA Overlays + ZKP	Sensitive data exposure, over-disclosure, surveillance
Network	Jitterbug + libp2p	IP address exposure, traffic analysis, central chokepoints
History	Receipt Chain + Grey List	Post-hoc manipulation, silent fraud, unaccountable abandonment

No single component provides the full guarantee. The guarantee is the composition: a system where location is never disclosed, identity is user-controlled, sensitive data is overlay-gated, network topology is self-healing, and exchange history is tamper-evident. Each layer enforces its guarantee structurally — not through policy, not through terms of service, not through administrator oversight — which is the only foundation on which a genuine privacy guarantee can be made.

The Meta-Claim: Architecture Is Policy

Every policy promise that humanitarian and governance systems make — data sovereignty, privacy, accountability, dignity — is only as strong as the architecture it rests on. Has-Needs makes no policy promises. It makes architectural guarantees:

Sovereignty is structural: your data cannot leave your chain without your signed consent, because the protocol has no other mechanism for data movement.[1][3]
Evidence is architectural: every receipt is cryptographically signed and bilaterally confirmed; the record cannot be altered after the fact by any party, including Has-Needs.[6][9]
Accountability is emergent: the Working state and receipt chain make commitments visible and failures undeniable — not because a rule says so, but because the data structure makes silence structurally impossible.[5][6]
Complexity is fractal: the same four primitives that coordinate a family’s crisis response coordinate a county’s disaster management — without a single new governance layer, permission system, or institutional agreement.[14][15]
Verification is ambient: chain-hopping runs continuously, in both directions, at every point of contact — not as an audit but as the normal behavior of the network itself.[5][7]

The architecture does not promise better behavior. It changes what the system makes possible — and what it makes impossible. That is the only foundation on which a just coordination infrastructure can be built.

Sources
[1] W3C, “Decentralized Identifiers (DIDs) v1.0,” July 2022. https://www.w3.org/TR/did-core/
[2] W3C, “Decentralized Identifiers (DIDs) v1.1,” March 2026. https://www.w3.org/TR/did-1.1/
[3] Dock Labs, “Self-Sovereign Identity: The Ultimate Guide 2026,” 2026. https://www.dock.io/post/self-sovereign-identity
[4] Wikipedia, “Self-sovereign identity.” https://en.wikipedia.org/wiki/Self-sovereign_identity
[5] Has-Needs Project, “Has-Needs_Project.md” and “frame2-technical_narrative.md,” internal documents, 2026.
[6] Has-Needs, “Has-Needs-Comprehensive-Blueprint3: No Trust/Reputation — Receipts Only,” internal document, 2026.
[7] Has-Needs, “Novel Features: Chain-Hopping Verification,” Has-Needs_Project.md, 2026.
[8] Has-Needs, “Stack.md: Node Marshall, Persona Manager, Jitterbug Topology,” internal document, 2026.
[9] Cord Network, “Selective Disclosure and Zero Knowledge Proofs,” 2023. https://docs.cord.network/techoverview/zeroknowledge/
[10] Human Colossus Foundation, “Overlays Capture Architecture,” 2021. https://humancolossus.foundation/blog/cjzegoi58xgpfzwxyrqlroy48dihwz
[11] OCA Technical Specification, ColoSSI Network. https://oca.colossi.network/specification/
[12] Human Colossus Foundation, “OCA 2.0: A New Era of Semantic Flexibility,” 2025. https://humancolossus.foundation/blog/introducing-overlays-capture-architecture-20-a-new-era-of-semantic-flexibility
[13] Gataca, “Zero Knowledge Proof and Selective Disclosure,” 2023. https://gataca.io/resources/blog/ssi-essentials-which-selective-disclosure-protocol-will-succeed/
[14] Adcock, R., “Fractal Intelligence: A Hypothesis of Self-Organization in Natural Systems,” 2024. https://randaladcock.com/2024/09/07/fractal-intelligence-a-hypothesis-of-self-organization-in-natural-systems/
[15] PMC, “Fractal approaches to scaling transformations to sustainability,” 2023. https://pmc.ncbi.nlm.nih.gov/articles/PMC10406776/
[16] Kleinberg, J., “The Small-World Phenomenon and Decentralized Search,” Cornell University, 2003. https://ww2.amstat.org/mam/04/essays/smallworld.html
[17] Watts, D. and Strogatz, S., “Collective dynamics of small-world networks,” Nature, 1998. Discussed in: https://data4sci.substack.com/p/the-watts-strogatz-model-and-the
[18] Klein, G. et al., “seL4: Formal Verification of an OS Kernel,” ACM SOSP, 2009. https://www.sigops.org/s/conferences/sosp/2009/papers/klein-sosp09.pdf
[19] Klein, G. et al., “Comprehensive Formal Verification of an OS Microkernel,” ACM TOCS, 2014. https://sel4.systems/Research/pdfs/comprehensive-formal-verification-os-microkernel.pdf
[20] Cheng, R. et al., “Preserving Privacy in Mobile Spatial Computing,” NOSSDAV, 2022. https://felixshing.github.io/papers/NOSSDAV_2022_Privacy.pdf
[21] Springer, “A Homomorphic Encryption Based Location Privacy Preservation Scheme,” 2022. https://www.springerprofessional.de/en/a-homomorphic-encryption-based-location-privacy-preservation-sch/23169818
[22] Demmler, D. et al., “Faster Privacy-Preserving Location Proximity Schemes,” TU Darmstadt. https://encrypto.de/papers/JKSTY18.pdf
[23] Huang, M. et al., “Privacy-Preserving Task Assignment for Fully Distributed Mobile Crowdsensing,” IEEE IoT Journal, 2021. https://cse.hkust.edu.hk/~weiwa/papers/mingzhe-iot-j21.pdf
[24] Has-Needs, “Features.md: Transaction State, Smart Contract Conditions,” internal document, 2026.
[25] Mazzoleni, P. et al., “Privacy-Preserving Smart Contracts for Permissioned Blockchains,” arXiv, 2025. https://arxiv.org/abs/2501.03391
[26] Bonneau, J. et al., “Escrow protocols for cryptocurrencies: How to buy physical goods using Bitcoin,” Financial Cryptography, 2017. https://jbonneau.com/doc/GBGN17-FC-physical_escrow.pdf
[27] LSEO, “Mastering Semantic Triples for Machine Comprehension,” 2026. https://lseo.com/join-lseo/mastering-semantic-triples-for-machine-comprehension/
[28] Seale, T., “How triples power knowledge graphs and AI,” LinkedIn, 2025. https://www.linkedin.com/posts/tonyseale_one-of-the-simplest-yet-most-powerful-ways-activity-7301164277233577985-asm7
[29] DXOS, official site. https://www.dxos.org
[30] DXOS, “How local-first multiplayer works in DXOS apps,” DXOS Blog, 2024. https://blog.dxos.org/how-local-first-multiplayer-works-in-dxos-apps/
[31] Protocol Labs, “Advancing IPFS and libp2p Governance,” 2023. https://www.protocol.ai/blog/advancing-ipfs-and-libp2p-governance/
[32] CRDT.tech, “About Conflict-free Replicated Data Types.” https://crdt.tech
[33] Third Bit, “Conflict-Free Replicated Data Types.” https://third-bit.com/dsdx/crdt/

Why Every Attempt to Build Humanitarian Mapping Has Failed the Same Way — and Why Has-Needs Doesn’t

A rigorous, evidence-anchored analysis of every major humanitarian mapping initiative shows each one has failed at the same structural point — this is why Has-Needs produces pristine, real-time, self-sustaining geographic data as an emergent property of participation rather than as a design objective.

The Prize Everyone Is Chasing

Every UN agency, UNHCR operation, FEMA deployment, and humanitarian NGO shares a single desperate data need: GIS-located, secure, provenanced, reliable, multi-source-verified information that is directly beneficial to the stakeholders who provided it.

This is sometimes called “pristine data” in the field. It is the gold standard because it is simultaneously:

Geospatially precise — you know where the need or resource is
Timely — it reflects current conditions, not last week’s survey
Verified — it has been confirmed by more than one source
Provenanced — you know who declared it, when, and under what conditions
Actionable — it can be immediately matched to a response
Beneficial to its source — the person who provided it gains something from providing it

That last criterion is the one every existing system fails. And it is the one that determines whether you get the data at all.

Why Maps Work: The UN/UNHCR Case

The reason UN agencies, UNHCR, OCHA, and the Red Cross have invested heavily in map-based interfaces is well-founded. Spatial reasoning — “I am here, the need is there, the resource is here” — is among the most universally accessible cognitive operations available across languages, literacy levels, and cultures.[1] A person who cannot read English, French, or Arabic can still point to a location on a map. A child can do it. An elderly person who has never used a smartphone can do it with minimal guidance.

The HeiGIT group at Heidelberg University documents that geoinformation is now recognized as foundational humanitarian infrastructure: “Maps and geographic information systems help humanitarian organizations plan logistics routes, identify vulnerable populations, coordinate relief efforts, and monitor ongoing situations.”[2] OCHA’s Centre for Humanitarian Data has made geospatial data a core pillar of its humanitarian data standards — its 2022 geospatial strategy and 2023 enterprise agreement with Esri reflect a recognition that location-tagged information is orders of magnitude more actionable than unlocated reports.[3][4]

The theory is correct. The execution model is where every major initiative has broken down.

How MapKibera Proved the Theory and the Problem Simultaneously

MapKibera launched in October 2009 as a pioneering effort to put Nairobi’s Kibera settlement — home to hundreds of thousands of people and essentially absent from official maps — onto OpenStreetMap.[5][6] The project was genuinely groundbreaking: it demonstrated that community members in an informal settlement could be trained to map their own environment, producing data of higher accuracy and relevance than any external survey had achieved.[7]

The project succeeded in producing a map. It did not succeed in producing a self-sustaining data ecosystem.

The structural problem was the same one that defeats every training-dependent participatory mapping effort: you have to recruit mappers, train them, sustain their motivation, replace them when they leave, and continuously validate their output.[6] In Kibera, trained mappers remained the bottleneck. When funding cycles ended, mapping activity dropped. When trained individuals moved on, the knowledge did not transfer automatically. A notable consequence documented even within the project was that mappers had to be paid — the nature of mapping work as “voluntary” was directly resisted by participants who sought recognition for their time and effort.[7]

The 2024 State of the Map session “Mapping Kenya: 15 Years of Map Kibera and beyond” acknowledged the project’s ongoing struggle to maintain active contributor pipelines — fifteen years after launch, the fundamental recruitment and retention problem remained unsolved.[8] MapKibera proved that community members can produce high-quality, locally relevant geographic data. It did not solve the question of why they would continue doing so without external support and training — because the data they produced was not directly, immediately beneficial to themselves.

How OpenStreetMap Demonstrates the Validation Tax

OpenStreetMap is the most successful volunteer geographic data project in history. It has produced a genuinely global, genuinely useful map that powers applications from Uber to UN logistics operations.[2] It remains actively maintained by a hobbyist and professional contributor community.

It is also a model that cannot scale to the speed, volume, or specificity that humanitarian response requires — for a structural reason: every input requires validation.

The HOT Tasking Manager’s own documentation is explicit: “Validation is the process of a second mapper reviewing the mapping of the initial mapper of a task… Fundamentally it involves more experienced mappers checking the contributions of other volunteers to ensure that the OSM data is complete, accurate and meets the OSM features and tagging requirements.”[9][10] The system requires experienced validators to review the work of less experienced mappers, creating a permanent bottleneck: as contributor volume increases, validation demand increases proportionally, and the pool of qualified validators is always smaller than the pool of contributors.[11]

The consequence for humanitarian use is a structural lag: data produced in an active disaster may not be validated and therefore not trustworthy enough for operational use until hours or days after it was collected. The deeper problem is that as HOT shifted toward satellite and social media imagery tagging, it moved further from ground truth rather than closer to it. Remote mappers tagging satellite imagery from the Global North are producing data about places they have never been, of conditions they cannot verify, at a resolution that cannot distinguish a functional water point from an abandoned one.

Ushahidi: The Right Idea, the Wrong Execution Model

Ushahidi launched in 2008 in response to Kenya’s post-election violence, allowing citizens to report incidents via SMS and web, geolocated on a public map.[12] It was a genuine innovation: crowdsourced, real-time, citizen-generated crisis reporting at a moment when nothing like it existed. It was deployed in Haiti (2010), Libya (2011), and dozens of subsequent crises.

Ushahidi’s core insight — that the people experiencing a crisis are the best source of information about it — was correct. Its execution model had three structural problems that have become more rather than less limiting over time:

Report-centric, not needs-and-haves-centric. Ushahidi collects incident reports, not declarations of need or offers of resources. It tells you what happened; it does not match what people have with what people need. The data is informational, not operational.
Requires active deployment and administration. Each use requires someone to set up an instance, manage the incoming data stream, moderate content, and produce actionable outputs. This is significant overhead that limits deployment to well-resourced organizations.[13]
No inherent benefit to the reporter. A person who reports a crisis incident through Ushahidi receives nothing in return. The data flows to the platform and the organizations that use it; the reporter is a data source, not a participant. There is no receipt chain, no matching, no sovereign record.

By the mid-2010s, Ushahidi had largely retreated from active disaster deployment into a platform-as-a-service model for NGOs and election monitoring. Its 2023 annual report explicitly reframes its positioning as a “data company” focused on platform subscriptions and organizational clients rather than mass citizen participation in crisis response.[14] The Haiti and Libya deployments that made it famous have not been replicated at comparable scale.

Hivemapper: What Participatory Data Collection Looks Like When It Works

Hivemapper is a decentralized mapping network that pays contributors in HONEY tokens for dashcam footage collected during normal driving. Contributors install a dashcam, drive their normal routes, and the network processes the footage into continuously updated map data. By March 2023, the network had mapped over 1 million unique kilometers — 5x faster than Google Street View had captured equivalent coverage in the same period in many markets.[15]

The reason Hivemapper works where MapKibera stalled and OpenStreetMap validation-taxes itself into bottlenecks is structural, not motivational:[16][17]

No training required. You mount a camera and drive. The contribution behavior is already part of normal life.
No validation overhead for the contributor. The network’s AI and consensus mechanisms handle data quality assessment.
Direct benefit to the contributor. Every kilometer mapped earns tokens. The data you produce is immediately valuable to you.
Scale compounds rather than bottlenecks. More contributors means more coverage, not more validation burden.

Hivemapper does not produce the specific kind of data humanitarian response needs — it produces street-level imagery, not needs-and-haves declarations. But it proves the participation model that Has-Needs applies to humanitarian coordination: when contribution is a natural behavior that benefits the contributor directly, you get scale, quality, and self-sustaining participation without training anyone.[15]

What Has-Needs Does That No Mapping Project Has Done

Has-Needs does not require anyone to be trained as a mapper. It does not require anyone to do anything they would not do anyway in a crisis: declare what they have, declare what they need, and say where they are.

The map interface in Has-Needs is not a data collection tool for external use. It is the participant’s own view of their own situation and the situations of people around them. Placing a pin is not a contribution to a database — it is the act of asking for help or offering it. The motivation is intrinsic and immediate: you declare your need because you want it met. You declare your have because you want it matched. The data quality follows automatically from the motivation.

This produces exactly the “pristine data” that every humanitarian system craves, as an emergent property of participation while protecting privacy and sovereignty:

Data Quality Criterion	Current Mapping Approaches	Has-Needs
GIS-located	Yes, but requires trained mappers or satellite interpretation	Yes — placing a pin is the act of participation
Timely	Lagged by training, deployment, and validation cycles	Real-time — declared at the moment of need
Verified	Requires separate validation layer; bottleneck at scale [9][10]	Multi-source verification emerges from match confirmation by both parties
Provenanced	Partial — contributor accounts exist but not sovereign identity	Full — anchored to sovereign identity receipt chain
Actionable	Informational only; no matching mechanism [12][13]	Operationally matched — need meets have directly
Beneficial to source	None — contributor is a data donor [6][7]	Direct — your need gets met, your have gets matched
Safe	Location data is exposed	All location data is obscured through homomorphic encryption, assuring privacy and searchability

The data is high quality because the person who produced it had an immediate personal stake in its accuracy. You do not lie about where you are when you are asking for help. You do not misrepresent what you have when you want it matched to someone who needs it. The incentive structure produces data integrity without a validation layer.

The Humanitarian Aid Data Crisis and the Has-Needs Solution

The 2025 humanitarian funding crash — documented by CFR as “the Great Aid Recession” — makes this argument existential rather than theoretical.[18] The US cut nearly 5,800 foreign aid awards totaling $54 billion, a 92 percent reduction, under an executive order signed in January 2025.[19] US humanitarian support fell from approximately $14 billion to $3.7 billion in a single year; WHO estimates foreign aid for global health shrank 30 percent from 2023 to 2025, disrupting services at 5,687 health facilities across 20 crisis settings.[20]

When the budget for hiring mappers, training community data collectors, and running HOT tasking sessions disappears, the entire model of externally-funded participatory mapping collapses. HOT, Ushahidi, and MapKibera all depend on humanitarian funding to generate their data — and that funding is now in structural retreat with no clear recovery path.[18][20]

Has-Needs does not depend on humanitarian funding to generate data. It generates data because participants need the data to get their own needs met. The funding crisis that is currently forcing externally-funded mapping projects to scale back or restructure is irrelevant to Has-Needs’ data generation model — because Has-Needs does not pay anyone to collect data. The data collection is the mutual aid itself.

The Meta-Claim: The Mapper Was Always the Wrong Unit

Every humanitarian mapping initiative of the past twenty years has made the same foundational error: treating the mapper as the unit of participation rather than the person with a need or a have.

MapKibera trained mappers.[5][6] OpenStreetMap recruited mappers.[9] HOT organized remote mappers.[11] Ushahidi solicited reporters.[12] All of them were asking people to do something extra — to contribute data to a system that served someone else — and then wondering why participation was hard to sustain.

Has-Needs asks people to do one thing: tell the system what they have and what they need. That is not an extra task. It is the reason they are using the system. The map is not the product. The match is the product. The map is just the most natural interface for declaring your position in a situation.[1]

When the unit of participation is the person with a need, you never run out of participants. When their contribution directly benefits them, you never have a motivation problem. When the match confirmation serves as mutual verification, you never have a validation bottleneck.[15][9]

The data you get is the most pristine data available: real-time, geolocated, provenanced, multi-source verified, and produced by the only people who could possibly know whether it is accurate — the people living it, who are architecturally prevented from creating false data.

Sources
[1] Uttal, D., “Map Use and the Development of Spatial Cognition,” University of Chicago, 1999. https://groups.psych.northwestern.edu/uttal/documents/uttal2000.pdf
[2] HeiGIT, “Geoinformation for Humanitarian Aid,” Heidelberg Institute for Geoinformation Technology, 2026. https://heigit.org/geoinformation-for-humanitarian-aid/
[3] OCHA Centre for Humanitarian Data, “Geospatial Data and GIS — Learning Path,” 2022. https://centre.humdata.org/learning-path/an-introduction-to-geospatial-data/geospatial-data-geographic-information-systems/
[4] Esri, “Enterprise GIS Unifies Workflows for UN’s Humanitarian Aid Coordinators,” ArcNews, 2026. https://www.esri.com/about/newsroom/arcnews/enterprise-gis-unifies-workflows-for-uns-humanitarian-aid-coordinators
[5] OpenStreetMap 20th Birthday Archive, “Map Kibera and OpenStreetMap,” 2009. https://birthday20.openstreetmap.org/timeline/2009-map-kibera-and-openstreetmap/
[6] Participedia, “Map Kibera,” Case Study, 2021. https://participedia.net/case/7878
[7] GFDRR, “Getting on the Map: A Community’s Path to Better Services,” World Bank, 2013. https://www.gfdrr.org/sites/default/files/documents/How%20to%20-%20interactive%20mapping.pdf
[8] Hagen, E. and Ogure, J., “Mapping Kenya: 15 Years of Map Kibera and beyond,” State of the Map 2024. https://media.ccc.de/v/sotm2024-53434-mapping-kenya-15-years-of-map-kibera-and-beyond
[9] OpenStreetMap Wiki, “Tasking Manager/Validating data,” 2025. https://wiki.openstreetmap.org/wiki/Tasking_Manager/Validating_data
[10] HOT Tasking Manager, “Validation,” GitHub Pages. https://hotosm.github.io/tasking-manager/validation/
[11] HOT Toolbox, “Working with Tasking Manager,” Humanitarian OpenStreetMap Team. https://toolbox.hotosm.org/pages/3_participatory_osm/3_4_working_with_tasking_manager/
[12] Goldstein, J. and Rotich, J., “Digitally Networked Technology in Kenya’s 2007-2008 Post-Election Crisis,” MobileActive, 2008. https://www.mobileactive.org/research/digitally-networked-technology-kenyas-2007-2008-post-election-crisis/
[13] FitGap, “Ushahidi Reviews 2025.” https://us.fitgap.com/products/004864/ushahidi
[14] Ushahidi, “2023 Annual Report,” 2024. https://www.ushahidi.com/about/blog/2023-annual-report/
[15] Hivemapper, “Hivemapper Mapped 1 Million Unique Kilometers,” Hivemapper Blog, March 2023. https://blog.hivemapper.com/hivemapper-mapped-1-million-unique-kilometers-3e0a1b6db1b8
[16] Hivemapper, “What Is HONEY?,” Hivemapper Docs, 2025. https://docs.hivemapper.com/honey-token/what-is-honey
[17] Gate.com, “A Deep Dive into the DePIN Project Hivemapper,” 2024. https://www.gate.com/learn/articles/a-deep-dive-into-the-depin-project-hivemapper/1876
[18] Council on Foreign Relations, “The Great Aid Recession: 2025’s Humanitarian Crash in Nine Charts,” December 2025. https://www.cfr.org/articles/great-aid-recession-2025s-humanitarian-crash-nine-charts
[19] Al Jazeera, “US cutting foreign aid budgets by more than 90%, Trump administration says,” February 2025. https://www.aljazeera.com/economy/2025/2/27/us-cutting-foreign-aid-budgets-by-more-than-90-trump-administration-says
[20] Refugees International, “A Generational Collapse: Tracking the Toll of Trump’s Humanitarian Aid Cuts,” February 2026. https://www.refugeesinternational.org/reports-briefs/a-generational-collapse-tracking-the-toll-of-trumps-humanitarian-aid-cuts/
[21] HeiGIT / GIS Resources, “New Global Satellite Resource to Support Humanitarian Navigation and Infrastructure Tracking,” 2025. https://gisresources.com/new-global-satellite-resource-to-support-humanitarian-navigation-and-infrastructure-tracking/
[22] Mapping Change — Map Kibera, MIT Press Innovations, Vol. 6 No. 1. https://direct.mit.edu/itgg/article-pdf/6/1/69/1626156/inov_a_00059.pdf

How a Sovereignty-First Architecture Interrupts Trauma Formation Before, During, and After Disaster — With Measurable Outcomes

The relationship between Has-Needs and trauma is not incidental. The protocol was designed from the ground up with the psychological reality of disaster survivors as a primary constraint. This section makes the case that Has-Needs is the first coordination system to address trauma formation at the architectural level — producing measurable improvements in individual agency, community social capital, and post-event collective resilience as natural byproducts of its normal operation.

Part 1 — The Mechanism: What Causes Disaster Trauma

Helplessness as the Pathological Core

The clinical literature is unambiguous about the central mechanism of disaster-related trauma: it is not the severity of the event but the perception of uncontrollability that determines whether exposure produces lasting psychological damage. Seligman’s foundational research on learned helplessness established that subjects exposed to repeated uncontrollable stressors develop not just a behavioral response of passivity, but a generalized cognitive expectation that their actions cannot influence outcomes — an expectation that persists even when circumstances change and control becomes possible.[1][2] The result is decreased motivation, impaired learning from success, and “a self-perpetuating cycle where the perception of lack of control leads to cognitive distortions which, in turn, reinforce the helpless behaviour.”[1]

The neurobiological correlates are equally well-documented. Uncontrollable stress activates the hypothalamic-pituitary-adrenal (HPA) axis, producing elevated cortisol that is specifically and reproducibly linked to the helplessness condition rather than to the pain or threat level of the stressor itself. Research comparing controllable and uncontrollable stress exposures found “significantly higher pain perception and helplessness ratings as well as a significantly more pronounced salivary cortisol response” under uncontrollable conditions — and identified “perceived controllability of painful stimuli” as the crucial factor for both pain perception and HPA axis activation.[3] A 2026 meta-analysis confirmed that perceived control functions as a measurable resilience factor with direct neural and physiological correlates.[4]

Bessel van der Kolk’s clinical work adds the somatic dimension: trauma is not just a cognitive event. When the threat-perception system of the brain registers uncontrollability, the body responds with a cascade — elevated heart rate, disrupted digestion, eventual immobilization — that becomes encoded as a somatic pattern independent of conscious memory.[5][6] “Reliving trauma shuts down people’s ability to express what they are experiencing in words,” precisely because the somatic response is activating neural systems that precede language.[6] Recovery from trauma therefore requires not just cognitive reframing but the restoration of the body’s sense that it can act, and that actions matter.

Has-Needs addresses this at the architectural level. The Working state visibility chain — the Brown-to-Green progression showing that a Need is accepted, assigned, in progress, awaiting resources — is not a UX feature. It is a direct intervention against the learned helplessness mechanism. The user does not wonder whether anyone received their report, whether anyone is coming, or whether they have been forgotten. They see, in real time, who holds their Need, what stage it is at, and what is preventing resolution. The psychological effect is the opposite of helplessness: the situation is unfolding visibly, actions are producing traceable consequences, and the individual is not passive.[7]

The SAMHSA Framework: Has-Needs as Trauma-Informed Architecture

SAMHSA’s six principles of trauma-informed care — Safety, Trustworthiness and Transparency, Peer Support, Collaboration and Mutuality, Empowerment/Voice/Choice, and Cultural Sensitivity — were developed as guidance for organizations and programs.[8][9] Has-Needs does not implement these as program policies. It implements them as protocol properties:

Safety: the Persona Manager and HE location layer ensure physical location is never disclosed; the blind matching protocol ensures no contact without mutual consent
Trustworthiness and Transparency: every transaction is a visible, hash-verified receipt; no action occurs without a signed chain entry; the responsiveness metric makes institutional behavior observable
Peer Support: the mutual aid model makes every user simultaneously a provider and a recipient; the stigmatizing division between “aid recipient” and “service provider” is structurally eliminated
Collaboration and Mutuality: matching requires bilateral consent; no exchange can be imposed
Empowerment, Voice, and Choice: declarations originate from the Sovereign Being; needs are stated by the person who has them, not inferred by an institution; every filter has a visibility mode preserving user agency over their own information environment
Cultural Sensitivity: the emergent ontology preserves linguistic and cultural context without external translation; communities define their own categories[8][9][10]

SAMHSA’s framework describes what organizations should aspire to. Has-Needs instantiates it as a non-negotiable property of the data structure.

Part 2 — Before the Event: Social Capital as the Primary Resilience Variable

What Predicts Survival and Recovery

The most important finding in the disaster resilience literature is also the most consistently ignored in disaster preparedness policy: the primary predictor of community recovery after a disaster is not the amount of aid received, the level of damage, or the quality of government response — it is the pre-existing density of social connections.

Daniel Aldrich’s research across four major disasters — Japan’s 1995 Kobe earthquake, the 2004 Indian Ocean tsunami, the 2005 Katrina floods, and the 2011 Great East Japan earthquake — established this finding with multivariate rigor: “Recovery from natural and other disasters does not depend on the overall amount of aid received nor on the amount of damage done by the disaster; instead, communities with more trust, civic engagement, and stronger networks can better bounce back after a crisis than fragmented, isolated ones.”[11][12] Specifically, controlling for demographics, damage level, and economic resources, communities with higher social capital showed lower mortality rates, faster population return, and faster economic recovery.[13] The mechanism is clear: “disaster resilience comes from internal factors: How connected are we? How much trust do we have in each other? How often do we work together?”[13]

A growing body of subsequent research confirms and extends this finding across bond social capital (tight-knit groups), bridging social capital (connections across different groups), and linking social capital (connections to institutional resources). The community with diverse, dense social networks has distributed access to information, skills, physical resources, and emotional support that no centralized aid system can replicate — and it activates that access without waiting for institutional permission.[14]

Has-Needs builds social capital as a direct byproduct of everyday mutual aid use. Every completed exchange is a bilateral receipt that records a connection, deepens an ontology node, and adds a hop to the chain-hopping verification graph. A community that has been using Has-Needs through a drought, a mutual aid project, and a supply disruption enters the next emergency with a richer, denser, more verified social graph than one that has not. The disaster preparedness investment is not a separate program or training requirement — it is the accumulation of normal, everyday, self-interested mutual aid activity, recorded permanently on individual chains.

Part 3 — During the Event: Preserving Agency Under Maximum Stress

The Working State as Agency Infrastructure

The critical window for trauma formation is the peritraumatic period — the hours and days during which the event is unfolding and the individual’s nervous system is assessing whether their actions can influence outcomes.[3][5] This is precisely when existing coordination systems fail most completely: dispatch systems are overwhelmed, status queries cannot be answered, volunteers are misallocated, and the person who submitted a need has no way to know whether anyone received it. The result is not just operational inefficiency — it is the systematic production of the uncontrollability perception that Seligman, van der Kolk, and the broader trauma literature identify as the primary pathogenic mechanism.[1][5][6]

The Working state visibility chain is the Has-Needs response to this failure. When a Need is accepted by any party — government, volunteer, peer, community organization — the declaring Being immediately sees the confirmation, the accepting party’s identity, and the status as it progresses. When the Field Team arrives on site, that status update appears. When they are waiting for equipment, that delay is visible and explained. The user does not call City Hall. They do not wonder whether they have been forgotten. Their anxiety is not suppressed by a policy — it is reduced by the architectural fact that silence is impossible in a Working state.[7]

Dr. Diamond’s Katrina experience provides the ground-level evidence for why this matters at scale. He came home from the Convention Center asking why some people became Thrivers rather than victims — and found that agency, connection, and the sense that one’s actions matter were the distinguishing variables.[15][16] Has-Needs provides those variables at the protocol level, for every user with a device, continuously throughout the event.

Peer Support as First-Line Response

The research on spontaneous volunteer networks — Occupy Sandy, People’s Relief, the Red Hook Initiative — consistently shows that peer-organized mutual aid reaches affected populations before formal institutional response, operates with less overhead, and produces stronger social capital reinforcement precisely because the exchanges are reciprocal rather than charitable.[17] Has-Needs is the structured layer these improvised networks were trying to be. The peer support principle is not implemented as a program feature — it is the default operating mode of the protocol, because every user simultaneously has Needs and Has declarations, and matching is peer-to-peer by design.

Part 4 — After the Event: The Receipt Chain as Collective Healing Artifact

Shared Narrative as Social Capital

Research on post-disaster community recovery identifies collective narrative – a shared, coherent account of what happened, who helped, and how the community responded, is a critical mechanism for both individual healing and community cohesion. Post-Katrina research in St. Bernard Parish found that a shared community identity as “a close-knit, family-oriented community of hard workers” directly shaped recovery strategy, producing self-reliance and faster return rates than demographically comparable communities without a coherent shared narrative.[18][19] Storytelling is not a soft supplement to recovery; it is “a strategic tool for recovery and resilience” that “transforms the recovery process into a journey of empowerment and collective action.”[20]

The Has-Needs receipt chain generates this artifact automatically. Every completed exchange is a permanent, cryptographically verified record of who helped whom, what was exchanged, what was promised, and what was delivered. After the event, a community’s aggregate exchange graph is a verifiable, fact-based account of its own competence and reciprocity. This is not a survey conducted after the fact, not a journalist’s reconstruction, not an institutional narrative authored by an agency that wants to emphasize its role. It is the facts, signed by the parties, in the order they happened — the most powerful possible counter-narrative to victimhood, helplessness, and institutional dependence.

Emergent Leadership vs. Self-Declared Local Actors

The post-disaster environment is consistently documented as vulnerable to aid diversion by self-declared local authorities — individuals who fill coordination vacuums, claim community leadership roles, and redirect resources toward patronage networks rather than genuine need.[21] This is a documented pattern in humanitarian response in Haiti, the Philippines, and post-Katrina New Orleans, among many other events. It is not a character failure — it is a predictable consequence of coordination vacuums in high-stress, low-information environments.

Has-Needs eliminates the information conditions that make this possible. Community leadership is not self-declared in a Has-Needs environment — it emerges from exchange history. The individuals and organizations with the most completed exchanges, the most verified connections across the community graph, the most diverse and active Has declarations, are visible as de facto coordinators and connectors through the normal operation of the protocol. No announcement is needed. No authority is claimed. The receipt chain is the evidence, and the community can see it.

Part 5 — Measurable Outcomes

Has-Needs does not require new measurement instruments. It generates trauma-relevant metrics as a natural byproduct of operation:

Pre-event social capital density: Exchange graph density — the number of completed bilateral exchanges per capita in a defined community — is a direct proxy for Aldrich’s social capital measures (trust, civic engagement, network strength). Communities can compare their pre-event exchange density against post-event recovery metrics to build an evidence base for what level of mutual aid activity predicts resilience.[11][12]

Peritraumatic agency preservation: Working state resolution time — time from Need declaration to Working state initiation — measures how quickly the protocol converts perceived uncontrollability into visible agency. The Brown-to-Green progression is itself a measurable variable: what percentage of Needs reach Green status within one hour, four hours, twelve hours? That metric directly indexes the failure mode documented in every major disaster after-action report.[7]

Workforce burnout reduction: The literature on emergency management workforce crisis documents that high workload and ambiguous status are the primary burnout mechanisms.[22] Working state transparency eliminates the status-query loop — the repeat calls, the transferred inquiries, the “let me check” chain — that accounts for a significant fraction of emergency management cognitive load. Reduced status-query volume is directly measurable in communication log data.

Post-event community competence narrative: The aggregate exchange graph from an event is a permanent, verifiable record of community-level mutual aid volume, resource distribution, and peer-to-peer coordination. This is the first time this data has ever been available in a form that is not constructed post-hoc by an institution with an interest in the narrative.

Conclusion: Trauma-Informed at the Protocol Level

Has-Needs is the first coordination system in which the six SAMHSA trauma-informed care principles are architectural properties rather than organizational aspirations. The first system in which the Seligman controllability finding — that perceived control is the primary determinant of whether stress produces lasting damage — is implemented as a data structure. The first system in which Aldrich’s social capital research — that connection density predicts recovery outcomes — is built by design into everyday operation.

The result is a system that does not merely avoid causing harm. It actively, measurably, structurally reduces the conditions that produce harm — before the event, during it, and in the community that remains when it is over.

Sources
[1] NDP Psychology, “Martin Seligman’s Theory of Learned Helplessness: Implications for Motivation.” https://ndpsych.com.au/martin-seligmans-theory-of-learned-helplessness-implications-for-motivation/
[2] Simply Psychology, “Learned Helplessness: Seligman’s Theory of Depression,” 2024. https://www.simplypsychology.org/learned-helplessness.html
[3] Wiech, K. et al., “Helplessness and perceived pain intensity: relations to cortisol and HPA-axis activation,” PMC, 2011. https://pmc.ncbi.nlm.nih.gov/articles/PMC3141369/
[4] PMC, “Perceived control as a resilience factor: associations with neural and physiological markers,” 2026. https://pmc.ncbi.nlm.nih.gov/articles/PMC12417506/
[5] van der Kolk, B., The Body Keeps the Score: Brain, Mind, and Body in the Healing of Trauma, Viking, 2014. Summary: https://www.simplypsychology.org/the-body-keeps-the-score-summary.html
[6] Forte Labs, “The Body Keeps the Score Summary,” 2019. https://fortelabs.com/blog/the-body-keeps-the-score-summary/
[7] Has-Needs, “Has-Needs-Comprehensive-Blueprint3: Working State, Situational Awareness,” internal document, 2026.
[8] SAMHSA, “Infographic: 6 Guiding Principles to a Trauma-Informed Approach,” 2025. https://www.samhsa.gov/resource/dbhis/infographic-6-guiding-principles-trauma-informed-approach
[9] SAMHSA, “Trauma-Informed Approaches and Programs,” 2024. https://www.samhsa.gov/mental-health/trauma-violence/trauma-informed-approaches-programs
[10] Pathways RTC, “SAMHSA’s Concept of Trauma and Guidance,” 2015. https://www.pathwaysrtc.pdx.edu/focal-point-S1510
[11] Aldrich, D., “Fixing Recovery: Social Capital in Post-Crisis Resilience,” Purdue University. https://docs.lib.purdue.edu/context/pspubs/article/1002/viewcontent/Aldrich_Fixing_Recovery_Journal_of_Homeland_Security.pdf
[12] Tierney, K., “Only Connect! Social Capital, Resilience, and Recovery,” Risk, Hazards & Crisis in Public Policy, 2013. https://onlinelibrary.wiley.com/doi/abs/10.1002/rhc3.20
[13] Aldrich, D., “Social Capital in Disaster Mitigation and Recovery,” FEMA PrepTalk, 2020. https://www.youtube.com/watch?v=z7A8m0zQ6T8
[14] Kyne, D. and Aldrich, D., “Capturing Bonding, Bridging, and Linking Social Capital through Disaster Recovery,” Oregon State University. http://explorer.bee.oregonstate.edu/Topic/InfluenceNetworks/Documents/Kyne_Aldrich_2019.pdf
[15] Diamond, D., Faculty Bio, American Association of Physician Leaders. https://www.physicianleaders.org/faculty/bio/dan-diamond
[16] Diamond, D., Leadership page. https://www.dandiamondmd.com/leadership
[17] Has-Needs, “EFFICIENCY-has-needs.md: Supporting Self-Organizing Systems,” 2026. (Referencing NSF Hurricane Sandy research)
[18] Hawkins, R. and Maurer, K., “Social capital as collective narratives and post-disaster community recovery,” Mercatus Center / Wiley, 2011. https://www.mercatus.org/hayekprogram/research/journal-articles/social-capital-collective-narratives-and-post-disaster
[19] Academia.edu, “Social capital as collective narratives and post-disaster community recovery,” 2016. https://www.academia.edu/20174411/Social_capital_as_collective_narratives_and_post_disaster_community_recovery
[20] Public Works Partners, “The Role of Storytelling in Community Recovery and Resilience Building,” 2025. https://publicworkspartners.com/storytelling-framework-for-recovery-and-resilience-building/
[21] Has-Needs, “Has-Needs_Project.md: Emergent leadership vs. self-declared local actors,” internal document, 2026.
[22] Has-Needs, “EFFICIENCY-has-needs.md: Human Cost — Burnout and the Talent Drain,” 2026.

Has-Needs is the only system that makes agency an emergent property of use, not a therapeutic add-on.

“30–40% of direct disaster victims develop PTSD. The research identifies loss of agency — not injury or loss alone — as the core peritraumatic risk factor. Yet every current intervention attempts to restore agency after the event, in clinical settings, at individual scale.”[14][1][2][4]
“Has-needs makes agency emergent during the event: using the system is the act of self-determination. Sovereignty over data, declared needs and haves, and bidirectional situational awareness all produce the internal locus of control the literature identifies as the most critical PTSD protective factor — without a single therapy session.”[2][5][7]
“This is not a mental health tool. It is a governance and resource coordination architecture that produces mental health outcomes as an emergent property of its use — at mass scale, at the moment it matters.”[13][11]

What the PTSD Research Actually Shows:

Loss of agency is the core injury, not just a symptom

In disaster settings, the research draws a direct line between loss of agency and PTSD onset. Sixty percent of earthquake survivors reported helplessness as a peritraumatic response, simultaneously projecting all-powerful agency onto the event itself, feeling like “pawns” or “vegetables,” and experiencing what researchers call “psychological annihilation.” This is not metaphor: it is a documented, measurable shift in self-perception that is tightly coupled to PTSD trajectories.[1]

A systematic review across six major disaster types — earthquakes, hurricanes, wildfires, SARS, and fireworks explosions — confirmed that external locus of control is a direct predictor of PTSD while internal locus of control is the most important protective factor. The damage is not primarily from the event itself, but from the structural removal of the person’s capacity to act meaningfully within it.[2]

The five evidence-based recovery elements all point at agency

The National Center for PTSD’s framework of five evidence-informed early intervention elements are: promoting safety, promoting calming, promoting a sense of self- and community efficacy, promoting connectedness, and instilling hope. Three of the five are explicitly about restoring the capacity to act. The VA further documents that “coping self-efficacy — the belief in one’s ability to get through difficult times — is related to better mental health outcomes.”[3][4]

Perceived self-efficacy during the event, not just after, has measurable protective effects: survivors who saw themselves as efficacious at the time of the emergency had significantly fewer posttraumatic symptoms. This is the critical finding for Has-needs: the window for preventing PTSD is open during the event, and it is opened or closed by whether the person has meaningful action available to them.[5][6]

Preparedness and mental health are bidirectionally coupled

A randomized controlled trial in Haiti demonstrated that disaster preparedness and mental health symptoms co-mediate each other: improving preparedness reduced PTSD, depression, and anxiety, and reducing mental health burden increased preparedness behavior. In other words, giving people something to do that matters is itself a mental health intervention— and that effect runs in both directions.[7]

Participation empowers; exclusion re-traumatizes

Research on community participation in disaster risk reduction consistently shows that when people are actively engaged in designing, planning, and responding, they develop leadership capacity, efficacy, and resilience. Where participation is token or absent, recovery is slower, public uprising is documented, and communities remain brittle. The World Bank and SFDRR framework both call community agency a “key principle” of inclusive disaster risk management, yet 67% of disaster survivors studied were unaware they were even permitted to participate in planning.[8][9][10]

The enactive PTSD model: trauma as a breakdown of the sense of agency

A 2024 peer-reviewed perspective paper articulates the theoretical link precisely: “Trauma is viewed as a breakdown of the sense of agency, leading to a freeze response and dissociation, with peritraumatic dissociation increasing the risk of PTSD.” The authors propose an “enactive” perspective of PTSD, where therapy restores the sense of agency through direct engagement with body and environment — not through talk alone. This is the theoretical frame that Has-needs fits into at the systems level.[11][12]

The Has-Needs Claim: Agency as an Emergent Property of System Use

This is where Has-needs becomes uniquely powerful. Every intervention in the literature tries to restore agency therapeutically after the fact, in clinical settings, by individual providers, at scale-limited bandwidth. Has-needs does something none of them do:

During the event, using the system is itself an act of agency: you are declaring your needs, offering your haves, making choices about what you share and what you don’t.
Sovereignty is preserved structurally: your data does not belong to the incident command, the platform, or the vendor. That structural fact means you are not once again experiencing removal of control at the moment of greatest vulnerability.
Situational awareness becomes bidirectional: instead of the natural information-seeking colliding with command-and-control, it is channeled productively. You are not fighting the system; you are the system’s primary input.
Agency is emergent because it is not assigned, coached, or prescribed — it arises naturally from the act of participation in a sovereignty-respecting, needs-visible network.

No current therapeutic intervention, crowdsourcing platform, or disaster management framework achieves this combination because none of them treats the human as the base unit of value from the ground up.[4][13][1][2][7][11]

Sources
[1] Feelings, Thoughts, and Behaviors During Disaster – PMC https://pmc.ncbi.nlm.nih.gov/articles/PMC7753093/
[2] Exploring the impacts of perceived locus of control on post‐traumatic stress disorder among disaster survivors: A systematic review https://onlinelibrary.wiley.com/doi/full/10.1111/jpm.13030
[3] Effects of Disaster Events: Resilience and Risk Factors – PTSD.va.gov https://www.ptsd.va.gov/disaster_events/for_everyone/effects_de_risk_factors.asp
[4] Early Interventions Following Disaster Events – PTSD: National Center for … https://www.ptsd.va.gov/disaster_events/for_providers/early_intervention_tx.asp
[5] Perceived Self-efficacy during an Emergency Situation Reduces … https://www.cambridge.org/core/journals/spanish-journal-of-psychology/article/perceived-selfefficacy-during-an-emergency-situation-reduces-posttraumatic-stress-symptoms/9AAD401E9FC43D801E049BC0FBA8CBBE
[6] Perceived self-efficacy during an emergency situation reduces posttraumatic stress symptoms – PubMed https://pubmed.ncbi.nlm.nih.gov/24230919/
[7] Integrating mental health and disaster preparedness in intervention https://pmc.ncbi.nlm.nih.gov/articles/PMC7083573/
[8] The role of public participation in disaster risk reduction initiatives https://pmc.ncbi.nlm.nih.gov/articles/PMC8905445/
[9] [PDF] IMPORTANCE OF COMMUNITY PARTICIPATION IN DISASTER … https://salford-repository.worktribe.com/OutputFile/1492119
[10] Community Participation and Empowerment in a Post-disaster Environment: Differences Tied to Age and Personal Networks of Social Support https://pmc.ncbi.nlm.nih.gov/articles/PMC7399938/
[11] Enhancing Agency in Posttraumatic Stress Disorder Therapies Through … https://pmc.ncbi.nlm.nih.gov/articles/PMC11250045/
[12] Enhancing Agency in Posttraumatic Stress Disorder Therapies through … https://preprints.jmir.org/preprint/58390/accepted
[13] Community Participation and Citizen Engagement – GFDRR https://www.gfdrr.org/en/citizen-engagement
[14] Predicting Post-Disaster Post-Traumatic Stress Disorder Symptom … https://pmc.ncbi.nlm.nih.gov/articles/PMC11204121/
[15] The Impact of Disaster Events on Mental Health – PTSD: National … https://www.ptsd.va.gov/disaster_events/for_providers/mental_health_impact.asp
[16] Association between resilience, social support, and institutional trust … https://www.sciencedirect.com/science/article/abs/pii/S0883941722000012
[17] Psychosocial impacts of disasters: Resources for mitigation, response and recovery https://ncceh.ca/resources/subject-guides/psychosocial-impacts-disasters-resources-mitigation-response-and-recovery
[18] Psychosocial Impacts of Disaster https://dss.sd.gov/docs/behavioralhealth/bh_covid/Assisting_Community_Leaders_Psychosocial_Impacts_of_Disasters.pdf
[19] PTSD following a natural disaster – PTSD UK https://www.ptsduk.org/what-is-ptsd/causes-of-ptsd/natural-disaster/
[20] Examining a Comprehensive Model of Disaster-Related … – PMC – NIH https://pmc.ncbi.nlm.nih.gov/articles/PMC3490647/
[21] Pre-disaster social support is protective for onset of post-disaster depression: Prospective study from the Great East Japan Earthquake & Tsunami – Scientific Reports https://www.nature.com/articles/s41598-019-55953-7
[22] [PDF] Disaster mental health response – UNI ScholarWorks https://scholarworks.uni.edu/cgi/viewcontent.cgi?article=3538&context=grp
[23] Disaster mental health preparedness in the community https://pmc.ncbi.nlm.nih.gov/articles/PMC5489140/
[24] [PDF] Post-Traumatic Stress Disorder After Natural Disasters: A Review https://dergipark.org.tr/en/download/article-file/3061835
[25] Long-Term Treatment Interventions Following Disaster Events – PTSD https://www.ptsd.va.gov/disaster_events/for_providers/long_term_intervention_tx.asp
[26] Disaster Behavioral Health and Approaches to Community … https://www.samhsa.gov/sites/default/files/dtac-disaster-behavioral-health-approaches-to-community-response-recovery.pdf
[27] Role of Perceived Control in Coping with Disaster https://guilfordjournals.com/doi/pdf/10.1521/jscp.1989.8.4.376
[28] The mediating role of disaster response self-efficacy in the effect … https://pmc.ncbi.nlm.nih.gov/articles/PMC12243243/
[29] Intermediate Treatment Interventions Following Disaster Events – PTSD https://www.ptsd.va.gov/disaster_events/for_providers/intermediate_intervention_tx.asp
[30] The Role and Effectiveness of Remote Mental Health Interventions … https://pmc.ncbi.nlm.nih.gov/articles/PMC12835632/
[31] Are you prepared? Efficacy, contextual vulnerability, and … https://www.sciencedirect.com/science/article/abs/pii/S2212420922002916
[32] Mental health and psychosocial interventions to limit the adverse … https://www.sciencedirect.com/science/article/pii/S266660652200195X
[33] The role of response efficacy and self-efficacy in disaster preparedness … https://nhess.copernicus.org/articles/23/3789/2023/
[34] [PDF] Mental Health Intervention in the Event of a Disaster – CIDRAP https://www.cidrap.umn.edu/sites/default/files/php/223/223_guide.pdf
[35] The Role of Mindfulness and Embodiment in Group-Based … https://pacja.org.au/article/94979-the-role-of-mindfulness-and-embodiment-in-group-based-trauma-treatment
[36] Crowdsourced Community For Citizen Safety: Help & Alerts – Pubsafe https://pubsafe.net/role-of-crowdsourced-technology-in-disaster-response/
[37] Exploring the impacts of social media and crowdsourcing on … – PMC https://pmc.ncbi.nlm.nih.gov/articles/PMC10877096/
[38] How Trauma Therapy Can Help Individuals with PTSD https://www.thesupportivecare.com/blog/how-trauma-therapy-can-help-individuals-with-ptsd
[39] crowdSA – https://archiv.cis.jku.at/crowdsa.situation-awareness.net/html/PDFs/Proel_CrowdSA_SMERST2013.pdf
[40] Sensorimotor Psychotherapy and the Embodied Experience in Clinical … https://sensorimotorpsychotherapy.org/embodied-experience-clinical-practice/
[41] Crowdsourcing, citizen sensing and sensor web technologies for public and environmental health surveillance and crisis management: trends, OGC standards and application examples https://pmc.ncbi.nlm.nih.gov/articles/PMC3271966/
[42] Involving children in disaster risk reduction: the importance of … – PMC https://pmc.ncbi.nlm.nih.gov/articles/PMC5804784/
[43] crowdsourcing on disaster resilience[version 3; peer review https://links-project.eu/wp-content/uploads/2024/04/610e491e-111e-457d-b783-20ef7e902ff1_13721_-_antonio_opromolla_v3.pdf

Twelve prosocial ‘designed emergent’ features of Has-Needs

1. Personal needs met through collective behavior

Research on successive disasters shows that community-level resilience does not directly reduce PTSD and depression — it works by first building individual resilience, which then reduces adverse outcomes. In other words, the collective serves the personal, and the mechanism is participation, not charity. Has-needs operationalizes exactly this: collective visibility of needs and haves produces personal outcomes (your need gets met) without requiring central redistribution or formal aid apparatus.[1] Has-Needs makes collective participation the most efficient means to achieve personal goals, while providing opportunities for reciprocity.

2. Layered community autonomy and privacy

The humanitarian data sovereignty literature documents precisely the harm of the absence of this. Rohingya biometric data collected for aid was later used to identify and persecute people; Houthi and Ukraine data practices demonstrated the same pattern of “pseudo-sovereigns” — aid organizations, states, tech vendors — asserting competing authority over the most sensitive data of the world’s most vulnerable people. Has-needs addresses this with sovereignty as a primitive, not a policy layer. Layered community autonomy means a neighborhood can share internally without exposing data upward to a state or platform. No current system is designed this way from the ground up.[2][3][4]

3. Redemption

Community-led recovery research consistently shows that post-disaster environments create genuine openings for social and political transformation — not because disasters are good, but because normal hierarchies are disrupted and communities gain experimental room to reinvent relationships and roles. Has-needs gives a structural channel for that: a person who was previously a burden (pure needs) can become a resource (haves they didn’t know were valued), which is a socially legible act of redemption. This is not therapeutic framing; it is a structural consequence of making the full bidirectional ledger visible.[5]

4. Adjustable personal trust

The Signal Code (Harvard Humanitarian Initiative) identifies five rights pertaining to information in crisis, grounded in international human rights law, including the right to control how one’s data is used and shared. Current systems do not implement granular, user-controlled trust tiers. Has-needs’ adjustable trust allows someone who trusts their immediate block but not the county coordination center to still participate meaningfully — a design choice that directly addresses the documented harm of coerced data disclosure in humanitarian contexts.[3][6]

5. Anonymous need/resource matching

Anonymous peer behavior is powerfully contagious. When college students saw anonymous peers acting prosocially, it was a significant independent predictor of their own prosocial behavior — even controlling for empathy and personal values — and critically, none of the participants identified peer influence as their reason for giving. This is the anonymity paradox: removing identity reduces the risk of stigma or exploitation, and simultaneously increases prosocial contagion. Has-needs matches needs and haves anonymously at the matching layer while still maintaining enough verified metadata to prevent gaming — a combination no current aid or marketplace platform achieves.[7][8]

6. Safe AI

The “Reclaiming AI” paper in the Good Theory issue argues directly that AI as engineering (build things that work) has been confused with AI as theoretical tool (use AI to understand systems and test hypotheses). Has-needs’ safe AI layer is consistent with this: the AI serves the human’s declared frame of reference (their stated needs, haves, and trust levels) rather than optimizing against an external objective function the human never consented to. The sovereignty architecture makes the AI’s scope of action structurally bounded — it cannot generalize outside what the human has authorized and becomes dependent upon human intelligence to function.[9]

7. Situation-dependent metrics

This is one of the most rigorous claims available. Field et al. in the Good Theory issue demonstrate that whether unreproducible or imperfect evidence is “bad” for a theory depends entirely on what the theory is trying to do — explanation, prediction, or unification. The same logic applies to metrics: a “good” metric in normal operations (throughput, cost per unit) is a catastrophically wrong metric in disaster (survival, reunification, dignity, speed of need-meeting). Has-needs’ situation-dependent metrics are not a feature — they are a fundamental theoretical requirement for any system that claims to serve human needs rather than institutional accounting.[9]

8. Governance accountability

Public participation research following Hurricane Ike and Galveston found that post-disaster participatory processes were undermined primarily by homogeneity of participants, skipped deliberation, and exclusion of marginalized groups — even when governments intended inclusivity. Has-needs’ governance accountability layer makes this structural rather than dependent on institutional goodwill: every resource commitment, matching decision, and flow is logged in individual sovereignty-preserving ledgers, meaning accountability is not requested from the top — it is an emergent property of the architecture.[10] Users are then able to expose the number of Needs that have not been responded to and the entity that accepted responsibility. As a publicly owned metric, exposure can guide future voting decisions.

9. Direct participation and democratization

67% of disaster survivors in one major study were unaware they were permitted to participate in planning. The same literature shows that when participation is genuine, it produces leadership capacity, community cohesion, and faster recovery. Asynchronous, low-barrier participation — the kind Has-needs enables — is critical because post-disaster environments make synchronous, meeting-based participation almost impossible for the most affected people.[11][12][10] Community priorities are expressed as a stream of requests that sidestep bureaucratic meeting-based schedules in favor of live sentiment expression.

10. Asynchronous parallel recovery

Individual and community resilience function in tandem, not sequentially — activating them simultaneously produces the best mental health outcomes. Current systems force serial recovery: you wait for the official recovery plan, then you participate, then you rebuild. Has-needs enables parallel recovery because every household, block, and neighborhood can simultaneously declare their state and begin matching, without waiting for a central clearinghouse to authorize the process.[1] This feature is commonly thought to be impossible in typical humanitarian contexts.

11. Portable dignity

The international legal literature on climate displacement articulates a “right to life with dignity” grounded in the International Covenant of Civil and Political Rights. When biometric data collected to help Rohingya was later weaponized against them, it was not just a privacy violation — it was a dignity violation. Has-needs makes dignity portable by keeping the data anchored to the person across contexts: displacement, relocation, recovery. The record of what you gave, what you needed, what you contributed, and what was done to help you travels with you on your terms.[13][2]

12. Solution-based meetings of strangers (counteracting xenophobia by direct experience)

This is the most powerfully documented prosocial effect in the entire list. Allport’s contact hypothesis (1954) and decades of subsequent research confirm that prejudice is reduced by intergroup contact under four conditions: equal status, common goals, intergroup cooperation, and legitimate framing. A landmark preregistered field experiment in post-ISIS Northern Iraq found that randomly assigning Muslim players to Christian amateur soccer teams caused Christian players to measurably change their behavior — including material signs of respect — toward Muslim players over a 6-month period, with effects spilling over to other Muslim individuals outside the team. Long-run contact with Arab-Muslim communities in the US found that majority groups became less prejudiced, less politically hostile, more altruistic, and shifted voting behavior.[14][15][16][17]

Has-needs structurally produces Allport’s four conditions every time a need is matched across group boundaries: the strangers meet as equals (both are users of the same system), around a concrete common goal (the specific need being met), in direct cooperation (the transaction), with the system itself serving as the legitimizing authority. Xenophobia is not argued against — it is outcompeted by direct positive experience at functional scale. No policy, education campaign, or intergroup dialogue program achieves this at the speed and scale that a needs-matching architecture operating in a crisis can.

The Meta-Claim

None of these twelve effects are add-ons, incentives, or byproducts of good UX. They are emergent properties of building a system where the human is the base unit, sovereignty is a primitive, and agency is structural. That is the Has-needs claim that no other system, platform, intervention, or theory currently makes.[18][19][2][9]

Has-Needs is A Post-Capitalist Architecture Where People and Communities Own the Ledger

An evidence-anchored mapping of the economic harms that Has-Needs is uniquely positioned to correct shows why sovereignty, not inclusion, is the right architectural frame.

The Extractive Frame That Keeps Failing

The dominant global economic frame treats people and communities as data sources, labor inputs, and risk objects inside institutional and platform systems. Humanitarian and green-economy analyses note that growth-first, extractive models systematically externalize social and ecological costs, undermining local resilience and deepening dispossession, especially for Indigenous and rural communities.[1]

By contrast, Indigenous and social/solidarity economies are explicitly relational and regenerative, described as the original “sharing, green, regenerative, collaborative, and gift economies,” grounded in reciprocity, kinship, and land stewardship.[2] When these relational economies are overridden by extractive capitalism, the result is not just inequality but ecological degradation, cultural loss, and heightened disaster vulnerability.[3]

Has-Needs replaces the extractive frame with a sovereignty-first, relational economy where value is defined and governed by the people and communities who live it. It does not abolish markets or money; it relocates the ledger of value and obligation into the hands of sovereign individuals and communities, and forces institutions and platforms to plug into that ledger under their terms.

Who Owns the Ledger Now (and Who Should)

Today, all meaningful ledgers are external: blockchains reference identical nodes, banks hold financial histories, platforms hold behavioral and social graphs, and states hold identity and entitlement records. Online reputation and credit-scoring systems layer opaque models onto these ledgers, producing biased and easily gamed metrics that shape access to jobs, housing, and credit.[7]

The Indigenous Data Sovereignty movement responded by articulating the CARE Principles (Collective Benefit, Authority to Control, Responsibility, Ethics) as non-negotiable conditions for any use of Indigenous data, emphasizing that Indigenous Peoples and their communities must have binding authority over data that affects them.[10][11] CARE is a direct indictment of current data/ledger regimes that centralize control in states, NGOs, and platforms.

Has-Needs makes the person and their community the privacy-secure ledger, and reduces every institution to a guest that must request specified proofs instead of owning entire histories. Every transaction — of goods, time, care, information, or money — becomes a cryptographically signed receipt anchored to a Sovereign-being and scoped by a Community, with CARE baked into who can see and use it.

The “Unbanked Problem” is Inclusion in the Wrong System

Roughly 1.7 billion adults remain “unbanked,” and both humanitarian agencies and Big Tech have tried to solve this by creating new custodial accounts for them.[15] The World Food Programme’s Building Blocks project uses a permissioned Ethereum-based network to issue food entitlements to refugees in Jordan and Bangladesh camps; it reduces leakage and improves auditability, but the accounts and identifiers remain under WFP/UNHCR and vendor control — refugees cannot take those histories elsewhere as sovereign financial proof.[16][17][18]

Facebook’s Libra/DiEM stablecoin was explicitly marketed as a tool for global financial inclusion, but regulators, civil-society analysts, and even major partners like Mastercard criticized it for centralizing monetary and data power under a corporate-led association; the project ultimately stalled and was wound down.[20][21][22][23][24] Portable digital-identity work correctly notes that refugees and people in emerging markets need self-owned credentials to access services and finance, but most implementations still assume that once identity is solved, people will plug into existing bank/platform rails with the same extractive logic.[25][26]

Has-Needs does not “bank the unbanked”; it starts from the premise that people already own their economic histories, and invites banks and services to attach themselves to those self-owned ledgers. A person’s receipt chain — proof of fulfilled exchanges, reliability, and participation in co-ops and commons — is their portable financial and social credit file. Banks and MFIs read narrow proofs from that chain, then offer liquidity or custody, without ever owning (or needing to own) the underlying history.

Reputation Systems vs. Personal Receipt Chains

Online marketplaces and social platforms rely heavily on star ratings and reputation scores. Empirical work shows these systems are systematically distorted by reciprocity, social pressure, and network structures: users mutually inflate ratings, clusters trade positive reviews, and bad actors can strategically launder reputations.[8][9] Reputation scores are coarse, gameable proxies for trust.

In Indigenous and relational economies, by contrast, reputation is an accumulation of witnessed reciprocity and obligation over time — a lived ledger of who shows up for whom, and how they steward relationships and land.[5]

Has-Needs replaces platform reputation with a self-owned, cryptographically secured receipt chain that records what actually happened, not what people said about it. Each fulfilled match — a delivery, an hour of care, a ride, a facilitation, a debt repaid — becomes a signed receipt anchored to the parties and the community context. There is nothing to “rate” or game; there is only evidence, and each person chooses which slices of that evidence to share, with whom, under what terms.

Time, Care, and Indigenous Labor: Making the Invisible Visible

Standard markets mostly ignore or underprice care work, cultural work, and community maintenance, even though experiments with timebanking and local currencies show that when hours of service are explicitly valued, communities become more resilient and inclusive.[27][28][29][30][31] Timebanks and “time dollars” have been used in multiple countries to strengthen mutual support, reduce isolation, and offer a parallel economy where everyone’s hour counts equally.

Indigenous economic literature emphasizes that these forms of labor — caring for elders, transmitting culture, stewarding land — are central to sustaining people and ecosystems, not peripheral “unpaid work.” Treating them as economically invisible reproduces colonial and patriarchal harms.[5][32]

Has-Needs treats time and care as first-class economic assets everywhere in the system, not in a side project. Any community can decide that an hour of elder care, translation, ceremony support, or youth mentoring is a Has asset with its own unit, tracked on the same sovereign receipt chain as money and goods. This makes Indigenous and community labor economically legible without forcing it into wage-only logic.

Community Data: Co-ops Instead of Colonies

Agricultural and climate data are increasingly monetized by agribusiness and ag-tech platforms, often without farmers seeing any of the value. Farmer-owned data co-operatives have emerged to pool members’ data, negotiate licensing with input suppliers and insurers, and share revenues back to contributors.[33][34][35][36][37]

Indigenous data governance scholars document how external actors routinely capture and use Indigenous data — including environmental and cultural knowledge — without consent or benefit-sharing, calling this a continuation of colonial extractive relationships and arguing for Indigenous control over any such data.[10][11][12][13][14]

Has-Needs gives every community a built-in data cooperative: receipts can be pooled, licensed, and revenue-shared under community-defined CARE rules, with cryptographic audit trails for who contributed what. A coastal fishing community can sell access to anonymized catch and water-quality receipts to scientists or regulators under terms they negotiate; a farmer network can license micro-weather and yield data to climate services; an Indigenous nation can strictly limit how ecological and cultural data about their lands is used, and cut it off if terms are violated.

Commons and Reciprocity as Executable Rules

Where standard theory predicted tragedy in shared resource systems, empirical studies of long-lived Indigenous and local commons show that they endure when communities have clear rules, transparent monitoring, and reciprocal obligations around use and stewardship.[2][6] When these social and cultural controls are stripped away and replaced with purely price-based signals, over-extraction and ecological collapse follow.

Digital systems, however, typically treat commons as open APIs or open data sets that anyone can query until technical limits are hit; there is rarely a native notion of reciprocity or sufficiency encoded into the infrastructure.

Has-Needs allows communities to encode commons rules directly into the matching layer, so reciprocity and sufficiency become executable constraints, not just aspirations. A forest community can set extraction caps and stewardship obligations into the conditions for matching: no one can declare Needs for more timber or water than community rules allow without corresponding Has contributions to monitoring or restoration, and every extraction event creates a visible receipt. Overuse becomes socially and technically transparent, and can be stopped before damage becomes irreversible.

Protected Bazaars, Not Global Platforms

Global platforms like Uber, Airbnb, and Waze demonstrated the power of large-scale peer matching, but they also centralized control over data, matching logic, and fees in shareholder-driven corporations.[38][39][40] Users create the value; platforms own the reputation systems, transaction data, and market access, and can unilaterally change terms.

Timebanks, LETS systems, and local currencies showed a different path — localized, cooperative markets that keep value circulating locally and can support more equitable, solidarity-based exchange — but have typically remained small-scale due to infrastructural and network-effect limitations.[27][28]

Has-Needs implements “protected bazaars”: markets scoped by communities, with open innovation at the edge but no central chokepoint that can extract or reframe value. Matching engines and apps can be built by anyone via composable APIs, but they operate on views authorized by sovereign individuals and communities; there is no global scrapeable order book and no single platform that owns the relationships. Markets are federated by design.

Portable Dignity and Instant Inclusion

International human rights and climate-justice work now explicitly frames a “right to life with dignity” for climate-displaced persons, arguing that protection must include the ability to carry rights, history, and agency across borders — not just physical survival.[41][42][43][44] Analyses of digital identity in migration and refugee contexts similarly stress that ID systems should enable dignified access to services and mobility, but current deployments often leave refugees feeling surveilled and disempowered rather than recognized as rights-holders.[45][46]

Case studies of UNHCR and NGO digital-ID platforms in camps find that refugees often do not understand how their data is used, cannot meaningfully refuse enrollment, and experience identity systems as something done to them — with significant impacts on privacy, movement, and perceived dignity.[47][48][49][50] Even when digital ID improves efficiency, the underlying pattern remains: the ledger and credentials live with agencies and vendors; the person is a data subject, not the primary economic or political actor.

Has-Needs makes dignity portable by letting displaced people carry their own receipts and step into a new place as full participants, not supplicants. Example flow: a family reaches the edge of town, scans a QR code posted by the municipality or local co-op, and is immediately onboarded into the local Has-Needs community. Their sovereign ledger travels with them; they do not start from zero, and within minutes:

Their existing receipts — skills, past contributions, partial identity attestations, health and care preferences — are available for them to selectively reveal, not re-prove from scratch.
Locally matched needs and haves are visible in the map interface; they can declare what they need (shelter, medication, school access, translation) and offer what they have (skills, time, tools, caregiving capacity).
The system can immediately match their assets to local needs — a nurse from one country to an overstretched clinic, a driver to an ad-hoc transport network, a bilingual teenager to translation and orientation tasks. Even intangibles like companionship, or minor necessities like pet walking are equally valid.

Their Has-Needs ledger becomes a living record of what they survived and how they contributed, carried on their terms across jurisdictions. They arrive as sovereign economic and social agents whose history, capacities, and rights are intact — not as blank “beneficiaries” to be categorized, queued, and forgotten.[41][44]

What Sovereign Economics Changes

Dimension	Current Extractive Architecture	Has-Needs Sovereign Economics
Ledger ownership	Banks, platforms, states control accounts and histories [15]	Individuals and communities own receipt chains; institutions see narrow proofs
Data governance	FAIR at best; CARE seldom applied outside research	CARE enforced at transaction and community levels [10][11]
Reputation / credit	Opaque scores, gameable ratings, biased models [8][9]	Verifiable histories of reciprocity and fulfillment, self-presented as needed
Labor valuation	Wage work central; care and cultural labor largely invisible [5]	Time, care, and cultural labor are explicit Has assets tracked on-chain [27][32]
Community data	Scraped, centralized, sold back as services	Pooled via data co-ops; licensed on community terms with revenue sharing [33][36]
Commons	Managed via policy; often overridden by market signals [6]	Commons rules encoded into matching; every extraction visibly receipted
Markets	Global platforms as chokepoints and fee extractors [38][39]	Federated bazaars scoped by communities; multiple clients, no central owner
Institutions	Masters of identity and entitlement ledgers	Guests with negotiated, revocable access into sovereign-ledger space
Exploitation modes	Quiet data colonialism, predatory scoring, resource grabs via data [14]	Technically and procedurally blocked or made highly visible and vetoable [10][14]

Objections and Responses

“Isn’t this just another crypto utopia?”

No. Every component exists: Indigenous data governance (CARE)[10][11], farmer data co-ops[33], timebanks[27][28], mutual credit, and humanitarian mesh networks[16]. Has-Needs is a synthesis of proven practices around a sovereignty primitive, not a new token. The architecture does not require a new cryptocurrency or trust in any single technical actor.

“Won’t this be too complex for communities to govern?”

Communities already govern complex commons and social systems without software; Indigenous economies sustain people and lands through relational governance for generations.[2][5] Has-Needs gives them receipts, visibility, and rule-encoding tools; it does not add new external governance burdens— it makes existing community governance legible and enforceable at digital scale.

“How do banks and states accept this?”

They are offered cleaner risk profiles and lower data liability: they see cryptographic proofs instead of hoarding raw data, aligning with evolving privacy regulation and digital-ID directions.[16][17] The compliance cost of holding no raw personal history is strictly lower than the current exposure model. Regulators who want auditability get it through the receipt chain itself.

“What prevents a new platform from capturing Has-Needs data?”

Data can only leave sovereign ledgers with consent in the form of a completed Smart Contract; CARE gives communities collective veto over pooling and licensing.[10][11] Clients can be swapped without losing history, so platform capture would require visible, large-scale collusion that communities can contest and reverse. There is no data silo to seize. Additionally, if any personally identifiable information is discovered without the contract token, its holder is liable for theft.

“Can this scale globally?”

Mesh networking, distributed ledgers, data co-ops, and timebanks already operate at national and transnational scales.[16][33][27] Has-Needs uses the same technologies, but orients them around humans and communities as base units instead of institutions. Because the transactions and ontology are reflective of human interaction, the scale of personal chain technology is effectively infinite.

The Meta-Claim: Sovereignty as the Only Stable Basis for a Just Economy

Every harm you are trying to prevent — data colonialism, predatory finance, land and resource grabs, and aid that disempowers the people it claims to serve — traces back to a single architectural fact: the wrong entities own the ledgers.[10][14]

Has-Needs is revolutionary because it corrects that fact and lets everything else follow. An economy that starts from the sovereign human and their community makes exploitation technically unscalable and abundance locally governable — not by promising better behavior from institutions, but by changing what the system makes possible in the first place.[2][5][10]

None of these effects are policy add-ons, incentive programs, or UX choices. They are emergent properties of building a system where the human is the base unit, sovereignty is a primitive, and the ledger belongs to the person who lived it. Even if fraud is achieved, the damage is not systemic, just isolated to the individual level and easily detected.

Sources
[1] “The Great Aid Recession: 2025’s Humanitarian Crash in Nine Charts,” Council on Foreign Relations, 2025.
[2] “Indigenous Economies and the Social and Solidarity Economy,” UN Inter-Agency Task Force on Social and Solidarity Economy, 2022.
[3] “Here’s why Indigenous economics is the key to saving nature,” Green Economy Coalition, 2021.
[4] “Regeneration, Reciprocity & Relationships,” Reimagine Food, 2023.
[5] “Indigenous Economics: Sustaining Peoples and Their Lands,” 2023.
[6] “Circularity in Indigenous Relational Economy Theory,” Kogod School of Business, 2024.
[7] R. Zeckhauser, “Reputation,” Harvard University working paper.
[8] “Excess reciprocity distorts reputation in online social networks,” PLOS ONE, 2017.
[9] “Do reputation systems undermine trust? Divergent effects of enforcement,” Journal of Behavioral and Experimental Economics, 2015.
[10] “CARE Principles for Indigenous Data Governance,” GIDA/RDA, 2019–2024.
[11] “Indigenous Navigator, Indigenous Data Sovereignty and the CARE Principles,” Indigenous Navigator, 2025. https://indigenousnavigator.org/news/indigenous-navigator-indigenous-data-sovereignty-and-the-care-principles
[12] “Using the CARE Principles to Preserve Indigenous Data Sovereignty,” University of Arizona, 2023.
[13] Carroll et al., “Operationalizing the CARE and FAIR Principles for Indigenous data,” Scientific Data, 2021.
[14] Aaron Martin, “Why sovereignty matters for humanitarian data,” Big Data & Society, 2025.
[15] World Bank, Global Findex Database, 2021.
[16] “How the World Food Programme uses blockchain to better serve refugees,” ITU, 2020.
[17] “UN World Food Programme uses blockchain for direct payments,” Ledger Insights, 2020. https://www.ledgerinsights.com/un-world-food-programme-uses-blockchain-for-direct-payments/
[18] “Building Blocks,” WFP Innovation, 2026. https://innovation.wfp.org
[19] “Blockchain Technology Helps Feed Hungry Refugees in Conflict Zones,” WFP USA, 2026.
[20] “Facebook’s Cryptocurrency Gamble,” Wharton Magazine, 2020.
[21] “Facebook’s cryptocurrency won’t help the poor access banks,” Washington Post, 2019.
[22] “Facebook’s Libra currency won’t replace your money,” WIRED, 2019.
[23] “Facebook’s Libra cryptocurrency doesn’t make sense, says Mastercard boss,” The Independent, 2020.
[24] “The Social Media Giant’s Pursuit of Global Financial Inclusion,” North Carolina Banking Institute, 2020. https://scholarship.law.unc.edu/cgi/viewcontent.cgi?article=1508&context=ncbi
[25] “Portable Digital Identity: A Lifeline for Refugee Populations,” ChainScore Labs, 2025.
[26] Cardano Foundation, “How Blockchain Can Help in the Refugee Crisis,” 2023.
[27] “Timebanking can serve as a model for sustainable economic development,” Timebanking Canada, 2023.
[28] “Time Banking: Empowering Communities through Mutual Support,” CGAA, 2025.
[29] “Local Currencies to Build Resiliency: Time Dollars,” Green America, 2025.
[30] “The Currency of Compassion: TimeBanks USA and the Vision to Transform Communities,” SolutionBank, 2024.
[31] Michał Michalski, “Timebanking. A currency for stronger communities,” Management Papers, 2024.
[32] “Indigenous Economics: Sustaining Peoples and Their Lands,” sections on unpaid labor, 2023.
[33] “Farmer-Owned Data Cooperatives,” PRISM Sustainability Directory, 2025.
[34] “About Our Farmer Data Cooperative,” AgriDataCoop, 2024.
[35] “Putting a Value on a Precision ‘Data Cooperative’,” Strip-Till Farmer, 2019.
[36] “Data Cooperatives and Farmer Owned Agricultural Platforms,” PRISM, 2025.
[37] “Smallholder Data Cooperatives and Climate Adaptation Strategies,” PRISM Scenario, 2025.
[38] “How crowdsourcing is changing the Waze we drive,” Harvard Digital Initiative, 2018.
[39] “Waze Business Model,” Strategyzer / Business Model Zoo.
[40] “Hivemapper Mapped 1 Million Unique Kilometers,” Hivemapper blog, 2023.
[41] “Protecting the Right to Life with Dignity of Climate Displaced Persons,” ICAAD, 2025. https://icaad.ngo/righttolifewithdignity/
[42] “Right to Life with Dignity for Climate-Displaced Persons: Policy Brief,” ICAAD, 2024.
[43] “Expanding Legal Protections for Climate-displaced Persons,” Green Recovery, 2023.
[44] “When people are displaced by climate change, what rights do they have?” Amnesty International, 2025.
[45] “Digital Identity in the Migration & Refugee Context,” Data & Society, 2019.
[46] “Digital-Identity — An Analysis for the Humanitarian Sector,” IFRC, 2021.
[47] “Digital ID in Bangladeshi refugee camps: A case study,” The Engine Room, 2018.
[48] “Digital Identity: Enabling dignified access to humanitarian services in migration,” IFRC/partners, 2021.
[49] “Protecting the Human Rights of Persons Displaced by Climate Change,” Columbia Law School, 2018.
[50] “Digital Identity in the Humanitarian Sector,” IFRC & Red Cross Red Crescent Climate Centre, 2021.

What Happens When a County Says Yes

The Has-Needs deployment model is completely unique but familiar to all of history in terms of what is signed, what is built, what happens during an event, how savings are calculated, and what the county retains when it is over. The model is designed to eliminate every procurement barrier: there is no upfront cost, no vendor lock-in, no licensing fee, and no ongoing subscription. The only moment at which Has-Needs is compensated is the moment at which the county can prove Has-Needs saved money.

Part 1 — The Agreement

What the County Signs

The Has-Needs partnership agreement is not a software license. It is a performance agreement with a single payment trigger: a 5% fee on independently verified cost savings from a specific deployment event, assessed after the event, based on third-party audit. The county owes nothing unless Has-Needs demonstrably reduces their response costs. The county pays nothing upfront.

The agreement covers four things:

Baseline establishment: the county provides historical cost data for a defined response category — typically one to three years of per-event costs for emergency services, resource deployment, and coordination overhead. This establishes the counterfactual against which post-event costs will be measured.
Deployment authorization: the county authorizes Has-Needs to recreate their organizational structure as a Community tree within the protocol, and to support citizen-facing deployment during the defined deployment window.
Audit process: the parties agree to an independent, third-party auditor — typically a municipal finance auditor or a recognized emergency management research organization — who will conduct the post-event savings assessment on agreed methodology.
Perpetual use rights: the county retains the right to continue using Has-Needs indefinitely after the first event, at no additional cost, regardless of whether future events are audited or fees assessed.

What the county does not sign: any data sharing agreement, any data ownership transfer, any commitment to migrate from existing systems, or any licensing fee. Has-Needs does not take the county’s data. The county’s organizational structure, operational data, and citizen interaction records remain on sovereign chains — they do not become Has-Needs assets.

Part 2 — The Deployment

Recreating the Org-Chart as a Community Tree

The core deployment activity is the instantiation of the county’s organizational structure as a fractal Community tree within Has-Needs — at no cost to the county. The same four primitive entities and three relation states that coordinate two neighbors exchanging tools coordinate a county’s entire emergency response apparatus. No new architecture is required; only the organizational structure needs to be mapped.

In practice this means:

Top-level Community: the county itself — Department of Emergency Management, or equivalent
Sub-Communities for each department: Public Works, Public Health, Sheriff, Fire, EMS, Volunteer Coordination, Mutual Aid
Sub-Communities for operational units: Field Teams, Incident Command Posts, Shelter Locations, Distribution Points
Citizen-facing Community: open to all county residents, visible to relevant departments

Each node in the Community tree is a sovereign entity. A Field Team’s Working states are visible to the Incident Commander who authorized them, to the citizen whose Need is in progress, and to any other parties the Field Team designates — and not to anyone else. Data flows downward by consent, not upward by default. The privacy architecture is enforced at the Community scope level: a county administrator cannot query individual citizen chains any more than a county IT department can read individual employees’ private emails.

The Pre-Event Period

The most significant value Has-Needs delivers may be in the period before any event occurs. Communities that have been using Has-Needs for everyday mutual aid — the block-level food sharing, the neighborhood tool library, the informal skill exchange — enter an emergency with a pre-verified social graph, an established ontology, and a dense network of bilateral receipts that the chain-hopping protocol can traverse immediately.[1]

The county’s organizational deployment during the pre-event period consists of:

Department sub-Communities established and populated with personnel
Has and Need declarations logged for standing resources: equipment inventories, volunteer rosters, facility capacities, supply agreements
Working state protocols established for common request types: water main repair, road clearance, shelter intake, medical referral
Citizen onboarding through existing county communication channels, available as a free download, shareable peer-to-peer without cellular infrastructure

This last point is the answer to the bootstrap question: citizen adoption does not require a marketing campaign. Has-Needs is free to every individual citizen and can be shared peer-to-peer via direct device transfer without connectivity. During an event, the motivation to use it is intrinsic: it is the fastest path to direct contact with the county department responsible for your need, the fastest way to find a neighbor with the resource you require, and the only system that shows you in real time whether your report was received and who is working on it.

Part 3 — The Event

How Has-Needs Functions During Response

During an active emergency, Has-Needs operates as a parallel, citizen-sourced situational awareness layer that functions on whatever communications substrate exists — mesh networking between devices, standard cellular where available, SMS via the feature-phone gateway where cellular is limited. It does not replace incident command, radio communications, or dispatch. It provides the layer that those systems cannot reach: the continuous, self-reported, ground-truth data from the people inside the event.

From the county’s operational perspective:

Citizen declarations flow into the relevant Community automatically. A citizen declaring a Need for water main repair, a medical situation, or structural damage becomes immediately visible to the Public Works, EMS, or Emergency Management sub-Community respectively — without a relay chain, without a dispatcher intermediary, and without the citizen needing to know which department handles their category of need.

Working state provides real-time accountability. When a department accepts a citizen’s Need, the Working state chain opens: the citizen sees confirmation, and the department sees an actionable record. If the Field Team is delayed, the status update is visible to the citizen. If the time-lock expires, the escalation is automatic. The Common Operating Picture — typically assembled from radio reports and dispatcher logs — now has a self-updating layer of citizen-reported, department-acknowledged, receipted events.[2]

Spontaneous volunteers become a structured resource. Citizens with relevant skills or materials declare them as Has entries. The matching engine connects them to Needs in their geographic proximity. The Working state protocol handles the coordination. Volunteer time is not wasted on duplication or misallocation; the matching engine routes it toward verified gaps.[3]

Part 4 — The Accounting

How Savings Are Calculated

Post-event, the third-party auditor compares two figures:

The baseline: the county’s historical average cost per event in the defined category, established from the data provided at agreement signing and adjusted for event scale (affected population, geographic extent, duration).

The actual: the total verified cost of the response in which Has-Needs was deployed, drawn from the same accounting categories as the baseline.

The difference is the verified savings. The Has-Needs fee is 5% of that figure.

If the auditor finds no savings — if the event response cost equaled or exceeded the historical baseline — the fee is zero. The county owes nothing. Has-Needs absorbs the deployment cost.

The audit methodology is agreed before deployment and includes:

Cost categories: personnel hours, supply expenditure, contractor costs, mutual aid reimbursements, communication infrastructure, post-event damage assessment
Scale adjustment factors: affected population, geographic area, event duration, severity index
Attribution methodology: which savings components are attributable to Has-Needs vs. other factors (weather, pre-positioned resources, etc.)

The independence of the auditor is a contractual requirement. Has-Needs does not select or influence the auditor. The county’s finance office approves the auditor selection. The methodology is published before the event. The audit results are available to both parties and to any public accountability process the county requires.

What the County Retains

After the first event and audit, the county retains:

Perpetual use rights to Has-Needs at no ongoing cost
The Community tree built during deployment — all sub-Communities, personnel structures, and established protocols remain active
Every receipt on every chain — the complete record of what was declared, matched, accepted, and completed during the event, owned by the individual chains, accessible to the county only through the consent of those individuals
The organizational knowledge encoded in the Community tree — which is to say, the org-chart re-expressed as a living, sovereign, receipt-generating coordination infrastructure that the county can use for the next event, for preparedness planning, and for ongoing citizen services

The county does not retain any data that belongs to individual citizens. Those receipts are on individual chains. The county retains its own chain: the record of what its departments accepted, what they committed to, and what they completed.

Part 5 — Why This Model Works

For the County

The county takes on zero financial risk and zero migration cost. They do not abandon their existing systems. They add a layer that their existing systems cannot provide — citizen-sourced situational awareness — and pay for it only if it saves them money. The fee is paid from savings that would otherwise be waste. The ongoing use is free.

For Has-Needs

A single large-event deployment at a county with a $50–100 million historical per-event response cost produces a potential fee of $1–5 million on a 20–50% savings scenario — which the EFFICIENCY document documents as realistic based on supply chain waste, volunteer misallocation, and coordination overhead data. That fee from one event funds the development, deployment, and support of the entire protocol for the following year. The model is self-funding from first deployment.

For Citizens

Citizens receive a free tool that gives them direct contact with county departments, peer coordination with neighbors, and real-time visibility into whether their needs are being addressed — during the most stressful event of their lives. They pay nothing. They own their data. They can use it after the event is over, for mutual aid in the recovery period and beyond. The county is not their service provider in Has-Needs; it is one participant in a network of sovereign actors of which the citizen is the center.

Sources
[1] Aldrich, D., “Fixing Recovery: Social Capital in Post-Crisis Resilience,” Purdue University. https://docs.lib.purdue.edu/context/pspubs/article/1002/viewcontent/Aldrich_Fixing_Recovery_Journal_of_Homeland_Security.pdf
[2] Has-Needs, “EFFICIENCY-has-needs.md: The Root Problem — Situational Awareness Failure,” 2026.
[3] Has-Needs, “EFFICIENCY-has-needs.md: Volunteer Coordination — The Spontaneous Volunteer Problem,” 2026.
[4] Has-Needs, “TECHNICAL-has-needs-FINAL.md: Community — The Fourth Entity,” 2026.
[5] Has-Needs, “EFFICIENCY-has-needs.md: The Revenue Model — 5% of Verified Cost Savings,” 2026.

The Defining Humanitarian Challenge of the Next 30 Years Requires a Different Architecture

The scale of climate-driven displacement is not a future risk. It is a present fact accelerating toward a threshold that no existing coordination system was designed to handle. Has-Needs was not designed specifically for climate response — but its architecture is uniquely suited to the specific conditions that climate displacement creates: stateless populations, absent or collapsed infrastructure, multi-year protracted displacement, and communities that must coordinate without the institutional scaffolding that conventional coordination systems require to function.

The Scale of the Problem

The numbers are not contested. What is contested is whether the institutions currently responsible for the response are architecturally capable of scaling to meet them.

At least 117 million people are currently displaced by war, violence, persecution, and climate events — a figure that UNHCR describes as a record.[1] Three in every four of those refugees or displaced persons are living in countries facing high-to-extreme exposure to climate-related hazards.[1] The crisis is not waiting for the displaced to stabilize before compounding itself.

By 2040, the number of countries facing extreme climate hazards could rise from three to 65.[1] By 2050, projections converge on a range of 200 million to 1.2 billion climate-displaced persons — the World Bank’s Groundswell report establishing 216 million internal climate migrants as its primary scenario, while the IOM cites 200 million environmental migrants and the Institute for Economics and Peace projects 1.2 billion in total displacement.[2][3][4] The spread in projections reflects the uncertainty in mitigation policy, not the uncertainty in the underlying dynamics.

Nearly all current refugee settlements face an unprecedented rise in hazardous heat. By 2050, the fifteen hottest refugee camps in the world will face nearly 200 days per year of hazardous heat stress — rendering them uninhabitable on current timelines.[1]

The coordination challenge is not primarily a resources problem. The resources exist, in aggregate, to address the humanitarian dimensions of climate displacement. The problem is architectural: every coordination system currently deployed for displaced populations assumes institutional infrastructure that climate displacement systematically destroys — reliable connectivity, stable jurisdictions, functioning governance, addressable populations, and the institutional continuity to maintain and operate centralized systems over multi-year timescales. Has-Needs makes none of these assumptions.

Five Has-Needs Structural Advantages for Climate

1. Compute Efficiency: Structured Semantics vs. NLP at Scale

The humanitarian coordination industry’s pivot toward AI-assisted needs assessment, real-time translation, and automated matching is creating a resource demand crisis that is itself a form of climate harm. Large language models require enormous energy to operate: research on LLM inference energy consumption shows that larger models consume up to 6× more energy than compact models per query, and that “longer inputs or higher lexical diversity directly correlate with increased energy cost.”[5][6] A typical short-prompt GPT-4 query consumes approximately 0.3 Wh; at humanitarian deployment scale — millions of needs assessments across dozens of languages — this becomes a non-trivial energy burden.[6]

Has-Needs requires none of this. The [entity, relation, context] triplet is already structured; matching is a graph query against defined semantic objects, not a natural language comprehension task. No LLM inference is required at any stage of the Has-Needs coordination pipeline. The energy cost per match is orders of magnitude lower than any NLP-based equivalent. This is not an incremental efficiency improvement — it is a category difference, and it scales: a deployment serving 10 million displaced persons does not require a proportionally larger compute infrastructure, because the matching engine’s complexity is bounded by the triplet structure, not by the linguistic diversity of the population.[7]

For climate funders increasingly accountable to Scope 3 emissions and digital infrastructure environmental impact, this difference is directly reportable.

2. Trauma Mitigation as Sustained Productivity

The TRAUMA document establishes the peritraumatic agency preservation argument for acute disaster response. Climate displacement introduces a more severe version of the same problem: protracted, multi-year displacement under conditions of sustained helplessness, where the learned helplessness mechanism does not just produce a trauma response during a crisis window — it becomes the default cognitive state of a population that has lost control of virtually every domain of daily life simultaneously.[8]

The humanitarian literature on protracted displacement is unambiguous about the consequences: loss of economic productivity, intergenerational transmission of helplessness, deteriorating mental health trajectories, and a progressive erosion of the community competence that is the primary predictor of eventual recovery.[9] Standard humanitarian response compounds this through its design: displaced persons are data subjects in needs assessments, beneficiaries in distribution systems, cases in protection databases. At no point in any existing coordination system is the displaced person an agent who declares their own state, coordinates with their own community, and builds a receipt history that documents their own competence and contribution.

Has-Needs is the first system in which this is structurally possible. The Sovereign Being does not cease to be sovereign because they have been displaced. Their chain moves with them. Their Persona Manager persists. Their Has declarations — skills, knowledge, materials, capacity — remain visible to Communities they join wherever they go. The displaced person arrives in a new Community as a contributor, not only as a recipient. That structural distinction is the single most powerful intervention against the helplessness-to-dependency cycle that protracted displacement produces. And it is architectural — it happens because of how Has-Needs works, not because of a program design that can be underfunded or discontinued.

3. Emergent Leadership vs. Self-Declared Local Actors

The post-disaster and displacement environment is the most documented context for humanitarian aid diversion in the literature. Corruption in humanitarian assistance includes “community leaders offering bribes to government authorities or humanitarian agencies in order to be favored in the distribution of relief supplies.”[10] In conflict-affected settings, research documents extortion, leakage, embezzlement, and the systematic use of registration processes to favor politically aligned beneficiaries.[11][12] The Taliban’s use of Afghan camp governance structures to extend authority and divert assistance is one documented example among many.[11]

The root cause is consistently the same: coordination vacuums are filled by whoever claims the coordination role, and existing systems have no mechanism for verifying whether that claim reflects genuine community standing. Donors operating under pressure to move resources quickly partner with whoever presents plausible credentials, and have no structural way to distinguish a genuine community leader from a self-declared one.[12]

Has-Needs eliminates the information conditions that make this possible. Leadership in Has-Needs is not claimed — it is accumulated. The individuals with the most completed exchanges, the most verified bilateral receipts, the most diverse Has declarations, and the most active Working states in their Community graph are visible as genuine connectors and coordinators through the protocol’s normal operation. An external donor or partner agency can traverse the chain-hopping verification graph of any proposed partner and see, from the actual exchange history, whether that person is embedded in a genuine network of bilateral commitments — or whether they appeared recently with no receipt history and a self-declared authority claim. The receipt chain is not a background check. It is the documentary record of what the person has actually done.

4. Peer Community Resource Sharing in Infrastructure-Absent Conditions

Conventional humanitarian logistics assumes an institutional supply chain: resources flow from donors to implementing organizations to distribution points to beneficiaries. This architecture fails systematically in climate displacement environments where distribution infrastructure is absent, destroyed, or inaccessible. It also fails to mobilize the most significant resource available in any displaced community: what the displaced people themselves have, can do, and are willing to exchange.

Every displaced community contains people with medical skills, construction knowledge, language capacities, food preparation expertise, childcare ability, and materials that others need. No centralized assessment can capture this in real time. No distribution system can route these resources horizontally between peers. Has-Needs does both, automatically, at the pace of declaration and matching — without institutional intermediaries, without distribution infrastructure, and without requiring anyone to identify themselves to an authority.

The offline-first, mesh-first DXOS architecture is specifically suited to infrastructure-absent deployment: CRDT synchronization operates across completely disconnected nodes and converges automatically when any connection is available — device-to-device mesh, intermittent cellular, satellite terminal, or community Wi-Fi.[13][14] A displaced community with ten smartphones can run Has-Needs as a fully functional peer-to-peer coordination network with zero external infrastructure. As connectivity becomes available, the chain synchronizes. As institutional partners deploy field nodes, the Community graph expands to include them. The peer layer does not disappear when institutions arrive — it becomes the ground truth that institutional coordination is responding to.

5. Ethical Monetization of Indigenous Knowledge and Cultural Wisdom

Climate displacement disproportionately affects Indigenous communities — the populations with the deepest knowledge of local ecosystems, adaptive agriculture, water management, and sustainable resource use. That knowledge has historically been extracted by researchers, development organizations, and institutions without compensation, consent, or ongoing benefit to the communities that hold it. The CARE Principles for Indigenous Data Governance — Collective Benefit, Authority to Control, Responsibility, and Ethics — establish the standard that the research and development community has committed to.[15][16] The gap between that commitment and current practice is the absence of a technical mechanism to implement it.

Has-Needs closes that gap. The OCA overlay system and smart contract layer together constitute the first practical mechanism for communities to share knowledge on their own terms, at their own pace, to parties they choose, and to receive verifiable, receipted value in exchange. A community’s traditional water management knowledge can be disclosed selectively — only to verified partner organizations who have signed a smart contract specifying the terms of use, the compensation, and the prohibition on onward transfer. The receipt chain documents every disclosure: who received the knowledge, what they agreed to, what they paid. The community’s sovereign chain is the proof of the agreement and the record of the benefit received.

The UN Declaration on the Rights of Indigenous Peoples asserts Indigenous peoples’ rights and interests in data and “their authority to control their data” as fundamental to self-determination.[15][17] Has-Needs is the first coordination protocol in which that authority is not a policy commitment — it is an architectural property.

The Funding Landscape

The specific funding channels this document addresses — UNHCR, IOM, the Gates Foundation’s climate and global development programs, USAID, FCDO, the Green Climate Fund — are already allocating resources toward the problem of coordination at scale for displaced populations. The gap in every current funded program is the same gap Has-Needs addresses: data flows from displaced people upward to institutions that make decisions about them, and the people themselves have no agency, no receipt, and no sovereign record.

Has-Needs does not compete with any current program for those funds. It provides the foundational layer that every current program is missing — and without which the resources those programs deploy will continue to produce the coordination inefficiencies, aid diversion vulnerabilities, and dependency cycles that the humanitarian literature has documented for three decades.

The compute efficiency argument, the trauma-as-productivity argument, the emergent leadership argument, the peer resource sharing argument, and the indigenous knowledge sovereignty argument each independently justify the investment. Together they describe a system that does not just reduce the cost of the humanitarian response to climate displacement — it structurally changes what that response is capable of producing.

Sources
[1] UNHCR / UN News, “Refugee camps set to be uninhabitable by 2050 as extreme weather worsens,” November 2025. https://news.un.org/en/story/2025/11/1166318
[2] World Bank, “Groundswell: Climate Change Could Force 216 Million People to Migrate Within Their Countries by 2050,” September 2021. https://www.worldbank.org/en/news/press-release/2021/09/13/climate-change-could-force-216-million-people-to-migrate-within-their-countries-by-2050-world-bank-report
[3] ReliefWeb, “Climate Migrants Might Reach One Billion by 2050,” 2017. https://reliefweb.int/report/world/climate-migrants-might-reach-one-billion-2050
[4] Zurich Insurance, “There could be 1.2 billion climate refugees by 2050,” 2024. https://www.zurich.com/insights/business/there-could-be-1-2-billion-climate-refugees-by-2050-here-s-what-you-need-to-know
[5] Arxiv, “Investigating Energy Efficiency and Performance Trade-offs in LLM Inference,” 2025. https://arxiv.org/html/2501.08219v3
[6] Dev.to, “Reasoning + RAG: Toward a More Sustainable Future for LLMs,” 2025. https://dev.to/injeniero/reasoning-rag-toward-a-more-sustainable-future-for-llms-397f
[7] Has-Needs, “TECHNICAL-has-needs-FINAL.md: The Emergent Ontology and AI Efficiency,” 2026.
[8] Simply Psychology, “Learned Helplessness: Seligman’s Theory of Depression,” 2024. https://www.simplypsychology.org/learned-helplessness.html
[9] Has-Needs, “TRAUMA-has-needs.md: Part 2 — Before the Event: Social Capital as the Primary Resilience Variable,” 2026.
[10] Basel Governance Institute, “Corruption in Natural Disaster Situations,” 2019. https://baselgovernance.org/sites/default/files/2019-01/Corruption%20in%20natural%20disaster%20situations.pdf
[11] DIVA Portal, “Anatomy of Corruption in Humanitarian Assistance,” 2023. https://uu.diva-portal.org/smash/get/diva2:1803244/FULLTEXT01.pdf
[12] The New Humanitarian, “Everybody’s hiding their skeletons: Aid fraud and double standards,” October 2023. https://www.thenewhumanitarian.org/feature/2023/10/03/aid-diversion-and-double-standards
[13] Calibraint, “Offline First Mobile App in 2026: Real-Time Data Sync with CRDTs,” January 2026. https://www.calibraint.com/blog/offline-first-mobile-app-in-2026
[14] NextUpGrad, “The Local-First Revolution: Building Apps That Work Offline by Default,” January 2026. https://www.nextupgrad.com/the-local-first-revolution-building-apps-that-work-offline-by-default/
[15] PMC, “Operationalizing the CARE and FAIR Principles for Indigenous Data Sovereignty,” 2021. https://pmc.ncbi.nlm.nih.gov/articles/PMC8052430/
[16] LINCS Project, “CARE Principles for Indigenous Data Governance.” https://lincsproject.ca/docs/terms/care-principles-for-indigenous-data-governance
[17] SFU Library, “Indigenous Data Sovereignty,” 2025. https://www.lib.sfu.ca/help/publish/research-data-management/indigenous-data-sovereignty

Has-Needs represents a Non-Extractive Coordination Infrastructure for the People That Every Previous Platform Left Behind

We feel the specific opportunity and obligation that Has-Needs carries for the 3.1 billion people who remain offline or underconnected, and the billions more who are connected via feature phones, SMS, and low-bandwidth mobile in low- and middle-income countries but are not being heard. We make the case for funders, development organizations, and policy institutions who are currently allocating resources to close the digital divide that: connecting those three billion to existing platforms replicates the data extraction dynamic that has already failed them.

For them, Has-Needs offers a different foundation.

The Scale of the Connectivity Gap

The numbers are precise. The ITU reported 2.6 billion people offline in 2023, representing 33 percent of the global population.[1] As of 2025, GSMA data shows that 3.1 billion people remain unconnected despite living in mobile internet coverage areas — the “usage gap,” where barriers are not infrastructure but cost, digital literacy, and the absence of services that justify connectivity.[2][3] The majority — 93% — live in developing countries, predominantly in Sub-Saharan Africa and South Asia, where mobile is already the primary — and often only — pathway to digital services.[2]

Mobile line subscriptions reach 98.7% of the population in developing countries.[4] In many low-income economies, more people have access to a mobile device than to clean water or reliable electricity. The population that Has-Needs must serve is not a population waiting for smartphones — it is a population that is already connected, via the device it has, at the bandwidth it can afford.

This is not a constraint to be engineered around. It is the design requirement.

Why Every Previous Platform Failed This Population

The pattern is consistent across the history of the digital development sector: platforms designed in high-income contexts, with high-bandwidth assumptions, are adapted downward for deployment in low-income contexts. The adaptation produces a technically functional product and a structurally extractive one. The data generated by users in those contexts flows to servers in Ireland (KoboToolbox/AWS), California (Google, Meta), or Washington (USAID’s implementing partners) — where it is analyzed, monetized, and used to make decisions about the populations who generated it, without those populations having any access, control, or obvious benefit.

A 2026 academic analysis of digital solidarity platforms found this pattern reproduced even in explicitly cooperative and emancipatory systems: “emancipatory rhetoric often co-exists with data monopolies, assetisation tactics and legal clauses that reproduce extraction,” including platforms that state “data belongs to citizens” in their communications while specifying that “data obtained with user consent is owned by the city and consortium firms” in their terms of service.[5] The extraction dynamic is not a consequence of bad intent — it is a consequence of architecture. The data flows to where the servers are, and the servers are never where the people are.

Has-Needs is architecturally incapable of this failure. There is no Has-Needs server that holds user data. There is no central database. The Sovereign Being’s chain is on their device. When they are offline, their data is on their device. When they connect to the mesh, their data is on the mesh — scoped to the Communities they have joined. When they leave, their data leaves with them. Has-Needs cannot extract what it architecturally cannot aggregate.

The Four Technical Requirements are Already Met by Has-Needs

Feature Phone and SMS Gateway

The population Has-Needs must serve includes hundreds of millions of people with no smartphone — only basic phones capable of SMS. The Has-Needs protocol is designed for a tiered access model:

Full client: smartphone app with the complete UI, chain visualization, and matching interface
Lite client: low-bandwidth progressive web app accessible on any browser-capable device
SMS gateway: a stripped interface through which any feature phone user can declare a Has, declare a Need, and receive match notifications via text message

The SMS layer does adapts the full sovereignty and chain-hopping capability of the full client as preferences — as a full participant in the Has-Needs network. A feature phone user declaring a Need or Has via SMS generates a chain entry that the protocol processes identically to a smartphone declaration. Matches are returned via SMS according to the users filtering preferences. Working state progression is communicated via SMS. The user is a Sovereign Being in the network regardless of the sophistication of their device.

Offline-First, Local-First Operation

The DXOS foundation’s CRDT-based synchronization provides the technical answer to intermittent connectivity: the application is fully functional offline.Data is created and modified locally; synchronization occurs automatically whenever any connection becomes available, whether device-to-device Bluetooth mesh, intermittent cellular, community Wi-Fi, or satellite terminal.[6][7] Apps designed for offline-first operation experience 33% higher retention rates in low-connectivity environments, and CRDT-based sync cuts multi-user conflict errors by up to 90% compared to traditional sync mechanisms.[6]

In practical terms: a community health worker in rural Kenya with no cellular signal can use Has-Needs to declare the medical needs of the families she visits, record the Working states of the supplies she has committed, and coordinate with a district warehouse — all on her phone, offline. When she reaches a location with signal, everything synchronizes, the chains update, and the district coordinator sees the current state of all active Working states without any manual reconciliation.

Linguistically Agnostic Interface

Has-Needs is designed with an icon-first, language-secondary interface. The map interface and four primitive entities (Has, Need, Being, Community) are expressed through visual primitives that do not require literacy in any specific language. Being undefined, an emergent localized ontology grows as the Community’s exchange history builds, the locally-relevant categories emerge in the users’ own language and cultural framing — not translated from English, not imposed from an external schema, but generated bottom-up from the declarations of the people using the system.

This is not a localization feature. It is an architectural property of the triplet model: the ontology is what the community says it is. A community in Bangladesh whose most-exchanged category is a specific form of monsoon flood labor assistance will develop an ontology node for that category in the language and conceptual framing that their declarations use — without any schema administrator, translator, or development organization defining it for them. Sharing their ontology enables resoponding agencies to immediately understand local priorities and adjust accordingly in realtime.

Peer-to-Peer Distribution Without Connectivity

Has-Needs can be shared peer-to-peer via direct device transfer without any internet connection. This means community adoption does not require a data plan, an app store, or a cellular network — it requires one person in a community with the application, and a way to pass it to the next person. In markets where a $10 phone and a shared SIM card are the standard technology configuration, this distribution model is the only viable one.

The Five Development Sector Arguments

1. The Non-Extractive Model as the Primary Innovation

The standard critique of development sector digital platforms is not that they fail technically — it is that they succeed technically while failing to transfer value to the communities they serve. Has-Needs is the first coordination platform designed from the ground up so that the value generated by exchange stays with the people who generated it. The receipt chain is the user’s asset. The emergent ontology belongs to the Community. The exchange history is sovereign data that cannot be aggregated by any party without consent.

For Gates Foundation, USAID, FCDO, and similar institutional funders who are increasingly accountable to do-no-harm digital development principles, this distinction is the difference between funding a new extraction infrastructure and funding the alternative to it.

2. Trauma as the Productivity Gap

The development economics literature consistently underestimates the productivity cost of unaddressed trauma in high-risk, climate-vulnerable, or conflict-adjacent communities. Has-Needs’ trauma-informed architecture — agency preservation through Working state visibility, social capital building through peer exchange, healing through collective receipt narrative — is not a mental health program grafted onto a coordination tool. It is the coordination tool operating as designed, producing trauma mitigation as a structural consequence of its normal operation.[8]

For development funders measuring economic productivity and community resilience outcomes, this is a measurable intervention on the most significant and least-addressed productivity barrier in the populations they serve.

3. Emergent Leadership as Anti-Corruption Infrastructure

Aid diversion by self-declared local authorities is among the most persistent and costly failure modes in development sector programming.[9][10] The receipt chain’s emergent leadership model — where genuine community connectors become visible through exchange history, not self-declaration — is the first structural solution to this problem that does not require external oversight. A development partner can traverse the chain-hopping verification graph of a proposed local partner and see, directly from bilateral receipt history, whether that partner’s claimed community standing is reflected in actual exchange relationships.[9][11]

This is not a replacement for due diligence. It is the due diligence substrate that currently does not exist.

4. Peer Resource Sharing as the Durable Layer

Development programming is structurally dependent on institutional presence. When the program ends — when the implementing partner leaves, when the grant cycle closes — the coordination infrastructure disappears with it. Has-Needs produces a different outcome: the peer resource sharing network built during a program continues operating after the program ends, because it does not depend on any institutional infrastructure to function. The Community tree persists. The exchange relationships persist. The emergent ontology persists. The receipt chains are on individual devices.

This is the answer to the sustainability question that every development funder asks and that no existing platform adequately addresses: what happens when we leave?

5. Indigenous Knowledge Sovereignty as Ethical Monetization

As the CLIMATE document establishes, the CARE Principles for Indigenous Data Governance[12][13] represent the research and development community’s commitment to Indigenous data sovereignty — a commitment that currently lacks a technical implementation mechanism. Has-Needs provides that mechanism: OCA overlay-protected knowledge, smart contract-governed disclosure, receipt-chain-verified compensation. A community can share its knowledge on its own terms, to parties it chooses, for compensation it defines, with a permanent cryptographic record of every disclosure and every payment. This is not a revenue model for Has-Needs. It is a revenue model for the communities — and the first one that the receipt chain can verify as structurally honest.

The Investment Case

The three billion people remaining offline, and the additional billions on feature phones and low-bandwidth mobile, represent the largest underserved coordination market on earth. They also represent the populations most vulnerable to the climate displacement described in the CLIMATE document, most exposed to the aid diversion documented in the corruption literature, and most likely to benefit from the trauma mitigation and social capital building that Has-Needs produces as structural byproducts.

Has-Needs reaches this population without the extractive infrastructure model that every previous platform has used — and in doing so, it becomes the first coordination system that these communities can trust with their data, because it is the first one that structurally cannot use their data against them.

The development sector has spent three decades and hundreds of billions of dollars building digital coordination infrastructure for these populations. The problem is not the investment level. The problem is that every system built assumed the wrong architecture. Has-Needs is the correction.

Sources
[1] ITU, “Measuring Digital Development: Facts and Figures 2023.” https://www.itu.int/itu-d/reports/statistics/wp-content/uploads/sites/5/2023/11/Measuring-digital-development-Facts-and-figures-2023.pdf
[2] Developing Telecoms, “3.1 billion people remain offline despite mobile internet coverage,” September 2025. https://developingtelecoms.com/telecom-business/telecom-regulation/19042-3-1-billion-people-remain-offline-despite-mobile-internet-coverage.html
[3] The Register, “There’s three billion people offline and without phones,” September 2024. https://www.theregister.com/2024/09/03/three_billion_people_offline/
[4] MIT Solve, “MedBot: SMS Text Based TeleHealth with Offline Forms,” 2022. https://solve.mit.edu/challenges/performance-improvement/solutions/66565
[5] Policy Review, “Governance, technology, and the limits of digital solidarity economies,” February 2026. https://policyreview.info/articles/analysis/governance-technology-limits-digital-solidarity
[6] NextUpGrad, “The Local-First Revolution: Building Apps That Work Offline by Default,” January 2026. https://www.nextupgrad.com/the-local-first-revolution-building-apps-that-work-offline-by-default/
[7] Calibraint, “Offline First Mobile App in 2026,” January 2026. https://www.calibraint.com/blog/offline-first-mobile-app-in-2026
[8] Has-Needs, “TRAUMA-has-needs.md: The Mechanism — What Causes Disaster Trauma,” 2026.
[9] Basel Governance Institute, “Corruption in Natural Disaster Situations,” 2019. https://baselgovernance.org/sites/default/files/2019-01/Corruption%20in%20natural%20disaster%20situations.pdf
[10] The New Humanitarian, “Everybody’s hiding their skeletons: Aid fraud and double standards,” October 2023. https://www.thenewhumanitarian.org/feature/2023/10/03/aid-diversion-and-double-standards
[11] DIVA Portal, “Anatomy of Corruption in Humanitarian Assistance,” 2023. https://uu.diva-portal.org/smash/get/diva2:1803244/FULLTEXT01.pdf
[12] PMC, “Operationalizing the CARE and FAIR Principles for Indigenous Data Sovereignty,” 2021. https://pmc.ncbi.nlm.nih.gov/articles/PMC8052430/
[13] LINCS Project, “CARE Principles for Indigenous Data Governance.” https://lincsproject.ca/docs/terms/care-principles-for-indigenous-data-governance

Status:

omdesign has working prototypes.

Using mature technologies like DXOS, Overlays Capture Architecture, SmallWeb, and Rust makes real-world test deployment in the six months following funding a reality. 15 years of design and vetting have only validated the premise upon which Has-needs was built.

Start a conversation: