Solstice FC
← All specs

Solstice FC — Founding Architecture

draftInformed by: round-01 (Reform vs. Replace, AFF won 14-13) · round-03 (Geographic Scope, NEG won 16-15) · championship-final (Community-First vs. Systems-First, AFF won 2-1)

Founding Architecture

Solstice FC is a community-first youth soccer organization that builds systems. The community governs; systems serve. Neither stands alone.

This document synthesizes the architectural decisions from three debate verdicts into a coherent founding design. Each section traces its reasoning to the debate that resolved it.

Core Identity

Informed by: Championship Final (AFF won 2-1)

Solstice FC is governed by its community. When community judgment and systems logic conflict, the community has final authority -- exercised through deliberative democratic process with high procedural bars. This is not community-without-systems. Every structural protection built across the debate series is retained. The community owns those protections and holds the ultimate power to modify them.

Legitimacy is the foundational value, not optimization. Every system, process, feedback loop, and policy must pass one test: does this preserve the community's sense of ownership and agency? Systems that produce better outcomes but erode ownership are rejected in favor of systems that produce good-enough outcomes while preserving ownership. Optimization is pursued within the constraint of legitimacy, not the other way around.

The founding architecture is a community act. The spec's structural protections -- pro/rel, coaching certification, minimum standards, cooperative governance -- are adopted by the founding community through deliberative process, not imposed by founders and accepted through opt-in consent. The founding clubs debate, negotiate, and ratify the charter together. This is slower than presenting a finished design. It produces deeper commitment.

Systems thinking is the operating methodology within this identity. Feedback loops, leading indicators, evidence-based evaluation, incentive alignment -- these are tools the community uses to make better decisions. The community governs the tools. The tools do not govern the community.

Platform Strategy: Affiliate, Don't Build

Informed by: Round 1 (AFF won 14-13)

Solstice FC affiliates with existing competition platforms -- ECNL, MLS NEXT, or both where dual-platform membership is permitted. The competition calendar, showcase events, and college exposure pathways are infrastructure Solstice FC rents, not builds.

The debate established that building a parallel league structure requires solving the cold-start problem, securing unproven funding models, and constructing national infrastructure before a single player benefits. None of the NEG's proposed funding mechanisms (corporate sponsorship coalitions, public funding, professional club solidarity payments) have US youth soccer precedent at the required scale. By contrast, affiliating with an existing platform is something a real club in a real city can execute immediately.

The real innovation happens at the club level. Both debaters converged on this point: the platform provides scheduling and exposure; the club provides the development model and economic structure. Solstice FC differentiates through its business model and governance, not its competition platform.

Geographic Design: National Protocol, Local Test

Informed by: Round 3 (NEG won 16-15)

Solstice FC architects its governance model, data schema, fee structure framework, and replication playbook as portable specifications from day one. The first instance launches in San Diego, but the design scope is national.

This follows the CrossFit affiliate model and the KIPP charter school model: a portable design, rigorously specified, tested against local reality. The distinction the Round 3 verdict drew is precise -- "design national, test local" is not the same as "start local, then generalize." Design scope determines what you build. If you start hyperlocal, your technology, governance, and economics are shaped by one city's feedback. If you design national, they are shaped by the requirement to work everywhere, tested against one city's reality.

Protocol Layer vs. Policy Layer

The architecture separates two layers:

Protocol layer (location-independent): How clubs join the cooperative. How players transfer between member clubs. How competitive tiers are structured. How data flows between clubs and the central cooperative. How coaching certifications are recognized. These specifications must work in any US metro area without modification.

Policy layer (locally determined): Fee amounts. Practice and game schedules. Facility partnerships. Club-to-club agreements. Local sponsorship deals. These are set by each city's member clubs based on local market conditions.

Using the Existing Evidence Base

The local pilot is not a blank-slate discovery process. Thirteen years of Development Academy data, fifteen years of ECNL data, and sixty years of AYSO data document what breaks in youth soccer governance. The national protocol is designed from that evidence base and validated locally. The goal is to validate, not discover.

Standalone Viability

The national architecture should enable network effects -- player records, coaching certification portability, cross-market tiering -- but must not depend on them for the first city's success. San Diego must work as a standalone instance.

Revenue Model: The Unsolved Problem

Informed by: Round 1 (AFF won 14-13)

The Round 1 NEG correctly identified that the AFF has no proven answer for funding a no-fee or low-fee club at scale within an existing platform. The AFF's strategy depends on Solstice FC solving the revenue problem at the club level. This is the single most important open design problem in the spec.

The revenue model must not depend on family fees as the primary funding source. Priority areas for development:

  • Sponsorship and community investment as primary revenue
  • Public-private partnerships (parks and recreation facility access, municipal grants)
  • Professional club pipeline agreements (if MLS NEXT affiliated, negotiate development fees for players who sign professional contracts)
  • A clear financial model that demonstrates operational viability without pay-to-play economics

