I prefer short answers unless I ask for a breakdown.
Memory, dreaming and skills
You do not have to tell Sophia to remember every useful fact. When enabled, idle dreaming reviews delivered conversations and proposes memories or procedural lessons. It preserves source references and audience restrictions. It is background model work and appears in usage accounting.
Correct what it remembers
Section titled “Correct what it remembers”# sophiaSimulated conversation
I’ll keep answers short by default.
What do you remember about how I like explanations?
Short by default, with more detail when you ask.
Update that: include an example when explaining code.
Sophia can search, explicitly save, revise and forget memories. Portable presentation preferences follow your account. Ordinary private facts retain their original audience. Forgetting uses tombstones so an idle job cannot immediately reconstruct the deleted memory from the same source.
Operators use /memories to review quarantined legacy content and explicitly adopt eligible records. Legacy memories do not automatically become public after migration.
A skill saves a method
Section titled “A skill saves a method”A skill describes how to do a repeatable task. It has a version, scope and source history. Sophia can find, load, save, assess and delete skills. Operator review is available through /skills.
# sophiaSimulated conversation
This event comparison worked well. Save the method for next month.
I’ll save a method that checks dates, deduplicates announcements, compares attendance, and cites the final decisions.
Use that event comparison method for August.
Dream-derived skills require assessment tied to the exact method and a completed owned task before promotion. Imported or uncertain methods remain quarantined or private drafts. A skill is procedural guidance, not permission to perform its actions.
The older workflow tools remain compatible entrypoints into the skill system. They do not run a separate workflow engine. See skills architecture.