Build it with us
Community & contributing.
The TOVIO engine, CLI, SDKs, and specification are Apache-2.0; the Forge is a proprietary commercial product. Architecture, requirements, ADRs, issues, and contribution rules will be available through the accepted public repository destination. That destination is not published yet.
Where to plug in
Six ways into the project.
Source repository
Source, issues, and pull requests will live alongside the Rust workspace, specification, ADRs, and conformance corpus in one repository. No public destination is accepted yet, so nothing here links to one.
Publication status →Contributing guide
How we work: cite the REQ-* IDs and ADRs, keep tovio-core I/O-free, and validate against the conformance corpus. Read this before your first PR.
Code of conduct
A welcoming, harassment-free project for everyone. We follow the Contributor Covenant; be kind, assume good faith, and review the change, not the person.
Code of conduct →Discussions
Feature requests, rough edges, and design questions go to the public feedback portal. Significant decisions still become ADRs, so a well-argued post is often the first step toward a merged proposal. Security reports never go there.
Feedback portal →Security disclosure
TOVIO's permission system is security-critical. Never open a public issue for a vulnerability — follow the responsible-disclosure policy in SECURITY.md.
Governance
How decisions get made and who maintains what. The CLI governance rule — "to add a command, remove or merge one" — keeps the surface small on purpose.
Governance summary →