docs: consolidate preliminary evaluation and protect local deliverables
docs: reconcile current acceptance and retire obsolete status
docs: synchronize intelligence, product and operating contracts
docs(product): align finals requirements, account design and live UI
docs: checkpoint TD2A and TD3 implementation review
docs: finalize M1-M3 requirements and design
docs: sync M1-M3 lifecycle closeout
docs: number technical design documents
docs: align bilingual technical design
docs: wire split technical design into wiki navigation
docs: define M4-M6 investigation runtime
docs: keep retrieval, embedding, context, memory and sandbox in English on Home
Per the confirmed terminology rule, only generic engineering words become Chinese;
the domain-precise English terms and the plane names stay as they are, matching the
figures and the code.
docs: normalize generic engineering terms on Home
The default Chinese edition now carries the terms in Chinese (data plane, working
set, promotion, projection, outbox, contract, boundary, ownership, policy,
taxonomy, timeline); identifiers, module codes, thresholds and links are unchanged.
docs(site): drop the misleading durable-state boundary and align language-switcher lines
The durable-state security group wrapped pg and blob, so its bounding box also
enclosed unrelated components; authority is now carried by the PostgreSQL tag and
the card. Switcher lines move to the third line, matching the DS corpus and the
repository's existing bilingual pair.
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: sync data-plane implementation status
docs: close data-plane design review
docs: add incident intelligence architecture
docs: add hot bug lifecycle and experience evolution
docs: rewrite technical design around runtime architecture
docs: restore Home document semantics
docs: tighten M1-M3 technical design contracts
docs: freeze requirements and open technical design
docs: broaden frontier security intelligence watch
docs: define model data and agent security landscape
docs: define normative knowledge and policy handling
docs: add CTI reuse and ownership baseline
docs: number the data source report
docs: restructure data source processing baseline