What happens if the project stops

Version control holds the asset a software organisation can least afford to lose, and TOVIO is an early, single-maintainer project. "What if you disappear" is a fair question, and the answer should be mechanisms you can verify rather than intentions.

The licence does not expire with the project

The Apache-2.0 grant over the engine, CLI, bindings, SDKs, and the specification is perpetual and irrevocable, including its express patent grant. A copy you already have stays licensed to you, to modify and to redistribute, regardless of what happens to the project. Nothing about the commercial Forge changes that — the Forge is a separate product, and the engine has no dependency on it.

Your repository is already a complete copy

A clone is the whole thing: objects, history, and refs on your own disk. Committing, branching, reading history, resolving conflicts, and decrypting content you hold keys for all work with no network. There is no service that has to stay up for your existing repository to remain usable, and no hosted component in the free tier — the server built into the Apache-2.0 CLI is a real bidirectional server you run yourself.

The bytes are documented, and the documentation is open

The storage format, wire protocol, cryptographic envelope, policy and token contracts, and the conformance corpus are Apache-2.0 and publicly versioned. This was made a separate decision from the Forge's licence deliberately, precisely so that the anti-lock-in guarantee does not depend on the commercial product's terms.

The corpus is the part that matters most here. A specification alone can be ambiguous; a corpus of objects with known encodings is a test another implementation can be held to. Old corpora are frozen and never deleted.

Someone other than the project has already read it

A dependency-free independent implementation, sharing no encoder with the reference one, re-hashes the addressed version-1 fixtures and reconstructs object families from the specification alone in continuous integration. That is evidence the specification is sufficient to reimplement — the property that makes an open format a genuine exit rather than a gesture.

An implementation that passes the whole corpus for the format version it claims may call itself TOVIO-conformant. The bar exists so the claim stays meaningful.

You can leave to Git

The project maintains a Git bridge: history imports from Git, and it exports back out to Git. If the answer to a continuity problem is "move the history somewhere very boring", that path exists rather than needing to be invented under pressure. See the Git collection for what each direction carries and what it does not.

What is honestly not guaranteed

• The commercial components. The Forge, the hosted service, and the enterprise modules are proprietary, and an escrow or source-availability arrangement for them is a commercial conversation, not a published policy. Do not assume one.
• Continued maintenance. An irrevocable licence guarantees you may continue; it does not guarantee anyone will fix things for you. That is the fork you would be taking on.
• A published support lifecycle. No release has been tagged and no end-of-support dates exist yet.

The check to run before you commit

Take a clone, disconnect it from every network, and do a day's ordinary work in it. That exercises the continuity claim directly, and it takes less time than reading a contract about it.