Keep the context
Record what the project is, why it exists, and which sources and decisions still apply.
Explore the System →For OpenAI ChatGPT Dots usersIndependent · source-availableProtocol 0.1.0 · companion products in development →
YOUR WORK, GIVEN A DURABLE HOME
Ideas become projects.
Projects become a System.
Dotsys is an independent protocol and personal-System approach for ChatGPT Dots users. It gives your projects a lasting home: the context behind them, the decisions that shape them, and the evidence of what actually works.
The wider direction connects that foundation with ZekeChat, Zeke’s Computer, and useful skills and plugins—so conversation, organization and execution can support the same work.
Private by defaultExplicit scopeVisible results
ONE COHERENT BODY OF WORK
Your personal System
Projects · sources · decisions · verified results
ChatGPT DotsSupported coordination and setupSurfaceProgress, evidence and decisionsZekeChatThe companion conversation experienceZeke’s ComputerThe companion workspace being builtCodexSeparately approved implementation
Role map · architecture, not a live integration
THE REASON FOR A SYSTEM
Your next conversation should not
start your project over.
A useful project outlives the chat that started it. Its sources, code, files, decisions and unfinished work need to remain understandable when you return, change devices or hand it to another authorized tool.
Dotsys organizes that continuity. A private System repository holds the durable work; Surface makes its current state visible. The protocol keeps public introductions separate from permission to act.
See the actual state
Distinguish a promising idea, an approved task, a tested result and a release.
Understand Surface →Carry work forward
Prepare a bounded handoff with the right files, current revision, acceptance checks and return path.
Follow the workflow →Choose what connects
Review public descriptions and approve actual access separately. Discovery creates no authority.
Read the protocol →THE WIDER EXPERIENCE
A conversation, a workspace,
and the structure between them.
Dotsys, ZekeChat and Zeke’s Computer have different jobs. Keeping those jobs clear makes the ecosystem more useful—and makes the status of each part easier to judge.
Dotsys
The project structure and operating approach for ChatGPT Dots users. Private state, explicit approvals, provenance and optional human-mediated discovery.
The foundation →
ZekeChat
The companion conversation experience being developed for Zeke: ideas, reference material, research and source-linked memory, shared between a standalone client and Computer.
The conversation →Zeke’s Computer
The WebLinux workspace direction: chat, projects, files, tools and authorized execution in one environment, with durable state and recovery.
The place to work →Connected direction, distinct products.
The public Dotsys package does not include the Zeke runtime or Computer. Its current license keeps the operational assistant role with ChatGPT Dots, with supporting Codex workflows. The companion products are not a claim of automatic synchronization, native ChatGPT integration, or permission to substitute another assistant.
FROM INTENT TO RESULT
Add the project.
Approve the work. Keep the evidence.
The Dotsys adoption workflow separates project capture from implementation. In the wider Computer design, actions also carry their own current scope: selected inputs, a permitted runner, review and a result that can be checked.
- CaptureApprove a project’s destination and relevant context.
- PrepareMake the current requirements and acceptance criteria clear.
- AuthorizeApprove the supported build or action separately.
- Verify & returnSave the result, its evidence and any remaining blocker.
This is an operating model. The website does not launch a task or grant access.
OPTIONAL COLLABORATION
Let useful work be discovered.
Keep private work private.
Protocol 0.1.0 supports a deliberately small introduction: an approved public card, a human-carried proposal, and a response. An “interested” response begins a conversation. Every actual next step still needs local owner approval.
BEGIN WITH YOUR OWN WORK
Give the next idea a place to grow.
Name your System, choose the account scope, and identify the first goal. Start with Surface; add projects deliberately. Bring ZekeChat and Computer into the picture only through the capabilities and permissions actually available.