UFTA

Charter — v0

Why UFTA exists, and what it will not do.

UFTA is a neutral, industry-first organization built to improve the independent food economy for everyone in it — vendors, organizers, commissaries, customers, and the apps that serve them.

Purpose

The food economy is too often shaped by who can afford the rent on a storefront, not by who can cook, host, or serve. UFTA exists to invert that: to make quality, reliability, and trust the things that get rewarded — independent of any single app, platform, or location advantage.

UFTA provides shared infrastructure: open standards, a transparent trust system, scheduling rails, and proofs. Consumer apps, partner platforms, and personal agents ride those rails. The customer chooses the surface they like; UFTA makes sure the underlying signal is real, fresh, and fair.

Non-negotiables

Neutrality
UFTA does not play favorites among apps, vendors, or providers. Requirements are published and applied consistently. Operating an app on UFTA standards earns no preferential treatment.
Transparency
Trust tiers, scoring inputs, and eligibility rules are documented, versioned, and auditable. If a factor influences selection or visibility, it is published.
Interoperability
UFTA standards are designed to be licensed and implemented by many front-ends. Providers are not locked to a single consumer app.
Freshness and truth
Scheduling and compliance data carry timestamps, sources, and clear expiry behavior. Stale data is marked stale.
Due process
Flags, downgrades, and disputes follow documented workflows with appeals. Receipts are durable and readable by the parties involved.
Privacy and minimization
UFTA collects the minimum data required to operate safely and reliably. Public surfaces show status and expiry indicators, not raw documents or identifiers.

What UFTA will and will not do

Will

  • Publish open, versioned standards for scheduling, compliance, operational signals, and disputes.
  • Operate the trust-tier ladder (U0–U4) with documented requirements and revocation triggers.
  • Provide partner-program access on consistent terms, regardless of relationship.
  • Maintain a structured community signal with moderation and escalation.
  • Provide dispute paths and audit trails for every decision that affects standing.

Will not

  • Grant standing on the basis of payment, relationship, or favoritism.
  • Use hidden ranking factors. Anything affecting selection or visibility is documented.
  • Lock providers into a single consumer app.
  • Publish private compliance details unnecessarily. Public-vs-internal fields are explicit per standard.

Governance (v0)

UFTA's governance exists to keep neutrality, consistency, and safety stable across releases. Decisions are made within four domains: standards (scheduling, compliance, signals), trust program (tiers, revocation, appeals), partner program (licensing, API access), and safety (food safety, fraud, abuse).

Standards change through versioned releases (v0, v0.1, v1…). Each change starts as a written proposal with rationale and backward-compatibility notes, opens a review window for partners and members, and ships with an effective date and deprecation plan for anything it supersedes.

What's intentionally out of scope

  • Operating a single consumer app. UFTA is the backbone; the apps ride on top.
  • Setting prices for providers. Pricing belongs to the provider.
  • Adjudicating taste. UFTA verifies operational truth, not opinion.