Changes name the work
A Change ID remains stable across the supported rewrite operations. A lane is a landing target, not a second identity for the work.
Coming from Git
Keep the workflow. Change the primitives.
TOVIO separates a unit of work—a change—from the shared pointer it eventually advances—a lane. That distinction shapes review, rewriting, synchronization, and conflict handling.
The product documentation identifies implemented commands, supported profiles, and specification-only behavior. Use it as the source of truth when planning a migration.
The short version
Three differences to understand first.
Concurrent refs reconcile deterministically
Native synchronization uses TOVIO's ref and conflict model. Authorization, protected-lane, review, and integrity checks can still refuse a proposed mutation.
Conflicts and local undo are explicit
Conflicts are stored objects. Undo covers supported mutations retained in the local op-log; it does not recall peer observations or reverse external or explicitly irreversible effects.
Concept map
Useful starting points—not one-to-one aliases.
TOVIO does not promise that arbitrary Git commands translate automatically. These mappings orient readers; the linked documentation defines exact behavior.
| Git concept | TOVIO starting point | Important difference |
|---|---|---|
| Commit on a branch | tovio commit, then tovio land | Recording a change and advancing a shared lane are separate operations. |
| Branch | Change stack + lane | The work and its eventual landing target have different identities. |
| Push / pull | Native sync, push, pull, and clone surfaces | Server authorization, policy, and protected-ref checks still apply. |
| Pull request | Proposal | Review follows the stable Change ID and a reviewed commit. |
| Merge conflict | Typed conflict object | The conflict is durable data that can be inspected and resolved later. |
| Reflog recovery | Local op-log + undo/redo | Only supported, retained local mutations are reversible through this boundary. |
| Git LFS | Chunked addressed objects | Large binary content uses the normal verified object path rather than a separate LFS pointer. |
Simulated comparison
One illustrative feature workflow.
This is a conceptual demonstration. It does not execute commands, create a repository, contact a Forge, or prove availability of a release artifact.
GIT
git switch -c feature/parser git add -A git commit -m "add parser" git push origin feature/parser
TOVIO
# work is recorded in a change tovio commit -m "add parser" tovio land --into main # actual policy and review gates still apply
Continue in the docs
Use the maintained guides for operational detail.
Migration guideImport a repository and understand the supported bridge boundary.Coming from GitLearn the conceptual model without assuming command parity.Branching modelsMap feature, release, and environment workflows deliberately.CLI referenceCheck exact verbs, flags, and implementation status before use.
Explore the public read surface.
The marketing explorer shows only a server-authorized public projection. Account, review, and repository mutations remain isolated on the authenticated app origin.