Skip to content

Design and Implementation Records ​

These documents preserve design intent and implementation context. They are grouped by maintenance purpose, not by delivery date. Most records are written in the language used by the original implementation work.

The current code and tests are authoritative. Read Documentation Maintenance before treating a proposal or dated record as a current contract.

Architecture and long-lived contracts ​

Implemented design records ​

N.E.K.O 小剧场与剧本工坊 ​

  • 小剧场体验目标与设计约束:当前产品目标、职责与事实权限、运行交付与工坊发布边界、验证方法及维护责任。
  • 小剧场架构:当前唯一的实现合同——模块与权限、Story Package/Session/Ledger/记忆归档数据合同、回合流水线、复核与确定性检查、生命周期事务、胶囊展示合同与当前固定模块配置。
  • 小剧场设计决策记录:关键取舍、被否决方案及已知风险与未验证范围。

剧本工坊 SDK 的调用、宿主与发布合同见仓库 services/theater_workshop/README.md。

Product-flow and interaction records ​

Security, persistence, and incident analysis ​

Approved proposals (not yet implemented) ​

  • Neko visiting infrastructure (v3, all decisions approved)
  • Neko visiting: Servers contract — Chinese-only. Current contract for the closed-source Servers endpoints; generated from §4.7 of the design record and pinned to it by a unit test.
  • Neko visiting: field tests T1–T15 — Chinese-only. Result table and chrome://webrtc-internals acceptance fields for the design record's field-test list.
  • Plugin call chains and capability checks — Chinese-only, with an English summary. Host-maintained call chains between plugins, chain-wide capability checks against user consent, and an audit trail; P0–P4 plan, P0 and P1 (observe only) implemented first.
  • NekoPower rewrite — Chinese-only. Replaces the agent module: a resident task brain that routes what the main dialogue dispatches (plugins first, task agent sessions for multi-step work), a built-in Python runtime with optional dsh, one capability gateway, and a per-project work memory.

New records should state whether they are a current contract, implemented record, proposal, historical snapshot, or deprecated document near the beginning.