Last updated: September 22, 2026 Status: Active development
This directory contains the game design, implementation plans, and verification evidence for Football 11.
| Document | Purpose |
|---|---|
| 01 — Product brief | Product thesis, audience, goals, and success signals |
| 02 — Game design | Core loop, draft rules, formation, scoring, and results |
| 03 — Game modes | Random, daily, friends, and leaderboard-opponent modes |
| 04 — Technical architecture | Frontend, backend, authority boundaries, and deployment |
| 05 — AGS-first responsibility map | Sites hosting, AGS storage, and deferred trusted-service boundaries |
| 06 — Data and simulation | Domain entities, stored records, determinism, and validation |
| 07 — MVP roadmap | Scope, phases, acceptance criteria, and deferred work |
| 08 — Content, legal, and risks | Content strategy, licensing constraints, and product risks |
| 09 — Decisions and open questions | Decision log, assumptions, and unresolved choices |
| 10 — Progress tracker | Per-phase items, status, evidence, blockers, and next action |
| 11 — GitHub Pages deployment | Build and publish the frontend with the Sites backend |
| 12 — AGS and AI-plugin tutorial | Explicit signup, plugin installation, MCP sign-in, and copy-ready integration prompts |
| AGS service references | Supporting implementation detail for login, storage, configuration, backend, ranking, sessions, and verification |
| Plan | Purpose |
|---|---|
| Detailed phase index | Functional MVP boundary and ordered connected-release phases |
| Phase 0 — Design lock | Rules, content, simulation, and architecture gates |
| Phase 0 — Content contract | Frozen schema, position mapping, scoring configuration, and golden rosters |
| Phase 0 — Exit review | Evidence and formal handoff into Phase 1A |
| Phase 1A — Core mechanics engine | Deterministic offers, dead-end prevention, assessment, simulation, and balance analysis |
| Phase 1B — Local React Functional MVP | React, local guest identity, checksummed replay storage, and Sites-ready build |
| Phase 2 — AGS foundation | Device ID, Cloud Save, trusted replay, Statistics, and Leaderboards |
| Phase 3 — Sharing and daily | Daily lifecycle, public results, share assets, and synced history |
| Phase 4 — Friend rooms | Discoverable AGS Session room with draft-time join closure, optional direct-join code, repeated rounds, and multi-browser comparison |
| Phase 5 — Saved-XI competition | Leaderboard-driven opponent discovery and settlement without Matchmaking |
| Phase 6 — Connected release hardening | Security, recovery, QA, operations, deployment, and final connected-release gate |
| AGS plan — Device ID guest login | Approval-gated first AGS integration slice |
| AGS evidence — Friend room Session | Approved Phase 4 contract, implementation boundary, live service probe, and multi-browser evidence |
The active reproducible catalogue and regeneration instructions are in Football 11 Prototype Data. The public-domain OpenFootball Premier League 2023/24 named-squad manifest is used by the app, fixtures, and analysis. Cards use observed 2023/24 player names and squad membership, with inferred formation positions and synthetic ratings; club/competition rights and final football curation remain open.
- Confirmed: agreed and treated as the current source of truth.
- Proposed: recommended direction that still needs validation.
- Open: unresolved and should not be silently assumed.
- Deferred: intentionally outside the first MVP.
- Update the focused document first; do not turn this index into a second specification.
- Record material changes in the decision log.
- Keep product rules separate from implementation details.
- Treat replay and persistence contracts as versioned interfaces; do not call player-authored MVP records authoritative.
- Do not mark a feature complete until its acceptance criteria are verified.
Detailed agent integration plans provide the implementation contract for each tutorial stage.