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
- Avatar performance module maintenance
- Avatar tool interaction design and maintenance
- Avatar tool prompt guidelines
- Cat Mind state-machine rules
- Cat idle states
- Deep topic hooks
- LLM prompt budget
- Proactive reason-code guide
- User activity tracker
- Voice design architecture
Implemented design records
- ASR client phase record
- Compact chat mode
- Memory event journal
- User-driven memory evidence
- PNGTuber lightweight avatar
- Translation subtitle panel
- TTS provider and voice-source unification
- Live2D idle motion selection and recovery
- PNGTubeRemix layered physics compatibility
Product-flow and interaction records
- Seven-day floating avatar guide
- Floating avatar panel functions
- Post-tutorial low-disruption chat branches
- CAT1 Playground Drop
- Focus / True-Name mode
- Memory-browser particle dissolve
- Yui guide-system cursor hiding
Security, persistence, and incident analysis
- Local mutation endpoint authentication
- Steam Auto-Cloud synchronization
- Telemetry distribution and Steam user ID race
New records should state whether they are a current contract, implemented record, proposal, historical snapshot, or deprecated document near the beginning.