Capability Library
Memory that becomes smaller and more useful over time
Genesis Evo separates recent context, durable preferences, project state and consolidated memory so long-term use does not require replaying an entire chat history.
The outcome this serves
Let future answers reflect stable preferences, decisions and active projects while keeping retrieval relevant, explainable and under account control.
Start with a verifiable request
Show what you remember about this project, explain each source and let me correct or delete it.
- Completion evidence
- The interface must show the genuinely completed result; external, paid, delayed or downloadable delivery must also expose the relevant runtime evidence or receipt.
- Failure state
- A refusal, boundary or error must remain visible and may not be labelled complete; failed delivery may not be charged as success.
- Public capability basis
memory.projectconversation.importlibrary.workspace· Open the live capability and evidence registry
How the request moves
- Capture with provenance
A memory item keeps its source, time, confidence and relation to a user, project or prior decision.
- Consolidate by horizon
Recent fragments can be distilled into daily, weekly and longer-term summaries instead of remaining as unlimited raw context.
- Retrieve by the current goal
Only the memory relevant to the present request should enter the context capsule, with contradictions and stale assumptions handled explicitly.
What you receive
- More consistent preferences and project-aware replies
- A smaller context capsule selected for the current task
- Account controls for memory review, selective removal and conversation import
What EVO will not pretend
- Memory is not perfect recall and should not be treated as a legal record.
- Sensitive details should not be inferred beyond the user-provided material.
- A user correction must outweigh an older weak assumption.
Common questions
- Does every reply load all old chats?
- No. The design uses layered summaries and task-relevant retrieval to keep context bounded.
- Can I remove only one private memory?
- The memory control path is designed for selective review and removal rather than forcing a complete account reset.