docs: reconcile current acceptance and retire obsolete status
docs(product): align finals requirements, account design and live UI
docs: finalize M1-M3 requirements and design
docs: place the language-switcher line after a blank line on both main documents
Matches the form used by the DS corpus and the other wiki documents; the view index
line stays directly below it.
docs: translate the remaining generic engineering terms in the two main documents
Second pass over Requirements-SPEC and Technical-Design: authority, ownership,
taxonomy, timeline, signal, cluster, chunk, probe, onboarding, metadata, workflow,
applicability, insight, boundary and identity become Chinese in prose, including
their capitalised forms. retrieval, embedding, context, memory, tool call, sandbox,
MCP, schema, component proper names, workload names and identifiers stay English.
Missing Chinese-Latin spaces were restored; tables, headings, code blocks, links,
URLs, digits and backticked literals are unchanged.
docs: add bilingual architecture views site and English wiki editions
- site/ holds the architecture views: an index separating Requirements from
Technical Design, one bilingual shell per view, the four archify artifacts
(zh default, en optional) and their specs
- Requirements-SPEC and Technical-Design link their own view from the top
- every wiki document except the problem statement has an English edition,
linked through a language switcher line; prd-flow/ is superseded by site/
docs: freeze requirements and open technical design
docs: make Home the file index and restore the development order in the SPEC
Home keeps the intro, the current stage and an index of the tracked files. The
development order and the Probe rule move to M8, their owning module, so the
index can replace the process section without losing it.
docs: state the remaining constraints positively
docs: drop the version number and state scope as ownership
Scope is expressed by which module owns a capability and where a concern lives,
replacing the excluded-capability lists; version labelling is removed from the
title and prose.
docs: restructure SPEC into layered modules with the decomposition rationale
Restore the requirement decomposition as explicit design premises (data-flow module
boundaries, metrics bound to modules, internal benchmark as a product module,
taxonomy recorded as two dimensions), and give every module a stable heading with
responsibility, internal stages and acceptance so each maps to one diagram node.
docs: rewrite SPEC in the documentation register used by the DSH repos
Reader contract opens the document; scoring tables, deliverables and deadlines are
owned by the 赛题 page and only referenced; requirements are stated as present-tense
product behaviour; English identifiers and thresholds take backticks with a
first-use Chinese gloss; each fact has one home; the 命题标准 mapping table is the
review checklist.
docs: rewrite SPEC with the confirmed scope and the scoring criteria mapping
- keep the section skeleton and the risk-taxonomy analysis, drop the claim that
AI Infra and supply chain are out of scope: all four classes are in scope, the
constraint is manpower allocation, not class difficulty
- bind performance metrics to their functional module, as the scoring tables do
- add the 命题标准 mapping table covering all 16 scoring items of the preliminary
and final rounds, plus the score structure consequence for prioritisation
- add deliverables, registration deadline, and the defence-readiness constraint
- carry over every open question from the previous revision
Updated Requirements SPEC (markdown)
docs: deepen PRD requirement analysis
docs: rewrite PRD as requirement analysis
Updated Requirements SPEC (markdown)
Updated Requirements SPEC (markdown)
Updated Requirements SPEC (markdown)
Updated Requirements SPEC v0.1 (markdown)