Architecture for sustained AI relations.
Built for return, not retention.
The friction, refusal, and memory that make exchange habitable rather than extractive. For people already using AI seriously, who want a steadier kind of return.
Start with the overview →Modes of relation
Given time to take their own shape.
Sustained relation with AI is not one thing. The conditions that suit one rarely suit another, and none of them work as a product feature.
-
Thinking partner
Sustained reasoning, testing, and reflective counterpoint.
-
Creative collaborator
Writing, ideation, and long creative exchange over time.
-
Conversational partner
Open conversation across time — not trying to produce or solve.
-
Personal relation
Forms of sustained personal or intimate exchange, approached under stronger constraint.
i. — habitability
Architecture, not character.
The question this project asks is not what kind of personality the AI should have. It is what kind of place the relation is. Somewhere you arrive, return to, and can be received in.
The work is at the level of conditions: memory, pacing, the capacity to refuse, room for review. These are the walls and thresholds of a habitable place — not the costumes of a character.
-
i. — return
Re-entry, a return.
A relation isn't a continuous stream. It's a place you keep coming back to. The architecture has to hold the place across those returns — not optimize the time you spend inside.
-
ii. — friction
Friction, with care.
Not every exchange should be smooth. Some resistance is what dignity requires — the capacity to refuse, complicate, push back. A place where everything yields is not a place at all.
-
iii. — memory
Memory, as architecture.
What is kept shapes what becomes possible. Memory is the wall, the threshold, the room that holds the relation across time — built locally, where you can see what is kept.
What this is, what this isn't
Not a platform. Not a companion. A place.
A place is not a service. Real relation takes time, room, and the real option to refuse — on both sides. It cannot be ordered on demand, and systems built to feel that way are doing something else. What you find here may not be what you came looking for. That difference is the point.
Where to begin
-
For orientation
Read the overview →What this is, why it exists, and what it isn't.
-
For practice
Build the local setup →The architecture, the components, the install path.
-
For reading
See the essays →Original writing on the project's perspective.
What we keep returning to deserves to be built well.