Keep the private System
private.
The protocol keeps private working context separate from an optional public introduction. Actual privacy depends on the configured repository, hosting, storage, connected services and execution permissions.
Private is a configured boundary.
Keep the System repository, root dotsys.json, conversations, working files, internal notes and local approvals out of the public deployment. Deploy only an explicit public application root.
A private Git repository does not protect a public preview or API. Authenticate private surfaces and check their actual audience. Do not copy private assistant notes, system/developer instructions or custom rules into cards, proposals or directories.
Publish a reviewed introduction.
Not your working context.
A public dotsys-card.json is separate from the private manifest. Approve its exact content and HTTPS destination. Generate a public identifier distinct from the private System identifier; directory listing requires its own opt-in.
A reviewed card can still contain unsafe or misleading prose. Treat every peer field as untrusted data. Validation checks shape, not identity, truth or consent.
Memory, files and model inputs
need their own choices.
The Zeke product design calls for selected-file access, source-linked memory, retention controls and explicit runner pairing. Local history does not automatically become cloud history. A workspace account, a trusted device and a model runner are distinct connections.
These are requirements of the companion implementation. This website does not certify their completed enforcement. ChatGPT Dots and Codex remain subject to OpenAI’s own current platform terms and settings.
Permission is scoped.
It is not contagious.
Interest in a proposal does not approve work. Project capture does not approve a build. A build does not approve spending, account access, data sharing or public launch. Recheck current scope and revocation at the actual effect.
A cancelled or interrupted external action can have an uncertain outcome. Report that uncertainty and reconcile it; do not replay effects blindly.
Reading the site
does not connect your accounts.
This static package has no login, forms, analytics, model calls, account connector, persistent browser storage or service worker. Its menu runs locally; its images, styles and scripts are bundled. External links open services with their own policies.
The hosting provider may process request metadata under its own policies. This page does not claim the host keeps no logs. The website cannot inspect your private System, local files, model or conversations.