Is TOVIO ready for my team yet?

Short answer: TOVIO is pre-release. Try it on real work you have backed up elsewhere. Do not make it the only copy of anything you cannot lose.

What is built and tested

The offline core, the permission and key system, the agent and capability-token layer, networked sync, the bidirectional Git bridge, the semantic layer, and the collaboration server are all implemented and tested under documented profiles. This is not a prototype. The repository carries broad unit, property, conformance, CLI, binding, and hermetic server coverage, and a container exercise runs production binaries across distinct network hosts with a real operator certificate authority — protected grants and revocation, partial sync, replica convergence, cold backup and restore, and cross-server coordination included.

What is genuinely missing

• No independent security audit. The cryptography and the permission enforcement have not been reviewed by an outside party. For a product whose entire claim is cryptographic access control, that is the single most important gap, and it is open.
• No scale or failure evidence at the advertised ceilings. The design targets are documented; the campaign that proves the system holds there — including the large multi-agent load run — is not finished.
• No hosted service. There are no accounts, no billing, and no hosted repositories you can sign up for. Anything you read about plans or pricing describes something that does not yet exist.
• No published build. Packaging, signing, and notarization are implemented for Linux archives and packages, macOS, and Windows, but nothing has been published and none of it carries production-credential or independent-verification evidence. Installing today means building from source.
• Most specifications are not yet Stable. See the next section.

About "the format is frozen" — the honest version

You may see the claim that the object format and the wire protocol are both frozen. Only half of that is true, and the difference matters if you are deciding whether to trust TOVIO with data.

• The wire protocol specification is Stable at version 1.0.0 and formally frozen. From here it changes only by additive, byte-compatible fields, under the project's deprecation policy.
• The storage format specification is still at Review status. It is not alone: of the specification set, only two documents are Stable at all — the wire protocol and the provenance graph. Roughly half the rest are at Review and slightly more than half are still at Draft. Promoting the set to Stable for a v1 release is open work, not finished work.

What actually protects the bytes you write today is narrower and more precise than the word "frozen", and it is worth stating exactly. The on-disk format is at version 1, and the format's own versioning rule is that any change which alters the encoding of an existing object — and therefore its address — is a breaking version bump that must follow the deprecation policy with a documented migration. Chunking parameters are recorded inside each file's own manifest, so historical files stay self-describing even if repository-wide settings change later. Reserved forward-compatibility fields are round-tripped byte-exactly rather than dropped. That is a real, checkable guarantee about your data. It is not a promise that the specification text has stopped moving.

Who should use it now

People who want to evaluate a different model of version control, who can build from source, and who keep a copy of their work somewhere else. Teams with a compliance obligation that depends on an audited cryptographic implementation should wait for the audit.

What you can rely on

• Breaking changes follow a published deprecation policy and are announced in the release notes.
• The CLI --json shapes and the TVO-* error codes are a declared compatibility surface. They are safe to script and to build agent tooling against.
• Every object is re-hashed on read and on receipt. A mismatch surfaces as corruption rather than spreading quietly.
• No telemetry. TOVIO does not report your usage anywhere. Two defaults do act on their own, though, and you should know about both before you start: automatic sync is on (it only does anything once a repository has a saved remote), and agent-transcript capture is on (a commit made while an AI coding session is running may attach that session's transcript to the commit). Both are one tovio config set away from off.

The project publishes a dated, authoritative current-state document on the documentation site. When this article and that document disagree, that document is right.