Projects
Give each project a bounded home, a current README, requirements, references and meaningful acceptance checks.
THE DOTSYS SYSTEM
Your work has a home.
And a history.
A personal System is the durable body of work around your ChatGPT Dot: projects, research, files, decisions, configuration and results. The current adoption pattern starts with one private monorepo and Surface.
THE FOUNDATION
One source of truth.
Many useful ways into it.
The repository is authoritative for the System’s versioned project source and operating documents. Interfaces can make that work easier to use, but they should not create competing copies of its decisions.
Evidence
Keep results tied to the source and environment that produced them. A test, a simulation and a live observation are different evidence.
Decisions
Record the chosen direction and the reason for it. New instructions should update the current plan rather than disappear into a chat branch.
Provenance
Retain origins, licenses, existing history and authored intent. Review imports before they replace working material.
SURFACE
The overview that earns your trust.
Surface is the default first project at apps/surface: a protected project-status home and bounded operator console. Its job is to show what needs your decision, what is running, what changed, what was verified and what is blocked.
Useful visibility
- Current projects and their next concrete action
- Source freshness and pending decisions
- Verified artifacts and acceptance evidence
- Execution, verification and release as distinct states
A real operator view, not a promise made by a dashboard.
Surface needs configured authentication, durable records and a supported operator loop. The public protocol package does not install it. A private repository does not automatically make its hosting or preview private.
THE APPROVAL MODEL
Capture and build
are separate decisions.
Prepare the project.
Approve the intended destination and scoped capture: README, specification, plan, relevant existing code and acceptance definitions. Exclude secrets and preserve provenance.
That approval does not launch implementation.
Implement the approved scope.
When the package and execution prerequisites are ready, approve the Codex handoff separately. It carries the repository, current scope, acceptance criteria, environment and return path.
Access changes, spending and public launch retain their own approvals.
Once authorized, routine work can continue within that scope. A material change to the destination, data, action or permission requires a fresh decision.
THE COMPANION PRODUCTS
More interfaces.
The same need for clear authority.
The new ZekeChat is intended to carry richer conversation and project context. Zeke’s Computer is intended to provide the files, applications and execution environment around it. Surface remains the project overview; Computer is where work can happen.
These are companion product designs. They do not add a Zeke operator, shared memory service or runtime transport to Dotsys Protocol 0.1.0. Any implemented integration needs its own supported access and licensing basis.