One community.
Every part of the event.
Crit Wild is an MCP-first event platform for people finding an event, players taking part, and organizers running the day. Shared event infrastructure is separate from versioned game rules, so future systems can be added without rebuilding registration and event management.
Three complete journeys
| Who | The job to be done |
|---|---|
| Event browser | Search published events by name, city or venue; inspect dates, capacity, rules and entry instructions. |
| Player | Register or join a waitlist, submit a roster, check in, view a table assignment, report a result and follow standings. |
| Organizer | Create a draft, configure and publish the event, manage players, approve pairings and results, close rounds and publish final standings. |
Available in this version
- Discovery: event search, published event pages, dates in the venue’s timezone, capacity and registration status. Drafts are organizer-only; unlisted events are accessible by link.
- Event covers: an optional uploaded PNG, JPEG or WebP overrides the default. Otherwise one of the three supplied community images is randomly chosen at creation and saved, so it does not change on refresh. Uploaded covers are stored with the event and follow its visibility.
- Event creation: a single location field with virtual-event support, schedule, organizer contact and rules/community links, Standard or Extended component format, entry instructions, capacity, visibility, waitlist, roster deadline and visibility, check-in policy, round count and duration.
- Scoring: Challenger scoring preset or custom win/draw/loss and bye values. Points, strength of schedule and VP are calculated from approved results. Organizers may order up to three criteria: average opponent points, victory points, and games won.
- Players: one registration per signed-in user; manual walk-in entries; organizer promotion from waiting list; check-in, withdrawal and pre-start reinstatement.
- Factions: choose zero to three unique factions per event registration, add or remove them later, and show their logos beside the player. The 25 supplied Longshanks PNGs are bundled locally. Choices are independent from squad affiliation and roster legality.
- Rosters: MCT import with a preview of characters, tactics, Secure and Extraction crises; editable text sections and counts for guidance; deadlines; organizer review and reasoned corrections. “Reviewed” is a human review status, never a claim of automatic legality.
- Rounds: Swiss-style pairings that prefer equal points, avoid repeats when a solution is found, assign eligible byes and optionally avoid same-club pairings in round one. Organizers inspect drafts, swap players, accept explicit rematch warnings and publish.
- Results: players report their own match; organizers confirm or correct scores, with a reason for confirmed-score corrections. The winner is stored independently from VP. Unresolved reports block closing a round.
- Player tools: edit registration details and factions; view scoring settings; open organizer-supplied rules, community and email links; share, follow/unfollow, and download a calendar entry. Followed events appear in My events without enrolling the player or sending notifications.
- Operations: announcements, an organizer-only timer, live refresh, standings, finalization, cancellation with reason, recent audit history and a JSON export.
- Practice: an isolated event with eight fictional entrants, including one associated with the signed-in organizer for testing the player view.
MCP rules and boundaries
The current core roster has 10 characters, 10 distinct tactics cards, 5 Secure and 5 Extraction crises. The preset uses 3/1/0 event points and a 14 VP bye. Standard/Extended component legality and Challenger event procedures are separate concerns. Timeline is a separate event structure and is not offered in this version.
The organizer remains responsible for card legality, crisis restrictions, concessions, time extensions and event-packet compliance. The timer starts from the configured duration; it does not roll dice or automatically administer the end-of-round grace period. The pairing engine is a bounded search with human review, not a certified implementation of every official pairing edge case.
Control model and infrastructure
Authentication uses Google sign-in. Every write is authorized on the server. Organizers own events; players can act only on their own registrations and matches. Event status, registration availability, visibility and round state are separate. An event cannot be completed with unresolved results.
Each event stores its game identifier and rules version. The MCP adapter defines the preset, roster shape and source references. Event aggregates are persisted in a database with revision checks, so concurrent registration or scoring changes cannot silently overwrite each other. Finished events are immutable in this version.
Current bounds are 128 total entries per event, including waitlist and withdrawn entries; 10 rounds; 50 events per organizer; the most recent 2,000 audit actions per event. Roster text is bounded. Data is stored on the server, not in browser storage. A future relational expansion should separate entrants, games, staff and payment records as scale grows.
Project phases
- Phase 1 — Website launch: complete and validate the event website. The current private review site is not the public-launch milestone.
- Phase 2 — Local agents, after launch: provide a supported event-management API and a Markdown instruction file for local Codex or Claude agents. Users can ask their agent to create and modify their own events, using the same permissions and validation as the website.
- Phase 3 — Hosted assistant, to consider later: add a prompting page backed by a server-side model agent. Users would manage events inside the site without installing a local instruction file.
Game System — planned
Make Game System a choice during event creation, starting with Marvel: Crisis Protocol and expanding to more games. Each system will have its own Markdown requirements file covering player registration, event-creation inputs and rules, match information, and standard tie-breakers. Shared event management will use the selected system’s fields and rules. Further requirements will be added as each game is defined.
The MCP requirements record zero to three affiliations per player and a roster listing what they play with. Planned match fields are Priority, 2nd Priority, Extract, Secure and Threat Level. The requested standard tie-breakers are SOS (Strength of schedule — average opponent TP), then VPS (Victory Points scored). The exact SOS calculation and match-field definitions remain to be clarified. Affiliation selection and rosters already exist; selecting another system and recording these match fields remain future work. Game System support has no assigned delivery phase yet.
Benchmark and unscheduled feature backlog
Longshanks documents organizer controls across registration, pairings and ranking. BCP describes event search, roster submission, check-in, pairings, scoring and ticketing. Some advanced controls are account-gated; a complete organizer walkthrough is still needed to verify exact parity. Longshanks help · BCP overview
| Backlog area | Potential scope |
|---|---|
| Organizer depth | Staff roles, judge calls and disputes, additional tie-breaker formulas, table locks, late-entry reconciliation, pairing methods beyond Swiss, event duplication and CSV/print exports. |
| Competitive formats | Top cuts and elimination brackets, complete Timeline rotation, doubles and teams, leagues and circuits, complete versioned card database and automatic legality checks. |
| Raffle draws | Planned organizer/admin options: Draw player at random, or Draw X players at random with a chosen count and distinct players within the draw. Show results only to admin is configurable and enabled by default. Eligibility and repeat-draw rules remain to be specified. |
| Player payments | Planned Paid / Unpaid status for each player’s event registration. A separate future Charge option will connect to credit-card payments or PayPal; the provider and payment workflow remain to be designed. Raffle and payment features are roadmap entries only and have no assigned delivery phase. |
| Commercial launch | Payment provider checkout, refunds and reconciliation; public account options; notifications; maps, distance and date filters; operational monitoring and accessibility audit. |
| Game System | Selectable game systems, each with its own requirements file, registration and event-creation fields, match fields, scoring and ranking rules. Start with MCP and reuse identities, discovery, enrollment and event operations for future systems. |
MCT interoperability
Import accepts comma-separated eight-digit codes, preserves leading zeros and attaches hyphen-separated Infinity Gem codes to their characters. A local catalog contains 679 known identifiers; unknown identifiers stop the import without replacing existing fields. Partial or duplicate lists produce review warnings. Previewing or applying an import does not submit it: the player still chooses Save roster. Newly released cards may require a catalog update.
Interchange behavior was checked against Jarvis’ Protocol; factual card identifiers, names and categories come from the Cerebro character catalog and its tactics, crisis and gem catalogs, retrieved 2 October 2026. No card rules or artwork are needed for decoding.
Future event design reference
The project documentation includes a source-linked Longshanks reference covering ranking families, special ordering rules, visibility and registration. Current scope remains individual Swiss events; global ratings, teams, community-only registration, additional formulas and private messaging remain separate future work. Longshanks event ranking reference
Acceptance criteria
- Complete draft → publish → register → roster → check-in → pair → report → approve → close → finish.
- Exercise a full event, waitlist promotion, odd attendance, withdrawals, a corrected score and a concurrency conflict.
- Reject unauthorized edits, duplicate registration, late roster editing, unresolved round closure and post-finalization changes.
- Keep another player’s private roster hidden, keep draft pairings hidden until publication, and calculate standings only from approved results.
- Rehearse with distinct organizer and player accounts before opening registration to a real community.
Separate-account hosted rehearsal and a full competitor account-level audit are release gates for public launch, not claims already fulfilled by this first version.