Why I built Yico
Amateur Go tournament information is spread across public account articles, QQ groups, spreadsheets, screenshots, and photos. The information exists, but it is not connected.
Yico turns those fragments into a growing tournament archive. Players can query rules, pairings, standings, player records, and promotion information while an event is in progress.
What it does
- Archives tournament rules, dates, groups, formats, scoring, and promotion standards.
- Imports pairings from spreadsheets, Markdown tables, or photographed sheets.
- Builds historical records for players, opponents, rounds, results, and standings.
- Answers questions such as “Who is the next opponent?” and “How many points are needed for promotion?” from stored tournament data.
How Agents are used
Agents turn unstructured tournament material into validated data and help users query existing facts. The current seven scenarios are tournament chat, pairing extraction, promotion-list extraction, image OCR, rulebook extraction, tournament import, and conversation summarization.
The detailed prompts, schemas, and safety boundaries are documented in Seven Agents inside a Go mini program.
Data flow
Public accounts / QQ groups / spreadsheets / photos
↓
capture, upload, OCR
↓
Agent extraction
↓
validation and review
↓
tournament and player records
↓
mini program queries
Agents organize information; validation and human review remain responsible for publishing official records.
System structure
Yico has three main parts:
- WeChat mini program: uni-app, Vue 3, TypeScript, Pinia, and wot-design-uni for tournaments, pairings, rankings, results, promotions, player profiles, and the tournament assistant.
- Go service: Go, Gin, and GORM for users, tournaments, groups, rounds, games, players, standings, and Agent sessions.
- Operations console: tournament setup, rulebooks, pairing imports, promotion lists, Agent prompts, model configuration, and usage monitoring.
Pairing imports follow a controlled path: upload or fetch material, convert/OCR it, extract structured data with an Agent, validate fields, preview, and confirm before storage. The model helps interpret messy material but does not directly publish official records.
Scope
Yico focuses on organizing and querying amateur Go tournament information. It does not replace referees, organizers, or official competition systems. When source material is incomplete, the product should say so instead of presenting an invented answer as fact.
Launch result
Yico was registered, filed, developed, reviewed, and published under an individual account. It reached release after three rounds of review changes. The launch process is documented in From registration to launch.
Try it
Scan the mini program code with WeChat to try Yico:
