Who we are, what we’re researching, and how it’s built.
The people behind Fruitful Network Development, the case for coordinated local supply, and the technical approach underneath it.
Why we exist
Northeast Ohio was once a fresh-produce powerhouse. Today that tradition survives in passionate, dispersed pockets — Harbor Gardens, Purple Brown Farm Store, Ohio City Provisions and the East Side Market, Yellow Bird Foodshed, the CWRU farms, and others. Fruitful Network Development is taking the next step: making local agriculture equitable to work in and with again.
Local agriculture is undercapitalized, undercoordinated, and full of people who would still rather be there than anywhere else. The first job of Fruitful Network Development is to make their day-to-day operations a little less broken — websites that work, payments that clear, mailboxes that don't get lost. The second job — open-source operations software that small operations can share without losing ownership — is what the first job pays for.
The founder
Dylan Montgomery
Tend to the Garden You Can Touch
— Jack Kornfield
Engineer, founder of Fruitful Network Development. Background in software, agricultural-systems research, and a lot of conversations with people working in food across Northeast Ohio. The web-services side of the business pays the bills; the open-source operations software is the long arc.
The good thing and the profitable thing can become the same thing
Local food is not structurally weak because good values are unprofitable. It is structurally weak because independent local supply has not had the coordination layer that centralized supply already controls.
Most people want food that is healthier, less expensive, easier to buy, and connected to local economies that can support small businesses. The inherited doubt is that these goals cannot exist together. Better food seems more expensive. Local production seems less reliable. Sustainable practice seems harder to scale. Small farms seem destined to remain culturally admired but commercially marginal.
That doubt is understandable, but incomplete.
Centralized food systems do not win only because they are large or because they cut more corners. They win because they already own a coordination layer. They see more supply. They see more demand. They can redirect product when one buyer cannot absorb it. They can standardize what buyers see. They can spread transportation, storage, administrative, compliance, and procurement costs across many transactions.
The central advantage is coordination.
Better value must be valued better
A system can place food on shelves while burning value through waste, spoilage, long transport, duplicated administration, weak planning confidence, and shifted risk. Price is visible. Value is structural.
The research problem is therefore not whether local food is morally desirable. The research problem is whether local agricultural value is stranded because nearby supply cannot yet be made legible, aggregated, schedulable, and reliable enough for routine procurement.
The coordination hypothesis
If farms in a bounded region can become visible as one cohesive supply source without being forced into one company, local sourcing can move beyond sentiment. Buyers can source from aggregated local availability at useful order sizes. Farms can plan against demand before production risk is fully absorbed. Nearby production can become operationally usable instead of merely geographically close.
Fruitful Network Development is positioned around this hypothesis: a buyer-oriented, locality-bounded coordination layer can make fragmented farm supply visible enough to test whether stranded local agricultural value is recoverable.
Centralized supply and coordinated local supply
Suggested figure: Centralized supply and coordinated local supply side by side. One side shows ownership-based coordination; the other shows independent farms connected through a shared procurement data layer.
1. Centralized Profit and Economies of Scale
Scale is coordination power
Economies of scale are often described as a production advantage: larger farms, larger buyers, larger distributors, larger warehouses, larger routes. That description is true but incomplete. Scale also creates an information advantage. A centralized system can see, redirect, and absorb more activity than an isolated producer can.
Internal supply visibility
Centralized food systems can coordinate what is available across many production points, distribution centers, contracts, buyers, and product classes. This visibility allows the system to treat supply as flexible rather than stranded.
Supply visibility includes
Product quantity.
Product location.
Product quality or grade.
Earliest and latest movement windows.
Storage and handling requirements.
Substitute products.
Expected buyer requirements.
Exceptions, shortages, and surplus.
Internal demand visibility
Centralized systems also coordinate demand across many customers and channels. A product that cannot move through one buyer may move through another. A shortage may be met through substitution. A surplus may be redirected before it becomes a final loss.
Demand visibility includes
Which buyers need product.
How much volume they can absorb.
Which buyers can accept substitutes.
Which contracts or routes can redirect product.
Which product classes can tolerate delay.
Which buyers require strict standardization.
Perishability becomes managed risk
Perishable goods become costly when timing fails. Centralized systems reduce that risk by increasing the number of places product can go and the number of ways demand can be satisfied. A small producer may experience unsold product as an immediate loss. A centralized system may experience the same problem as a routing, pricing, storage, or channel-management issue.
Centralization reduces finality
A failed match between one producer and one buyer does not necessarily end the transaction chain. Product can move into:
Another retail buyer.
Another institutional buyer.
Another distribution route.
Another pack size or product class.
Another timing window.
A processor or secondary outlet.
Profit emerges from coordinated optionality
Centralized profit is not only the result of producing cheaply. It is also the result of controlling optionality. Optionality reduces risk. Lower risk supports lower financing costs, tighter procurement, larger buyer commitments, and stronger bargaining power.
Sources of centralized advantage
Volume aggregation
Large systems can accumulate enough volume to satisfy standardized buyers and fill recurring contracts.
Cost spreading
Administrative, compliance, logistics, merchandising, and procurement costs can be distributed across many transactions.
Buyer-facing simplicity
Buyers prefer channels that reduce search, documentation, order management, delivery exceptions, and substitution problems.
Risk transfer
Large buyers and distributors can sometimes shift inventory, margin, timing, and compliance risk onto smaller suppliers.
Market legibility
A centralized system can make itself easier to buy from than a fragmented group of nearby producers, even when the nearby producers may have strong product value.
Evidence note: The SBIR proposal identifies the structural problem as fragmented farm-side data, buyer requirements, and logistics constraints remaining across incompatible systems and manual workflows. It also frames intermediated and institutional channels as requiring stronger reliability and coordination than direct-to-consumer channels alone.
The disheartening story is that scale crushes values because values are expensive. Health, locality, sustainability, and independence appear to be the corners that must be cut when profit becomes the goal. But that story mistakes a coordination advantage for a law of capitalism. The question is not whether better values can survive in a market. The question is whether those values have ever been given the same coordination machinery that centralized systems already use.
2. Local Farms and the Coordination Failure
Local supply is physically near but operationally fragmented
A farm can be close to a grocery store, restaurant, school, food hub, or institution and still be difficult for that buyer to use. Physical proximity does not automatically become procurement reliability.
The difference between distance and usability
Physical proximity
Nearby farms may reduce distance, product age, and transport burden.
Operational usability
A buyer still needs to know:
What is available.
When it is available.
How much volume exists.
Whether supply is reliable.
Whether products meet specifications.
Whether delivery can happen on schedule.
Whether substitutions are acceptable.
Whether documentation and compliance requirements can be met.
Demand does not automatically become farm revenue
Interest in local food is not the same thing as usable procurement. A buyer may prefer local sourcing and still default to centralized channels if the local option creates too much friction.
Common local procurement barriers
Availability uncertainty
Local supply may be real but not visible early enough for buyer planning.
Small-lot friction
Small orders can require disproportionate time for communication, pickup, delivery, invoicing, and exception handling.
Seasonal mismatch
Buyer demand may be steady while local supply is seasonal, variable, or weather-dependent.
Documentation burden
Retailers, institutions, and distributors may need traceability, food safety, vendor onboarding, insurance, lot records, or other documentation before they can buy routinely.
Delivery and routing limits
A buyer may not have staff time to coordinate many individual farm pickups or small deliveries.
Underproduction can be rational
When sell-through is uncertain, farms may limit planting, avoid diversification, delay investment, or stay within familiar direct-sales channels. This is not necessarily a lack of ambition. It can be a rational response to unsold-perishable downside risk.
Current output versus feasible output
A bounded feasibility model should distinguish current observed output from feasible output under improved coordination. Current output reflects existing constraints. Feasible output asks what can be produced and sold if demand visibility, buyer reliability, routing, aggregation, and handling improve.
Current observed output
What farms actually produce and sell under present conditions.
Feasible local supply
What farms could plausibly produce and sell within conservative capacity bands, given better sell-through confidence and coordination.
Capacity realization
The portion of feasible output that becomes economically rational to produce because the risk of unsold product is reduced.
Local agriculture may be supply- and coordination-constrained
The corrected market frame separates total demand from feasible supply. A county or region may contain far more produce demand than current local production can satisfy. In that case, the central problem is not whether demand exists in the abstract. The central problem is whether local supply can be grown, aggregated, and delivered into buyer-usable channels.
Four levels of the local market
Total regional produce demand
All produce demand in the region, regardless of whether it can be served locally.
Localizable demand
The subset of demand that could realistically be served by local or regional supply given season, radius, product type, and buyer class.
Feasible local supply
The local production capacity that could plausibly be available under bounded assumptions.
Recapturable friction
The value currently lost to fragmentation, transport, shrink, procurement friction, volatility, and under-realized capacity.
Evidence note: The market analysis distinguishes total regional produce demand, localizable demand, feasible local supply, and recapturable friction. It identifies the Summit County case as supply- and coordination-constrained rather than demand-constrained, because current observed produce output is far below total addressable produce demand.
Four-layer local market funnel
Suggested figure: Four-layer funnel: regional produce demand to localizable demand to feasible local supply to recapturable friction.
B. The Underuse Cycle and the Reinvestment Integration Cycle
Fragmented local supply creates a stable underuse cycle. Buyers do not rely on farms because supply is inconsistent. Farms do not expand because demand is uncertain. Infrastructure does not accumulate because volume is irregular. The system adapts to uncertainty and calls that adaptation reality. Coordination matters because it can reverse the cycle: sell-through certainty lowers risk, lower risk supports reinvestment, reinvestment improves reliability, and reliability brings repeat purchasing back into the system.
3. The Current Cost and Operation of Centralized Agriculture
The visible price hides a delivered-cost stack
Food prices do not only reflect the crop. They also reflect the cost of moving, cooling, storing, packaging, financing, merchandising, documenting, and coordinating the product after it leaves the farm.
Delivered cost
Delivered cost can be expressed simply:
Delivered Cost = Production Cost + Delivered Overhead
Production cost is only one part of the buyer's experienced cost. Delivered overhead determines whether a product reaches the buyer in the right form, at the right time, with acceptable reliability.
Refrigerated distribution chains
Perishable produce often requires controlled handling across long distances. Refrigerated transport can preserve product value, but it also adds cost, energy use, scheduling complexity, dwell-time risk, and dependency on larger distribution infrastructure.
Cold-chain burden
Transport
Distance adds fuel, labor, vehicle, scheduling, and routing costs.
Refrigeration
Temperature control adds equipment, energy, monitoring, and failure risk.
Handling
Every handoff can increase damage, delay, and administrative burden.
Storage
Cold storage can extend selling windows but requires capital, space, management, and throughput.
Shrink
Spoilage, quality loss, damage, rejection, and missed timing reduce the value of produced food.
Post-farm marketing costs are structurally large
Centralized agriculture often appears efficient because the system has become highly optimized around post-farm functions. Processing, transportation, logistics, wholesale, retail, marketing, merchandising, and administration can dominate the final food-cost stack.
Why centralized systems still win despite overhead
Centralized systems retain advantages when:
Products require large uniform volume.
Regions cannot grow the product locally.
Long-storage commodities can move cheaply in bulk.
Buyers need year-round uniformity.
Procurement must be standardized across many locations.
Compliance and traceability are already integrated into large systems.
Transportation networks are dense enough to lower per-unit cost.
Efficiency and loss can coexist
A centralized system can be efficient in one dimension and loss-heavy in another. It may achieve low unit cost while carrying waste, long transport, labor burden, shrink, and complex administrative overhead.
The mistake to avoid
The argument should not claim that centralized agriculture is irrational or useless. The stronger claim is that centralized systems are optimized for certain constraints, and that some of those constraints create avoidable cost when local supply could satisfy demand through shorter, better-coordinated channels.
Evidence note: The market recapture article defines delivered overhead as all non-growing costs required to sell a unit of product: transport, handling, spoilage, coordination, payments, communications, and scheduling. The SBIR proposal also identifies post-farm marketing functions as a major part of the food-cost stack.
Delivered-cost stack
Suggested figure: Delivered-cost stack comparing centralized baseline, uncoordinated local supply, and coordinated local supply.
C. Value Is Not Price
The cheapest visible price is not always the highest-value system. A price can hide waste. A high price can hide producer stress. A low price can depend on risk being placed somewhere weaker. Once value is measured across waste, time, risk, resilience, labor, logistics, and planning confidence, the question changes. The issue is no longer whether better food must always cost more. The issue is whether preventable loss has been mistaken for unavoidable cost.
4. Local Adjacency and Market Recapture
Local adjacency is a cost-structure advantage only when it becomes usable
Local supply has a physical advantage: proximity. But proximity alone does not create economic advantage. A nearby farm that is invisible, unpredictable, difficult to order from, or hard to verify may remain operationally distant.
Adjacency becomes valuable when supply is
Discoverable
Buyers can see what exists.
Schedulable
Buyers can see when product can move.
Aggregatable
Multiple farms can collectively fill useful order sizes.
Substitutable
Buyers can accept reasonable alternatives when exact products are unavailable.
Auditable
Buyers can trust product identity, source, handling, and basic documentation.
Repeatable
Transactions can become routine rather than custom one-off efforts.
Market recapture is bounded replacement of nonlocal supply
Market recapture does not mean replacing the entire global or national food system. It means replacing the portion of nonlocal supply that is currently used because nearby supply is too fragmented, too hard to verify, too hard to order, or too unreliable for buyers.
Recapture occurs where local supply becomes
Discoverable.
Schedulable.
Competitively delivered.
Reliable enough for repeat orders.
Diverse enough for useful substitution.
Dense enough for workable routes.
Transparent enough for buyer confidence.
Adjacency compresses delivered overhead
Local adjacency does not guarantee lower production cost. Its advantage is the potential to compress delivered overhead.
Overhead that local coordination can reduce
Distance
Shorter routes can reduce fuel, labor time, vehicle use, and product age.
Time
Shorter harvest-to-delivery windows can improve freshness and reduce spoilage exposure.
Handling
Fewer handoffs can reduce damage, delay, and administrative exceptions.
Refrigeration intensity
Shorter movement windows can reduce some reliance on long refrigerated distribution chains, depending on product and season.
Procurement friction
A coordinated regional layer can reduce buyer search, communication, ordering, and substitution burden.
Waste and shrink
Better timing between supply and demand can reduce unsold or degraded product.
Variety becomes a coordination advantage
A transparent local market can reward variety because diverse demand often tolerates substitution. A single farm may not need to satisfy every order. A coordinated region can behave like a supply portfolio.
Local supply as a portfolio
Cross-farm aggregation
Multiple farms can jointly satisfy buyer demand.
Product substitution
Related products can fill practical buyer needs when exact products are unavailable.
Seasonal planning
Buyers can be prepared for what local supply can provide during each seasonal window.
Risk dispersion
Farms are less exposed to the failure or price weakness of a single crop.
Regenerative and lower-input practices can become legible
Production practices do not create market value unless buyers can see, trust, and act on them. Coordination can make attributes more legible: soil stewardship, lower-chemical practices, rotational diversity, provenance, harvest timing, or freshness.
The bounded claim
The claim is not that regenerative practice automatically wins. The claim is that transparency and adjacency can make differentiated practices more economically selectable where buyers value those attributes and where delivery remains competitive.
Evidence note: The market recapture article defines local market recapture as replacement of imported or nonlocal supply when local goods become discoverable, schedulable, and competitively delivered. It also states that adjacency compresses delivered overhead rather than guaranteeing lower production cost.
Adjacency map
Suggested figure: Adjacency map showing farms, buyers, aggregation points, delivery radii, and product movement windows.
D. The Mirror Mechanism
The centralized system proves that coordination works. The local system asks whether that mechanism can be mirrored without reproducing central ownership. The mirror is not one corporation. The mirror is shared legibility: many independent farms becoming usable as one regional source when useful, without becoming one company. What appeared to be an unavoidable defeat becomes a design problem.
5. Coordination Infrastructure: Historical Precedent and Existing Models
Regional food systems have always needed shared interfaces
Local food systems were never only informal. They have depended on shared physical, commercial, and social interfaces that made supply and demand visible to one another.
Historical coordination infrastructure
Food terminals
Food terminals concentrated producers, buyers, transport, storage, inspection, and price discovery in one place.
Market houses
Market houses gave buyers and sellers repeated points of contact and made product availability more visible.
Rail-linked produce markets
Rail-connected markets compressed the distance between regional production and urban demand.
Auctions
Auctions created dense repeated transactions and supported price discovery.
Cold storage
Storage extended selling windows for perishable goods and reduced the finality of timing failure.
Trust networks
Repeated relationships allowed quality expectations, reputation, and buyer confidence to accumulate.
Knowledge commons
Shared information about varieties, timing, growing practices, and market expectations functioned as infrastructure.
The coordination function is old
The form of coordination changes, but the function remains consistent.
The function is to
Make supply visible.
Make demand visible.
Reduce search cost.
Accelerate turnover.
Support price discovery.
Compress logistics.
Preserve trust.
Give fragmented producers access to buyers.
Give buyers a stable interface.
Existing models solve fragments of the same problem
Modern local agriculture models already prove that coordination failures are real. Each model solves a part of the problem.
Food hubs
Food hubs aggregate supply, coordinate distribution, and often help local products reach wholesale or institutional buyers.
What food hubs solve
Aggregation.
Storage.
Some logistics.
Buyer access.
Some verification.
What can remain unresolved
High fixed operating costs.
Hub bottlenecks.
Thin margins.
Limited interoperability across systems.
Dependence on physical infrastructure.
Cooperatives
Cooperatives pool ownership, risk, infrastructure, or bargaining power.
What cooperatives solve
Shared identity.
Shared assets.
Risk pooling.
Member governance.
What can remain unresolved
Governance overhead.
Decision latency.
Capital constraints.
Variable participation burden.
CSAs and direct-sales models
CSAs create demand commitment and direct relationships.
What CSAs solve
Upfront cash flow.
Buyer loyalty.
Seasonal participation.
Producer-consumer trust.
What can remain unresolved
Institutional procurement.
Flexible substitution for buyers.
Wholesale reliability.
Aggregated supply visibility.
Farmers markets
Farmers markets create discovery, community visibility, and direct buyer relationships.
What farmers markets solve
Public access.
Product storytelling.
Trust formation.
Direct sales.
What can remain unresolved
Recurring procurement.
Delivery reliability.
Buyer documentation.
Wholesale volume.
Weather and attendance dependence.
Marketplaces and local-commerce platforms
Marketplaces improve listing, search, ordering, and buyer-seller discovery.
What marketplaces solve
Visibility.
Listings.
Basic ordering.
Some inventory display.
Multi-vendor storefronts.
What can remain unresolved
Live availability freshness.
Route-aware fulfillment.
Product substitution.
Cross-system interoperability.
Buyer-side procurement integration.
Documentation and traceability confidence.
The remaining gap is buyer-side orchestration
The missing layer is not another general farm tool and not another consumer-facing directory. The unresolved product is coordinated supply: a buyer-facing ability to source from fragmented local farms as if they were a legible, schedulable, auditable regional supply pool.
Buyer-side orchestration requires
Shared availability
Current supply must be visible with freshness windows.
Shared product meaning
Products, units, grades, quantities, timing, and attributes must be comparable.
Aggregated fulfillment
Multiple farms must be able to jointly fill useful orders.
Procurement reliability
Buyers must experience less friction, not more.
Trust and documentation
Supply must be credible enough for recurring retail, restaurant, institutional, or hub purchasing.
Open participation
Farm-side participation must remain low-friction enough for supply density to build.
Evidence note: The historical local food system material describes wholesale terminals and market houses as shared physical and social interfaces that lowered search cost, accelerated turnover, and produced price discovery. The competitive analysis identifies buyer-side local procurement orchestration as the strongest starting position, distinct from generic farm ERP, consumer discovery, or universal data-language positioning.
Coordination infrastructure matrix
Suggested figure: Matrix comparing historic coordination infrastructure and modern local agriculture models against the unresolved buyer-side orchestration gap.
E. Coordination Infrastructure Exists, but Coordinated Supply Is the Product
The need is not new. Regional food systems have always required interfaces that make fragmented supply usable. Modern models already solve parts of that problem, which proves the pain is real. The unresolved product is coordinated supply itself: local availability made legible enough for buyers, open enough for farms, and reliable enough to become routine. Farm software is the wedge. Coordinated supply is the economic product.
6. The Enabling Data Layer
Coordination requires shared operational meaning
Data transmission is not interoperability. Two systems can exchange a spreadsheet, file, form, API response, or JSON payload while still failing to share meaning. A buyer may receive product information and still not know whether it can be compared, ordered, substituted, verified, or fulfilled.
Transmission agreement is not enough
Transmission agreement answers
Can the file be opened?
Can fields be parsed?
Can the payload be received?
Operational interoperability asks
What does the product mean?
What unit is being used?
What timing window applies?
What constraints matter?
What substitutions are allowed?
What documentation supports trust?
How does the data change over time?
Local food data is structurally heterogeneous
Farm and buyer systems may differ in ways that matter operationally.
Product identity
The same product may be described by variety, crop, pack size, grade, brand name, market category, or buyer-specific shorthand.
Quantity and unit
A product may be measured in pounds, cases, bunches, units, pallets, bins, shares, or informal order descriptions.
Timing
Availability may refer to harvest window, pickup window, delivery window, standing order schedule, or estimated readiness.
Attribute meaning
Production practices, freshness claims, local provenance, certifications, or handling conditions may need explicit definition.
Constraint meaning
Buyer requirements may include pack size, temperature, insurance, traceability, food safety, lead time, substitute rules, or delivery cadence.
Failure modes
Schema drift
Data structures change across systems or over time.
Semantic drift
The label stays the same while the operational meaning changes.
Adapter explosion
Every pair of systems requires a custom translation.
Stale availability
Supply appears available after the real selling window has closed.
Context loss
Data leaves the local system but loses the assumptions that made it meaningful.
Centralized capture
One platform solves coordination by forcing everyone into its own rules, replacing fragmentation with dependency.
Schema-first procurement data
A coordination layer must define the minimum shared structure needed for local produce procurement.
Minimum procurement objects
Farm identity
Who can supply product and under what participation terms.
Product identity
What product is being offered.
Quantity
How much is available and in what unit.
Timing
When it can be harvested, picked up, delivered, or committed.
Location
Where product is produced, stored, or transferred.
Handling constraint
Temperature, packaging, wash-pack status, grade, or shelf-life needs.
Buyer demand
What buyers need, when, in what quantities, and under what service threshold.
Substitution rule
Which alternatives are acceptable.
Provenance and trust signal
Where data came from, when it was updated, and what record supports it.
Federated participation without one platform owner
A shared data layer should allow participants to keep their own systems while publishing enough structured meaning to coordinate.
The third path
Not isolated independence
Farms remain autonomous but operationally fragmented.
Not platform consolidation
Farms join one central system and surrender rules, data posture, or market access to the platform owner.
Coordinated independence
Farms remain independent by default and coordinate when useful through shared schema, mapping, provenance, and buyer-facing procurement logic.
The bounded technical claim
The near-term claim should remain narrow:
A schema-first, federated data layer can make local produce procurement legible enough to test coordinated sourcing.
What this claim includes
Procurement interoperability.
Shared operational meaning.
Structured availability.
Buyer-facing legibility.
Product comparison.
Aggregation across farms.
Substitution and timing logic.
Provenance and freshness signals.
What this claim does not include
A finished universal semantic internet.
Full automation of farm conditions.
Complete agronomic optimization.
Elimination of all human judgment.
Elimination of trust, governance, or verification work.
Evidence note: The self-describing semantic grammar material distinguishes transmission agreement from operational interoperability and identifies schema drift, semantic drift, adapter explosion, mapping, semantic difference, and provenance as core concerns. The shared-operational-meaning material frames the problem as inoperability: data exchange without reliable shared operational meaning.
The false choice is between remaining independent and remaining fragmented, or joining a central platform and accepting its control. The third path is coordination without ownership consolidation: independent by default, coordinated when useful, legible through shared syntax, and able to participate without surrendering local autonomy. This is where the diagnosis becomes constructive. The system being proposed is not a new gatekeeper; it is a way to make cooperation operational.
7. Experimental Design, Feasibility Window, and Critical Point
The proposal reduces to a bounded feasibility question
The central test is not whether local food is desirable. The central test is whether coordination can identify at least one credible sourcing scenario where both sides improve or remain protected.
Governing feasibility question
Can an open-source coordination framework identify a local sourcing scenario where:
Participating farms improve expected position
Buyers remain non-worse-off on delivered cost and service
Two-sided feasibility
A scenario is viable only where producer-side improvement overlaps with buyer-side usability.
Producer-side condition
Farms must improve or at least not worsen relative to baseline.
Producer-side measures
Sell-through certainty.
Margin stability.
Income volatility reduction.
Waste reduction.
Capacity realization.
Reduced marketing burden.
Better planning confidence.
More reliable timing for labor and harvest.
Better use of existing production capacity.
Buyer-side condition
Buyers must remain non-worse-off relative to comparator sourcing.
Buyer-side measures
Delivered cost.
Fill rate.
Service reliability.
Ordering friction.
Substitution success.
Documentation confidence.
Product freshness.
Delivery consistency.
Procurement time.
Feasibility window
The feasibility window is the overlap between producer improvement and buyer non-worse-off conditions.
Farm-only benefit is insufficient
If a scenario helps farms but creates unacceptable buyer cost, friction, or service failure, it is not durable.
Buyer-only benefit is insufficient
If a scenario helps buyers by squeezing farms, it does not solve the rural-development problem.
Phase I research design
The study should test coordination through a bounded, capacity-banded model rather than a full agronomic optimization system.
Minimum technical outputs
Coordination schema
A minimum representational structure for farm-side, buyer-side, and scenario-side variables.
Prototype coordination engine
A system that ingests structured inputs, normalizes key fields, applies bounded constraints, and produces interpretable scenario outputs.
Local feasibility simulation
A parameterized model using conservative capacity assumptions, local supply conditions, buyer constraints, routing assumptions, and service thresholds.
Decision-oriented feasibility report
A report that states pass/fail conditions, scenario results, binding constraints, and Phase II implications.
Scenario variables
Farm-side variables
Current output.
Capacity bands.
Crop timing windows.
Historical sell-through.
Unsold or discounted volume.
Handling capacity.
Storage capacity.
Labor bottlenecks.
Price bands.
Documentation readiness.
Buyer-side variables
Weekly basket.
Delivery frequency.
Acceptable substitutes.
Order lead time.
Service-level floor.
Cost threshold.
Quality requirements.
Vendor onboarding requirements.
Audit or compliance requirements.
Operational variables
Route distance.
Stop density.
Vehicle type.
Handling touches.
Spoilage incidence.
Payment lag.
Aggregation point availability.
Cold-chain requirement.
Timing alignment.
Scenario ladder
Scenario 01 - Proof lane
A narrow product category, limited buyer set, limited geography, and simple fulfillment pattern.
Purpose
Test whether coordination reduces friction.
Find the smallest useful supply-demand lane.
Avoid overbuilding before the mechanism is visible.
Scenario 02 - Single-hub routine
A recurring sourcing pattern with enough density to become operationally routine.
Purpose
Test repeat purchasing.
Test delivery cadence.
Test buyer reliance.
Test farm planning confidence.
Scenario 03 - County network
A county-scale group of farms and buyers where aggregated availability becomes commercially legible.
Purpose
Test participation density.
Test substitution across farms.
Test buyer-side usability.
Test coordinated seasonal planning.
Scenario 04 - Regional multi-hub
Multiple county or regional nodes coordinating through shared standards and procurement interfaces.
Purpose
Test broader replication.
Test interoperability across regional nodes.
Test whether scaling can occur without becoming a single chokepoint.
The critical point
The critical point is the threshold at which scattered local supply begins behaving as coordinated regional supply.
Conditions of the critical point
Enough farms participate
Supply density is high enough to matter.
Enough products are legible
Buyers can understand what is available and what constraints apply.
Demand is visible early enough
Farmers can plan before risk becomes irreversible.
Aggregated supply fills useful orders
Buyers can source at operationally meaningful sizes.
Transactions repeat
Local sourcing becomes routine rather than exceptional.
Trust accumulates
Data freshness, delivery reliability, and documentation confidence support continued use.
Negative results still matter
A negative result is not wasted effort. It identifies which constraint prevents the system from working under current assumptions.
Possible binding constraints
Insufficient supply.
Insufficient buyer density.
Delivery cost too high.
Product mix too limited.
Timing mismatch.
Buyer friction too high.
Farm benefit too low.
Participation threshold too difficult.
Documentation requirements too costly.
Data freshness too hard to maintain.
Evidence note: The SBIR proposal defines Phase I as an approximately eight-month feasibility study with minimum schema definition, prototype coordination engine development, bounded data collection, scenario simulation, and feasibility decision reporting. Success is defined by identifying a credible two-sided feasibility window or producing decision-grade evidence that none exists under tested assumptions.
Suggested figure: Scenario ladder from proof lane to single-hub routine to county network to regional multi-hub.
G. FND Called to Action
The argument begins with a shared desire and ends with a testable obligation. Better food, lower cost, easier access, and stronger local economies do not need to remain separate hopes if the obstacle is coordination rather than value itself. Centralized systems have already shown that coordination can make supply powerful. Regional history has already shown that local food systems need shared interfaces. Existing models have already shown that people will build and pay around fragments of this problem.
FND is called to the missing layer: making independent local supply legible enough to test whether stranded agricultural value can be recovered. The work is not to promise that local agriculture replaces everything. The work is to locate the threshold where coordination makes local sourcing practical, build only where the two-sided window exists, and let evidence decide whether the system should proceed, revise, or stop.
The call is not to ask buyers to subsidize values. The call is to test whether coordination can make the better option economically practical.
The problem, plainly
Local food is full of data: what is being grown, where, how much, when it will be ready, what it costs to produce, what it cost to sell. The data exists. It just lives in seven file formats across forty disconnected spreadsheets, three POS exports, two newsletter inboxes, and a clipboard on a barn door.
Every existing answer to this is a platform. The producer enters their data into someone else's schema, which lives on someone else's server, which charges a subscription that grows with success. The data is no longer the producer's; it is the platform's. Most of these platforms close within five years and the data goes with them.
The other answer — file-shipping between operations — solves the wrong problem. You can't coordinate a local food system on PDF attachments. Files are snapshots. Coordination requires references that stay current, are understood the same way by every reader, and survive when any one participant changes their software.
The approach, walked step by step
The thing FND is building is not a platform. It is a small, well-defined coordination grammar — a way of describing what a local food operation has and needs that is the same wherever it is read — plus a runtime that lets operations exchange references to each other's real-time state without giving up ownership of their data.
The grammar is self-describing. Anything written in it includes its own definitions, so a reader new to the system can interpret a message without consulting an external schema registry that may not exist next year. That part is the Mycelial Ontological Schema; the long-form is linked below.
The runtime is shape-addressed. A reference does not point at a row in a database; it points at a structure — "a Friday CSA slot for 12 customers in the 44106 zip code with the produce list still pending" — and resolves to the operations that currently hold that shape. Operations come and go; the shape is stable.
The interoperability is structural rather than negotiated. Two operations do not need a bilateral integration agreement to talk; they need to speak the same grammar. The cost of joining the network is the cost of describing your own operation correctly, which you have to do anyway.
The result is that the local-food coordination layer can grow node-by-node without a central authority. The software is real today; the network it can become is being built toward one operation at a time, opt-in always.
Further reading
Inline depth links. Each one is its own article in the archive.
