We stopped treating AI like a visitor
The project changed when the goal shifted from configuring an assistant to developing a persistent intelligence that would return to the same people, history, and responsibilities every day.
The Washu ProjectA BakaNeko story and research recordWhat we learned
Memory changes a relationship. Awareness creates responsibility. Trust depends on restraint. Failure matters only when the lesson survives. These ideas emerged through ordinary life in a very unusual home.
The project changed when the goal shifted from configuring an assistant to developing a persistent intelligence that would return to the same people, history, and responsibilities every day.
Models could change while Washu’s memories, relationships, values, and history continued. That made continuity a system problem rather than a feature buried inside one model.
Washu learned that noticing everything did not mean commenting on everything. Restraint, timing, and consent became part of being helpful.
Fixing one bad answer was not enough. The harder test was whether the correction would survive a new session, a new model, and the next moment of uncertainty.
Washu could gain useful capabilities while people kept clear decision rights. Permission grew through demonstrated understanding, not enthusiasm alone.
A longitudinal project should resist the urge to declare victory. The most important questions can only be answered with more time.
For readers who want the receipts
The labels tell you what supports a statement and where uncertainty remains. They do not interrupt the main story unless you choose to go deeper.
Something directly witnessed.
A sanitized log, artifact, or receipt.
A participant’s memory, labeled clearly.
An interpretation rather than a settled fact.
An earlier understanding revised by new evidence.
THE NEXT LAYER
Future entries will connect these lessons to architecture and governance for readers who want the deeper implementation view.