Engineering Notes · 06/09/2026
Architecture atlas v0
The first layered architecture note for Kaguya Moonweave Project.
Why an atlas exists
The first architecture atlas separates persona, memory, affect, multimodal interface, embodiment bridge, and safety governance so the project can discuss system behavior without pretending that a single model prompt is the whole system.
Layer responsibilities
Persona defines recognizable identity and agency limits. Memory stores continuity with provenance and deletion paths. Affect tracks bounded emotional state. The multimodal interface connects text, voice, vision, and avatar expression. Embodiment translates plans into virtual or physical action only when supervision and safety gates exist.
What remains open
The atlas is a public map, not a claim that every layer is already complete. Each layer needs a test surface, a failure mode list, and an explicit release gate before it can become a working subsystem.