USER-FACING APPLICATION
Sykes VCS Application
The Sykes VCS Application is the user-facing version-control experience built on the Sykes VCS Engine and Sykes DB. It turns structured source history into workflows for repositories, collaboration, review, provenance, and recovery.
The main Sykes VCS experience
The Application is the component most users interact with. It is intentionally part of a clean Git replacement rather than a Git-compatible shell, because the source model underneath is based on CRDT operations and structured history.
- Aimed first at solo developers and small teams.
- Designed for people working with coding agents as part of normal development.
- Built around understandable source history rather than opaque snapshots alone.
Repositories, history, review, and recovery
The Application gives product meaning to the operation stream. It presents repositories, branches, provenance, comments, review state, and recovery workflows without requiring users to reason about every low-level database record.
- Expose structured history as a usable source-control workflow.
- Connect review and comments to meaningful changes.
- Make undo, redo, provenance, and collaboration visible when useful.
Built for people and coding agents
Human and agent edits can use the same structured history while retaining distinct identities. The Application can show that distinction when it helps review, or present one combined change when that is the clearer view.
- Review can follow the edits that produced a change.
- Agent work can remain distinguishable from human work.
- Multi-machine and team workflows build on the same durable history.
A product assembled from focused components
The Sykes VCS Engine owns the CRDT edit model, Sykes DB owns durable operation storage, Editor Plugins connect editing tools, and shared components provide reusable foundations. The Application combines those capabilities into the version-control product.
- The Engine structures and applies edits.
- Sykes DB preserves the operation history.
- The Application owns user-facing workflows and product context.
Local proof before broad release
The Application is still early and should not be trusted for production. The first usable version is intended to prove the complete local path before expanding into a broader hosted product.
- Prove the Engine and database foundation first.
- Demonstrate basic version-control operations end to end.
- Earn trust through working software and visible progress.
NEXT STEP
The Application turns the component system into a product
The Sykes VCS Application is where durable CRDT history becomes practical version control. Its behavior depends on the Engine, Sykes DB, Editor Plugins, and the shared component layer working together.