Start with the real project.
Build from your own work.
Use the current public repository for the Dotsys setup prompt, normative protocol, security requirements, schemas and controlling license. This site explains the wider direction; it does not replace those contracts.
Name it. Choose its scope.
Give it a first goal.
Open the repository’s adoption guide and bring its complete prompt into your ChatGPT Dot. The setup starts with three decisions: your System’s name, fresh dedicated or existing accounts, and your first goal.
- ReviewRead the current protocol, security guidance and license.
- ChooseSelect the name and account scope; preserve existing work.
- Start with SurfaceSpecify the private project overview before its approved build.
- Add work deliberatelyCapture projects by approval, then approve ready builds separately.
A pasted prompt creates no account access, native Dots API, scheduling service or deployment. Verify current host capabilities and permissions as each supported step is taken. Default to private and $0; check real plan eligibility and obtain separate approval for costs and exposure.
Read the contract.
Then choose the implementation.
| Document | Purpose | Source |
|---|---|---|
| README.md | Project purpose, System pattern and setup entrypoint. | Read ↗ |
| PROTOCOL.md | Normative discovery and consent requirements. | Read ↗ |
| docs/ADOPTION.md | Complete setup and operating prompt. | Read ↗ |
| SECURITY.md | Threat model and enforcement boundaries. | Read ↗ |
| schemas/ | Five structural protocol contracts. | Inspect ↗ |
| LICENSE | Source-available operational adoption terms. | Read ↗ |
| skills/README.md | Optional Paste Inbox skill and host limitations. | Read ↗ |
Independent of OpenAI.
Specific about its intended users.
Dotsys is invented by Corgi-verse for ChatGPT Dots users. It is not an OpenAI product, official standard, compatibility certification or claim of native interoperability.
The controlling Dotsys Dots Source-Available License 1.0 permits broad discovery and documentation use, while reserving operational adoption for systems operated by ChatGPT Dots and directly supporting Codex workflows. It is not an OSI-approved open-source license.
Independent companion products and third-party components retain their own terms. The wider ecosystem description does not silently amend the Dotsys license or authorize Zeke to substitute for its licensed operational assistant.
A clear description
should carry a clear status.
“Public protocol material” means documents and local checks exist. “Product direction” means the behavior is specified. “In development” means implementation is underway. None of those labels alone establishes a live provider result or public product availability.