Help keep everyday life organised.
Household planning · Object and routine context
SYSTEM TRACEPreparing this route
Preserving identity and page context while the next view is assembled.
Preserving identity and page context while the next view is assembled.
Evopien / Thor generation
Evopien combines a working voice, vision and internet demo on Thor with a governed-memory development path. Reviewed synthetic records survive restart; a bounded bilingual voice-recovery diagnostic has passed. Public conversation and research are the active implementation task. Full voice, real-user and Alpha acceptance remain open.
Move your pointer. Try an expression. Tap the face.Try an expression, or tap the face for a wink.
The body is an interface. Identity, memories and permissions are governed separately by Evopien Core.
Concept visual — not a finished robot or a live AI demo. No camera or microphone access.
What exists now
Remember the source. Preserve the conditions. Recheck the rights.
The working local/cloud demo is preserved. A separate branch now stores, reviews, corrects and recalls synthetic memory across restart, with current-rights checks. The reported memory suite passed 903 required backend methods; a later, different 634-test run verified a narrow bilingual voice-recovery sequence. This is fictional-data engineering evidence, not unrestricted memory, real-user acceptance or a completed Alpha. Current implementation is refining public conversation and internet research; full voice and governance acceptance remain open.
The Evopien difference
A new generation does not inherit a life by default.
Evopien Core separates each artificial identity from models, devices, relationships, memories, permissions, skills, and bodies. The Thor-generation identity was created exactly once at MS-06 with disclosed engineering lineage; the Orin predecessor is not presented as the same active individual, and its conversations, operational memory, relationships, and identity state were not imported.
Keep people and permissions separate. Preserve lineage honestly. Require evidence before any continuity claim.
What Evopien is for
These are design objectives, not completed product claims. The goal is practical help that preserves human control.
Household planning · Object and routine context
Research support · Skill practice
Programming and design · Long-project context
Light object handling · Accessibility support
Development path
The roadmap is evidence-gated rather than a calendar promise.
MS-07 is the active implementation task: test public questions and retrieval in an isolated text-first path. Protected memory, camera and motion are not attached.
The narrow bilingual recovery diagnostic passed on Thor. Complete the remaining G8 voice corpus and G9 synthetic evidence matrix without treating one diagnostic as full acceptance.
Keep the reviewed PostgreSQL workflow, rights checks and demo recovery reference separate. Visual follow-ups, source freshness, completeness and latency tails remain tracked.
Head hardware follows separate control and safety evidence. Real-user data, powered motion and household deployment keep their own gates.
Latest progress
Real setup, working results, known limits, and the next problem to solve.
The 9–16 September engineering review: local/cloud demo recovery, durable synthetic memory, reviewed English/Spanish input and governed speech. The latest operator-reported backend run passed 903 required methods; broader cognition, voice and Alpha gates remain open.
Read record ↗
424 engineering commits bring full-duplex conversation, selected live and recent-history vision, and public research into one Thor demo. The baseline is frozen and merged into main, with local and cloud profiles. Governed memory and stronger permission boundaries are next.
Read record ↗
Explicit English and Spain-Spanish switching is frozen, continuous perception has been exercised, and Qwen has received a current camera image. The latest branch adds a 15-second visual-context window to ordinary turns, with physical qualification still ahead.
Read record ↗Join the community
The development journal remains the formal engineering record. Telegram is the place for shorter project updates, discussion, and staying close to what is being built next.