Placeholder — replace with a real walkthrough of automating a review workflow in Ozwala.
Placeholder — replace with a real walkthrough of building a knowledge base in Ozwala.
Placeholder — replace with a real walkthrough of curating a persona in Ozwala.
A jig's data goes into its repository with it, so a push to a public repository asks first: declining sends nothing. And a file bigger than a git service accepts is refused before anything is sent, rather than failing halfway.
A member browses ozwala.com's public jig directory, opens a jig, follows its repository link, and installs the jig into their desktop app from that link. The CLI then lists it, installed from the very address the directory gave.
ozwala.com's releases page says which release is current and serves it at /releases/latest/download. The CLI a member downloads from there, and the desktop app built the same way, must say they are that version -- so the releases page is not a page that merely looks right, and a bug report that quotes `ozwala version` names a real release.
A jig installed on a machine follows its repository by itself: when an agent starts Ozwala's MCP server, and when the app opens, a jig with something new is updated and its skills re-synced. Switched off -- for the jig -- it stays where it is. The state file is removed between checks to stand in for the six hours that would otherwise pass.
An installed jig follows its repository's releases. Before the first release it follows the latest commit and says so; after it, a push that is not a release does not move it. Pinned to an earlier version it stays there through updates and auto-update -- which is how you go back to one -- and unpinned it moves to the newest release.
A teammate with write access to the author's repository improves the jig and proposes it rather than pushing it: Ozwala puts the change on a branch named after them and the title, and opens a pull request. Later pushes add to it. While it is open the copy is left alone by auto-update and an update says why; once the author merges it, the next update puts the copy back on the default branch with the change, and the branch is gone. A proposal closed without merging is dropped when asked.
A user who has built a jig and keeps it in a git repository lists it on the members' site and publishes it. A second user finds it in ozwala.com's public directory, follows its repository link, and installs it into their own desktop app from that link.
Someone on a self-hosted GitLab saves one token for the host, in the CLI or in Settings > Git, and from then on every jig there pushes and installs without asking for one: a new repository is created in a group, and a second jig on the same host needs no token of its own. The token is never shown again, only the host it is for.
A developer keeps their jig in a repository on a git service Ozwala knows nothing about, reached over SSH with their usual key. They give Ozwala the repository's address and push; another machine installs it the same way. Until the server's host key is in known_hosts, Ozwala refuses to connect and says which fingerprint it was offered and how to trust it.
An author cuts a release: the version is bumped in jig.yml, committed, tagged and pushed, and on GitHub and GitLab a release page is made with the notes. On a service with no API, the tag is all there is.
The CTO's round trip. Someone builds a jig from a CSV, pushes it to a new private repository on GitHub, installs it on their second machine with a token, finds its skill already in their agent there, changes it on the first machine, pushes, and updates the second. Nothing is written by hand: Ozwala does the git work. The run records how big the pushed repository is, and that the update keeps the jig's data. Asking the jig a question through MCP needs a model, so it is in the human run.
Someone changes their jig on the laptop and on the workstation. The first push wins; the second machine is told to update first, and its update refuses to throw away its own changes until the person says to.
A member who publishes from a pipeline cannot click Allow in a browser every time it runs. Instead they make a personal token on their ozwala.com settings page and give it to the script in OZWALA_TOKEN, which the CLI uses in place of any stored sign-in.