What is doll?
doll is a continuity system for a personal AI environment. It is intended to keep the user's state usable when a model, provider, interface, network connection, distribution source, or primary machine becomes unavailable.
It is not a foundation model, a cloud-required assistant, or an unrestricted autonomous agent.
doll separates durable user-owned state from replaceable reasoning engines.
Models are replaceable reasoning engines. The user's state is the durable core.
What the completed doll is intended to do
The intended system is a personal AI environment that can continue across model changes, provider changes, machine failures, and periods without cloud access.
It is intended to support:
- conversation, writing, summarization, translation, planning, and code assistance;
- document, PDF, CSV, image, audio, video, and source-assisted research workflows;
- confirmed memory, preferences, policies, permissions, projects, decisions, and artifacts;
- switching between local models and optional cloud models without making either the source of truth;
- reduced-capability offline operation when better models or networks are unavailable;
- backup, migration, restoration, rollback, and recovery on another machine;
- permission-controlled tool use with local audit records and fresh confirmation for high-risk actions;
- Lite and Heavy execution profiles that share the same state and safety rules.
This is the intended end state, not the current implementation. Features may change as the specifications, safety requirements, and real-machine validation evolve.
Why build doll?
AI is unlikely to disappear. The more likely problem is that models, prices, limits, accounts, policies, regional access, interfaces, and retained context continue to change outside the user's control.
doll is not a bet on a future without AI. It is preparation for a future in which AI is useful or necessary, while the conditions required to keep using it are not owned by the user.
Read the longer note: AI will remain. Your access conditions may not.
Development
Current status
Pre-alpha. Local state, portability, verified backup, restore, and post-restore validation have been implemented. The model-independent continuity acceptance gate is in development. No model runtime is connected yet.
Roadmap
- Specification and principles — Complete
- Local state foundation — Complete
- Continuity, transfer, backup, and restore — In progress
- Safety boundary — Planned
- Local AI — Planned
- Cloud and multiple models — Planned
- Tools and external services — Planned
- Daily use — Planned
- Distribution and long-term operation — Planned
Read the detailed roadmap on GitHub
Recent development
Recent merged pull requests are available on GitHub.
Support doll
doll is free and open source. Support is voluntary. It does not purchase a product, service, ownership interest, development priority, or special access.
Send only the listed asset on the listed network. Always verify the full address and network before sending. Consider sending a small test transfer first.
Crypto transfers cannot be reversed or refunded. This is not a tax-deductible charitable donation.
BTC — Bitcoin
bc1q8pk7wra4fzt49cnz59d859xkn8ucc95fwkr7z0
EVM networks
Accepted asset and network pairs:
- ETH — Ethereum Mainnet
- USDT — Ethereum Mainnet (ERC-20)
- USDC — Ethereum Mainnet (ERC-20)
- BNB — BNB Smart Chain
- AVAX — Avalanche C-Chain
The networks are separate even though the address is the same. Use only the asset and network pairs listed above.
0x8e13ce8b1a272d60d5e950ef2a5fe59a4f889764
SOL — Solana
5Ln8MBCjGov8USnpNfF71tGP3vMZYQsfEz5HH47UGybT
XRP — XRP Ledger
rLovVdAUfSddXJYJ8JhmLnZNu7hwYFxKaX
Destination tag: Not required
DOGE — Dogecoin
DH7jdTwQ9vQWXzgBNmUF86NoCM6GtnsHyS
About the builder
I am not a professional software developer. I did not begin this project with the technical skills normally expected to design and implement a system of this kind.
GPT is used for architecture, specification, task decomposition, research, and review. Codex is used for implementation, tests, and pull-request preparation.
I decide what doll should be, set priorities, perform real-machine validation, review the results, and decide what is merged.
This project should not be trusted because of my credentials. It should be judged by its public specifications, tests, development history, failure behavior, and recovery procedures.
Previous public work
If you want to judge my actual level, look at the things I have already published.
- Historical Exchange Index — a historical registry of cryptocurrency exchanges.
- Stable or Gone — a lifecycle registry for stablecoins and issuers.
- ViewLoom — live-stream data collection and visualization.
Contact
General contact: Contact form
Technical issues and bug reports: GitHub Issues
Security reports: SECURITY.md