Workflows
How the concepts combine into working practice: the recommended Nexa workflow, coming from Git, local-first work, and several contexts at once.
The concept pages define the vocabulary one term at a time. These pages put it to work: each describes a way of actually using Nexa day to day, and they overlap deliberately, so you should read the one that matches your situation rather than all of them in order.
Which workflow applies to you
Working the Nexa way is the recommended path, and the one to read if you have no particular reason to pick another. It covers the multi-project shape in depth: one Development Root holding all your active work, several working contexts beneath it, every command run from the root, and sync as the single step that exchanges work with Rinko Hub.
Working inside a project directory is the Git-style alternative: change into a project and run the same commands there without naming it. It also covers a standalone repository with no Development Root at all. Read it if you prefer to live inside one project at a time.
Coming from Git is for anyone with existing Git habits. It maps the four everyday operations across, then is explicit about where the models genuinely diverge — no staging area, and a branch that holds competing candidates instead of a pointer. Read it before you reach for a reflex that will not work here.
Working local-first is for a folder of files you already have, and for anyone who wants version control without an account. It covers making an existing directory Nexa-managed, recording into it offline, and deciding later — if ever — whether the work becomes hosted.
Several contexts at once is for working on more than one thing simultaneously: several repositories, or several branches and attempts within one, side by side under a single root without either interfering with the other.
Humans and AI together is for teams where a person and an AI tool work on the same repository. It explains how the candidate model lets both attempt the same task without either overwriting the other, and is equally clear about what is not built.
If the terms in any of those descriptions are unfamiliar, start with Core concepts, which defines them in dependency order, or look one up in the glossary.