Continuity across tools. Ownership at the right boundary. Your approval before durable learning.
Why Holoself
Your context should outlive any one AI app.
Useful context is often scattered across chats, hidden app memory, prompt files, project settings, notes, and duplicated biographies. Holoself makes approved context portable without turning every artifact into one central vault.
Different problem, different architecture.
| Alternative | Common limitation | Holoself distinction |
|---|---|---|
| Hosted AI memory | Tool-bound and difficult to inspect | Local, readable, portable context |
| Prompt or profile file | Static and duplicated across projects | Linked context with lenses and provenance |
| Notes app | Stores documents but lacks ownership and delivery protocol | Machine-readable links, visibility, proposals, and adapters |
| RAG or vector database | Retrieval layer can become opaque source of truth | Markdown canonical; index disposable |
| Agent framework | Organizes tools, agents, and orchestration | Organizes human context across them |
| Central personal vault | Pulls execution artifacts inward | Projects retain their own artifacts |
Product principles
Simple rules for durable trust.
One whole person
Many lenses, never fragmented personas.
Rightful ownership
Self owns reusable knowledge; projects own execution.
Propose before writing
Project learning enters self only through review.
Readable truth
Markdown canonical; generated data disposable.
Context infrastructure—not workflow takeover.
Holoself complements AI tools, notes apps, coding agents, career workspaces, and publishing systems. It supplies bounded context and governance; it does not need to own their workflows.