Until this problem is solved with a working model, the architecture remains incomplete.

Proof of Concept Before Advocacy

Informed by: Round 1 (AFF won 14-13)

Solstice FC's first priority is operational viability, not systemic reform advocacy. The winning argument from Round 1 was direct: build one club that works, then let results drive ecosystem change.

The sequence is:

  1. Demonstrate that a community-governed, low-fee club can compete at the ECNL/MLS NEXT level
  2. Demonstrate that it can develop players effectively
  3. Let competitive results create the case for replication
  4. Advocacy follows evidence

This means the spec must include measurable milestones with timelines. If milestones are not met within the existing-platform model, the parallel structure option is revisited with specific criteria for when to pivot.

Contingency: Platform Resistance

Informed by: Round 1 (AFF won 14-13)

The Round 1 NEG's incentive alignment argument remains valid as a standing risk. Organizations whose revenue depends on family fees face a structural contradiction when asked to accommodate a model that eliminates those fees. If Solstice FC encounters platform-level resistance to its model -- rules changes that effectively require fee structures, exclusion from key showcases, or governance actions that undermine the cooperative's operating model -- that is the trigger to reconsider the parallel structure approach.

The NEG's argument is treated as a contingency plan, not dismissed.

Travel as a System Design Problem

Informed by: Round 3 (NEG won 16-15)

Travel cost and burden in youth soccer is a symptom of misaligned incentives, not a geography problem. Clubs need revenue, which drives roster expansion, which drives wider geographic reach, which drives more travel. A nationally designed incentive structure that caps roster fees and funds clubs through shared revenue eliminates the travel incentive at its root.

The fee and revenue model must remove the incentive for clubs to expand geographic reach to generate revenue. When the incentive is corrected, local competition becomes the natural equilibrium.


Dissents and Risks

The Theorist's Dissent: Community-First Contains a Structural Tension

Source: Championship Final, Theorist verdict (NEG won 18-16)

The Theorist identified that the AFF's community-first identity relies on systems-designed constitutional protections, which creates an internal tension. If the community is sovereign, then supermajority protections are themselves a systems constraint on community sovereignty. The AFF wants community-first identity with systems-first guardrails.

This tension is acknowledged as real and intentional. It is the defining feature of constitutional democracy: the community is sovereign, the constitution constrains sovereignty, and the community can amend the constitution. This recursive structure is the design. It is not pure community-first (the constitution constrains) and not pure systems-first (the community can amend). It is community sovereignty exercised through systems architecture.

The practical risk: if the founding community does not understand this tension, they may interpret "community-first" as "the community can do whatever it wants by simple majority." The charter must make the recursive structure explicit. Community-first means the community has final authority, not that the community faces no procedural requirements.

Convergence to Mediocrity

Source: Championship Final, all three judges acknowledged

Community-first governance naturally drifts toward median preferences. The median preference in a broad-based youth soccer organization tends toward comfortable mediocrity -- lower standards, fewer demands, less disruption. The NEG's convergence-to-mediocrity argument was the strongest unanswered systemic risk in the tournament.

The spec-level response is cultural, not mechanical: Solstice FC must build a culture of evidence-based deliberation. Every structural decision brought to a membership vote must be accompanied by evidence briefings, adversarial argument (the debate format itself is a model), and explicit articulation of tradeoffs. The goal is a community that makes rigorous decisions, not a community that votes its comfort level.

This is a risk that cannot be fully designed away. It must be actively managed through norms, not rules.

Revenue Model Fragility

Source: Round 1, NEG's strongest unanswered argument

Neither debater in Round 1 provided a proven revenue model for a no-fee club competing at the ECNL/MLS NEXT level. The AFF's strategy depends on solving this problem, but the problem remains unsolved. If the revenue model fails, the entire architecture collapses -- community governance, national portability, and platform affiliation all depend on a financially viable club.

This is the highest-priority risk in the spec. It should be treated as a blocking problem: do not scale until the revenue model is validated in the first city.

Incentive Misalignment with Host Platforms

Source: Round 1, NEG's incentive alignment argument

ECNL and MLS NEXT derive revenue from club membership fees, which are ultimately funded by family payments. A club that eliminates family fees threatens the economic logic of the platform. The platform has structural incentives to resist or marginalize such a club. This may manifest as rule changes, showcase exclusion, or informal pressure.

The contingency plan (pivot to parallel structure) requires its own feasibility analysis, which has not been completed. The trigger criteria for when to pivot should be defined in advance, not determined in the moment of crisis.

Timeline Accountability Gap

Source: Round 1, neither debater provided timelines

The Round 1 verdict noted that neither debater offered a timeline. The architecture spec inherits this gap. Without measurable milestones -- club operational by when, first season of platform competition by when, first cohort developed by when -- there is no mechanism to evaluate whether the strategy is working or whether a pivot is needed.

This gap must be closed before the architecture moves from draft to ratified status.