Building STANDING
STANDING models how public perception changes around connected entities — teams, players, coaches, companies, politicians, and public figures. FIFA World Cup 2026 is the first complete ecosystem being used to test that model.
The World Cup is not the product. It is the first complete perception ecosystem being modeled inside STANDING.
1300+
Entities modeled
48
National teams
104
Match moments
7
Entity categories
The Platform
What STANDING is
STANDING tracks public standing — the accumulated perception of an entity at a given point in time. Every public reaction to a real-world moment is a signal. Those signals move standing up, down, or leave it steady. Over time they form a standing profile that reflects genuine public sentiment, not follower counts or engagement metrics.
The core question: when something happens, does the public support this entity, oppose the direction, or stay neutral? Aggregated across many people and many moments, that becomes meaningful perception data.
How public standing is expressed
Every reaction is one of three stances — aggregated into a standing score and stability label: Trending, Stable, Volatile, or Declining.
Support
Confidence rising
Oppose
Confidence falling
Neutral
Watching, not committing
Entity categories — current and planned
Model
The perception model
The same structural model applies across every domain STANDING will cover. FIFA World Cup 2026 validates it at scale — football provides the clearest, most naturally structured set of entities, relationships, and moments of any publicly visible domain.
FIFA World Cup 2026 — Active Ecosystem
Future domains — same structure
Reaction layer and standing output are identical across all domains. Only entity types change.
Beyond sports
Why this matters outside of football
The FIFA World Cup 2026 was chosen because it is bounded, globally visible, and rich with structured entities. But public standing is not a sports concept — it is a universal one. How the public perceives a company after a product launch, a politician after a debate, a creator after a controversy — these follow the same pattern.
Sports
DoneWhere we start. Teams, players, coaches — structured, global, and publicly legible.
Business
In ProgressCompanies, founders, brands. Public standing shaped by decisions, launches, and crises.
Entertainment
In ProgressArtists, creators, films. Public perception is the entire currency of this domain.
Politics
PlannedPoliticians and parties. Standing measured by moment-by-moment public reaction, not polls.
Society
In ProgressInstitutions, organizations, cultural events. Perception at the societal level.
Places
In ProgressCities, nations, regions. Standing shaped by events, leadership, and global narrative.
First ecosystem
Why FIFA World Cup 2026 specifically
A perception platform needs a real, bounded, high-attention ecosystem to model first. The 2026 World Cup — the first with 48 teams — provides the largest structured football dataset in tournament history, with a global simultaneous audience.
48 national teams
Each team is a first-class entity with its own standing profile — not just a bracket entry.
1,000+ individual entities
Every player and coach has individual standing. A team and its captain can diverge significantly.
104 match moments
Every match creates a perception moment with measurable before/after standing movement.
Finite, testable scope
A start date, an end date, 48 teams. A complete dataset to validate before expanding.
Global simultaneous attention
Reactions from different countries to the same match are directly comparable — rare elsewhere.
Natural entity graph
Sport → Competition → Edition → Team → Player → Match. The hierarchy already exists.
Build log
Recent progress
A public record of the product decisions, interface work, and infrastructure improvements being made as STANDING moves from a World Cup preparation page toward a broader public perception platform.
Football national teams added to Standing
STANDING expanded beyond individual football players by adding football national teams into the replay-backed Standing system, giving countries their own public Standing surfaces ahead of the World Cup.
Activation experience clarified
The product became clearer about what STANDING is asking visitors to do: react to source-backed Moments, express why, and understand how those signals help shape public Standing.
Expression chips became stance-aware
Moment reactions became more expressive. Back, Doubt, and Hold can now surface more relevant expression chips, preserve custom user language, and return users to the right place after authentication.
Public identity and detail pages tightened
STANDING's public surface received a visual identity pass and detail pages became simpler, with associations and expressions made easier to reach.
Public pages became much faster
A major performance pass reduced public-page waiting time by snapshotting stable public data, trimming above-the-fold detail loads, and paginating Moments instead of loading the full feed upfront.
World Cup Moments became activation-ready
The World Cup experience moved closer to a participation surface, with friendlier Moment structure, clearer Standing prompts, and new highlighted tournament routes and fixtures.
Football replay and public indexing expanded
The football replay work expanded into priority player passes while public URLs and indexing became cleaner through canonical slugs and a more focused sitemap.
Unreplayed Standing cleaned up
Public Standing became more honest by hiding unreplayed scores and removing fake-looking public metrics until replay-backed data is ready.
Demand-driven Standing replay activation
Standing replay became requestable instead of assumed. Entities can now exist in the product without public Standing until users or admins ask the system to build it from verified Moments.
Replayed Standing becomes visible in product
The validated football replay outputs were connected to product-facing entity pages without cutting over the whole platform to live scoring.
Football Methodology V1 frozen
Football scoring methodology reached a defensible V1 after validation across attackers, midfielders, defenders, goalkeepers, older-era legends, and modern players.
Football golden replay expanded and calibrated
The golden replay dataset moved beyond Messi and Ronaldo into broader football validation, source upgrades, record rules, and duplicate-handling methodology.
Standing Engine V1 implemented contract-first
The old scoring approach was replaced with a replay-based Standing Engine built from the Constitution, Principles, HLD, Domain Model, and Scoring Contract before implementation details.
Legacy scoring removed from product direction
The app moved away from the earlier scoring prototype and prepared for replay-based Standing rather than direct score mutation.
Ingestion pipeline hardened
The ingestion pipeline became testable, observable, and split into independently deployable services so source-backed Moments can flow into Standing safely.
Ingestion microservices created
Candidate moment ingestion was split into focused services to support source-backed Standing Moments rather than manual event entry alone.
Reaction and activation experience improved
The reaction experience became smoother, localized, and more reliable before the Standing Engine replacement work began.
Anonymous reactions — no login required
Expressing a stance on a moment no longer requires an account. Any visitor can now choose Support, Neutral, or Oppose anonymously, reducing the friction between a public moment and a public signal.
Personalised editorial activation
Each country now sees a curated first moment when they arrive — a hand-picked World Cup event relevant to their national team or local interest, with custom copy, expression chips, and a tailored reaction prompt designed to get that first stance.
First multilingual foundation
STANDING gained its first language-level localization layer for English, Spanish, and Portuguese without adding a heavy i18n framework.
Detail pages became proper product surfaces
After Explore became the main discovery path, entity and moment pages were redesigned so search results open into clearer standing profiles and source-backed moment views.
First V1 Explore/search flow
Explore became the main discovery surface for STANDING, replacing the earlier low-value Figures/entity dump direction with a simpler search-led experience.
Moment-first positioning across public pages
The public pages were reframed around STANDING as a moment-first public perception platform, not a football database.
Mobile and public-page UX cleanup
The public experience became more usable on small screens, with clearer navigation, tighter layouts, and more natural page hierarchy.
SEO foundation
Every public page on STANDING gained a proper SEO layer — canonical URLs, Open Graph, structured data, and a dynamic sitemap — so entity and moment pages can be discovered and correctly indexed.
Status
Current progress
State of the FIFA World Cup 2026 ecosystem inside STANDING as of June 2026.
Football sport model
Sport entity created with correct configuration and category context
FIFA World Cup competition
Competition entity created and linked to the football sport model
FIFA World Cup 2026 edition
Edition created with dates, host countries, and full configuration
Entity pages
Public-facing pages are live, with entity and moment detail surfaces still being refined
National team import
All 48 qualified national teams imported with metadata and profiles
Players & coaches
Squad members and coaching staff linked to their respective team entities
Match schedule as moments
All 104 official matches modeled as perception moments
Association graph
Cross-entity graph linking teams, players, coaches, matches, and reactions
Standing calculation engine
Aggregating back/doubt/hold reactions into entity standing scores over time
Public reaction layer
User interface for submitting stances tied to specific match moments
Stack
Technical architecture
Founder-built. Optimized for iteration speed and a typed relational data model that scales to the full World Cup dataset and the broader platform beyond it.
Frontend
React 19
TypeScript
Tailwind CSS v4Build & Deployment
Vite
VercelBackend & Database
Supabase
PostgreSQL
Drizzle ORMSupabase AuthData Model
TanStack Start and Vite deployed to Vercel. Supabase handles the full backend — auth, database, and storage. Drizzle ORM manages the typed schema and migrations. No dedicated infrastructure team. Operational overhead is close to zero.
AI assistance
AI in the build
STANDING is built by a small team using AI as a core part of the development workflow. This is not hidden — it is how the product moves quickly without a large engineering team.
Lovable
UI & frontend scaffolding
Used for component generation, UI scaffolding, and frontend structure. Accelerates the visual layer without requiring a dedicated frontend team.
ChatGPT
Product & architecture thinking
Used for product decisions, architecture planning, content structuring, and working through positioning questions.
Codex
Code generation
Used for code generation, implementation assistance, and working through technical problems quickly.
AI broadly
Research & planning
Used for research, roadmap thinking, entity data generation, and documentation — freeing time for decisions that require original judgment.
AI accelerates execution. The product decisions, entity model, stance system, and platform vision are the founder's own. AI is a tool in the build — not the author of it.
Scale
Expected scale at tournament completion
The largest dataset STANDING will have hosted when the World Cup ends.
48
National team entities with standing profiles
1,000+
Football entities — players, coaches, staff
104
Match moments with standing deltas
10k+
Projected public reactions as standing inputs
~5k
Entity relationship edges in the graph
3
Host countries — USA, Canada, Mexico
Scalability progress
- Database indexingIndexes on reactions, takes, entities, and entity_says — removed full table scans from common pathsDone
- Query optimizationBounded all public queries, deduplicated home loader, atomic reaction counters, score history limitsDone
- CDN cachingCache-Control headers on all public loaders; localized routes (/en, /es, /pt) cached separatelyDone
- Route code splittingAll routes lazy-loaded; activation components deferred until neededDone
- Cache warmup workflowGitHub Actions job warms key CDN routes after every deploy so the first real visitor doesn't hit a cold functionDone
- Home loader cold-startloadHomeData() is the last major bottleneck — targeting KV caching or PgBouncer to cut cold FCP from 3.4sIn Progress
- Search indexespg_trgm and GIN indexes for faster entity search and World Cup JSONB queriesPlanned
- Realtime updatesSupabase Realtime for live standing movement during matchesPlanned
Transparency
Why we are building in public
This page is a progress document. STANDING is documenting its preparation for the World Cup openly — what is built, what is in progress, and what is planned. There is no pitch here. The goal is accountability and legibility.
Infrastructure partners
STANDING is a relational, entity-heavy platform with real scale requirements during a global event. We run on Vercel and Supabase and are actively growing toward World Cup scale. The workload is real — infrastructure support conversations are welcome.
Sponsors & partners
STANDING will have a live public presence during FIFA World Cup 2026 — standing pages for all 48 teams, 1,000+ players, and 104 match moments. Partnership opportunities are open for organizations aligned with public perception and sentiment at scale.
Infrastructure
Current infrastructure
| Component | Provider | Notes |
|---|---|---|
| Frontend | Vercel | TanStack Start + Vite, deployed on Vercel |
| Database | Supabase (PostgreSQL) | Entity storage, relationship graph, standing data |
| ORM | Drizzle ORM | Typed schema, migrations, and query layer |
| Auth | Supabase Auth | User accounts for reaction submissions |
| Storage | Supabase Storage | Team crests, player images, media assets |
| Domain | STANDING | Public-facing, live |
| Status | — | Actively preparing for FIFA World Cup 2026 |
Founder Note
STANDING is still early. But the FIFA World Cup 2026 offers something genuinely useful for a platform like this: a globally shared event with clearly defined entities, a natural timeline, and a massive simultaneous audience — all conditions that make testing a perception model meaningful rather than synthetic.
The goal is not to launch a finished product during the World Cup. The goal is to run a real perception ecosystem through a real global event and learn from it in public. Every team page, every match moment, every standing movement is a data point.
After the World Cup, the model expands. Sports was the entry point because the entities are well-defined and the moments are public. But STANDING is designed for any domain where public perception matters — and that is most of them.