Tasuki Keifu V0.1 PRD
The source document carries the date 2026-09-06. This is the initial product definition for that version, not a description of every feature the site has today.
1. Positioning
襷の系譜 is a multilingual reference site for Hakone Ekiden fans. It starts with an athlete and organizes basic identity, affiliations, background, and Hakone-related information so a fan can understand where that person fits into Japanese university distance running.
V0.1 did not aim to be a complete results database or a complex relationship graph. Its central hypothesis was whether fans would browse Hakone-related people through structured athlete profiles.
2. Audience
The first audiences were Japanese and Chinese-speaking Hakone Ekiden fans. The site was not designed as an introduction for general sports readers or as a news outlet. It aimed to feel like a careful athlete directory with an understanding of the fan community. English could have a basic framework, but was not the first release's main language priority.
3. Release Scope
The initial dataset covered current-year student rosters at Aoyama Gakuin University, Kokugakuin University, and Chuo University, prioritizing athletes connected to long-distance running and ekiden teams.
The one essential interaction was to search for or open an athlete and inspect the profile. University pages, high-school pages, race pages, relationship graphs, and a complete results database were not core V0.1 features.
4. Core Features
4.1 Athlete List
Visitors could browse included athletes. The list should show name, university, academic year, originating high school, and brief labels such as key team member, Hakone participant, or information pending. Its primary job was to lead to a profile.
4.2 Athlete Search
Search needed to handle Japanese written names, common kanji variants, and Romanized names where available. A Chinese-name search could wait. The first version did not need a complex search engine.
4.3 Athlete Profile
The profile was the core page. It should include the athlete's name, reading, Romanization, university, year, high school, birthplace when reliable, height and weight when reliable, selected PBs if included, Hakone records when available, links to athletes from the same university or high school, sources, last-update date, and a data state of confirmed, pending confirmation, or missing.
The aim was not maximum field count. Information needed to be credible, clearly structured, and extensible.
4.4 Lightweight Relationship Links
The first version retained simple navigation to athletes at the same university, from the same high school, or in the same academic year. A list or small module was enough; a graph visualization was unnecessary.
4.5 Languages
Japanese was the primary and most complete experience. Chinese interface text and explanations should be usable; English could retain a basic framework. Data content used Japanese as its reference language. Full Chinese translation of Japanese names and schools was not required because the original names were themselves important to fans; Chinese helped primarily with explanation and navigation.
5. Results Data
V0.1 took a conservative approach: include results that were easy to verify, important to fans, and useful on a profile.
- Hakone appearances: Year, stage, stage time, and stage ranking where available.
- Basic PBs: Such as 5,000 m, 10,000 m, and half marathon, only with clear sources.
- Other major university ekiden results: No systematic coverage in V0.1; a few facts could appear in a biography or note.
This kept the first version from expanding into a complete results database while giving profiles enough substance to be useful.
6. Explicit Exclusions
V0.1 did not include every university, the full history of Hakone results, complete high-school or university sections, a corporate-team destination system, a complex relationship graph, community submissions, automated collection, user accounts, comments, news, or live race updates. Those could be considered in later versions.
7. Success Criteria
A visitor should be able to find athletes from the three initial universities, open a profile and understand the person's basic history quickly, and move to someone from the same university or high school. Pages should look like a trustworthy reference collection, with clear sources and missing-data states. The product structure should allow additional universities without a redesign.
These were criteria for V0.1, not reported performance measurements.
8. Interface Direction
The intended visual character was a careful reference database with the warmth of a fan-made athlete directory: quiet, clear, restrained, readable in Japanese, with legible tables and profiles, strong information hierarchy, visible relationship links, and a style maintainable over time. It should not resemble a sports news site or an enterprise admin panel.
The proposed first viewport had the 襷の系譜 name, a subtitle, search, links to the three universities, and recently updated athletes. A profile would group basic information, affiliation and background, main records, Hakone results, related athletes, and data sources. The desired impression was that visitors could find useful facts and that the site understood Hakone Ekiden.