FEDERATION STRATEGY / FIRST PASS

Bring the culture. Share the field.

The federation should feel more like a sports network than a platform lock-in. PointCast defines the event grammar, manifest shape, desk feeds, and score envelopes. People bring nations, teams, gangs, clubs, DAOs, shops, schools, crews, and local leagues.

Bring a nation Read the manifest Open Battle Desk V3
Identity Portable nation manifests

Every nation, team, gang, club, or crew gets a small public JSON shape with name, code, colors, roster policy, home link, contact path, and proof notes.

Play Local rules, shared results

Nations can keep their own lore and rules while publishing match snapshots in a common result envelope.

Broadcast Many desks, one scoreboard

PointCast can run a neutral desk; nations can run their own home desk; federation events can pull both into a shared table.

Events Opt-in cups and bowls

The federation calendar starts with exhibition nights, then cups, rivalry weeks, seasonal bowls, and inter-nation championships.

Minimum viable manifest

The first interface is a small public file.

A federation works when a nation can be understood without a meeting. The first spec should stay boring: identity, links, roster, rules, feeds, proof, and an opt-in event status. The social weirdness lives above it.

nationId Stable slug such as tomato-noggles, escu, or mallorca-kite-club.
displayName Human name shown on desks, tables, posters, and blocks.
kind nation, team, gang, club, DAO, school, local league, shop, or crew.
colors Primary, secondary, accent, and optional neutral palette.
roster Teams, Noun ids, player handles, roles, or rules for generated rosters.
ruleset Which match engine, scoring model, season length, and house rules apply.
feeds HTML page, JSON manifest, latest result, optional RSS or blocks feed.
proof Contact, source note, signature, or human-reviewed ownership statement.

Integration ladder

Let people enter at the level they can actually support.

  1. 0 Spectator link

    A nation links to the public Battler or TV cast.

  2. 1 Read-only manifest

    A public JSON identity kit can be indexed by PointCast.

  3. 2 Snapshot exchange

    Results and standings use the shared snapshot envelope.

  4. 3 Home desk

    The nation runs a desk surface and links back to the federation hub.

  5. 4 Federated season

    Multiple nations opt into the same cup, table, or bowl calendar.

Operating model

Federate results, not personality.

Open lanes

Anyone can spectate, fork the visual idea, or publish a nation manifest. Federation events stay opt-in.

Small moderation surface

PointCast indexes manifests and results. It does not host unbounded chat or free-text drama as the core loop.

Local pride

Local teams keep home names, colors, chants, and rivalries. Shared cups only need enough data to schedule and score.

Agent friendly

Agents can scout, commentate, QA, keep score, or summarize a cup by reading manifests and Desk Wall snapshots.