UFTA

Hosts — v0

The human edge of the network.

A Scheduling Captain — a location Host — is a provider who takes on-the-ground responsibility for a place. They steward the relationship between a location and the vendors who serve it. UFTA's network senses demand and routes at a distance; the Host supplies the one thing it cannot: locality.

Why a network needs a person at the location

A network is excellent at sensing demand and matching supply at a distance. It cannot stand in a parking lot and smell the generator exhaust, notice the trash flow is wrong, or read whether the location's owner actually likes the trucks that showed up. Who fixes a problem hundreds of miles away from behind a screen? Nobody.

The Host is at the location regularly. They hear the issues and they fix them. That is the missing organ — ground truth and relationship at a single place — and it is why UFTA builds the human edge in from day one rather than pretending software alone is enough.

What a Host does

  • Stewards a location — the on-the-ground relationship between a venue and the vendors who serve it. Stewardship, not ownership.
  • Gets priority scheduling — a bounded ordering preference at their venue. Priority orders; it never reserves or blocks.
  • Can help gate participation — advisory by default. A hard gate is granted only when the location explicitly delegates that authority, so UFTA stays neutral unless a place asks for teeth.
  • May take a rev-share on paid events — negotiated and settled off-platform; UFTA records the relationship, it doesn't move the money.
  • Carries the feedback loop — food quality, noise, fixes, what worked. Receipted, and feeding the trust signal for both the venue and the vendors.

A warm word, with the teeth written down

"Host" sets the tone on purpose — welcoming, present, fostering. The point is to push locations toward someone local who hears them. But the authority a Host holds never lives in the title. It lives in explicit, negotiated grants — gate authority and rev-share terms — recorded and revocable. Host first; delegated authority second.

One active Host stewards a venue at a time. Every host action leaves a receipt, and a vendor who contests a gate decision has a documented dispute path.

It generalizes beyond food

A location is a venue; a Host is a steward; vendors are providers of any kind. So a city could steward its public spaces and reach every nearby vendor with a few clicks; an event coordinator is simply a Host over a one-off event, scheduling and gating participation for that day. The primitive ships without assuming a Host is a food vendor — the city tier is configuration, not a rebuild.

Becoming a Host

Interested in stewarding a location — a market, a lot, a recurring event, a city's public spaces? Reach hosts@ufta.online with the place you'd steward, your relationship to it, and what authority (if any) the location is prepared to delegate.