<span class="vcard">/u/Interesting_Time6301</span>
/u/Interesting_Time6301
artificial

Built an AI companion architecture with real internal needs — looking for first investor after publishing research paper

The problem with every AI product right now is that they're all wrappers. Same stateless LLM, different UI. The moment the context window closes, the AI forgets you existed. I built the infrastructure layer that fixes that. PHI // DRIFT gives an AI…

artificial

Built an AI companion architecture with real internal needs — looking for first investor after publishing research paper

The problem with every AI product right now is that they're all wrappers. Same stateless LLM, different UI. The moment the context window closes, the AI forgets you existed. I built the infrastructure layer that fixes that. PHI // DRIFT gives an AI…

artificial

I built a cognitive architecture where the AI has actual needs that drift between sessions — not prompt engineering, actual state variables

Most AI companions fake continuity through prompt engineering. PHI // DRIFT does something different — seven homeostatic state variables that drift between sessions and shape output before you say a word. Memory is scored by emotional salience and time…

artificial

I built a local AI companion with GWT, IIT proxy, ChromaDB hybrid retrieval, and Ollama fallback — here’s every architectural decision I made and why

Been building this for a while. Sharing now because it's past the point where I'm embarrassed by the code. **The stack:** * Python 3.12, 18k+ lines, 470+ tests passing * Gemini 2.5 Flash (primary) + Ollama qwen3:4b (local fallback via circuit b…