Skip to main content
Start here

Where everything lives

Docs, help center, boards, roadmap, release notes, security — one map.

Written By Dustin

Last updated About 1 month ago

TOVIO's material is split across a few places on purpose. This is the map.

This help centerTask answers, troubleshooting, and how the project works as a service. Short articles that answer and then link onward.
Documentationdocs.tovio.dev — the system of record. Command reference, concepts, tutorials, guides, specifications, and the error catalog. When this help center and the docs disagree, the docs are right.
Error code pageshttps://tovio.dev/errors/<code> — an error prints its own link on the last line of the error block, so you rarely have to search for it. The generic TVO-CORE-000 fallback has no page and therefore no link.
Feedback boardsfeedback.tovio.dev — bugs, feature requests, and documentation problems. Public, and moderated before posts appear.
RoadmapOn the feedback portal. Status-only, and deliberately carries no dates.
Release notesThe changelog on the documentation site. This is the system of record for what shipped; every other announcement is a copy of it.
Securityhttps://tovio.dev/security and security@tovio.dev. Never a public board.
SourceThe engine, CLI, SDKs, editor integrations, and specification are Apache-2.0. The Forge and the web dashboard are commercial.

Reference documents worth knowing about

  • A dated, authoritative current state document listing exactly what is implemented, what is deferred, and what is a deliberate non-goal. It overrides every other status claim, including the roadmap and this help center.
  • The error catalog, which defines the three-part error standard, the TVO-<AREA>-<NNN> namespace, the exit-code classes, and the structured --json error shape agents and scripts bind to.
  • A complete capability catalog — every task TOVIO can perform, with the command against each. Treat its build-status column as secondary to the current-state document.
  • The threat model, including the accepted residual risks for this release, which is worth reading before reporting a security issue.
  • The compatibility and deprecation policy, which names every versioned surface and the rollback boundaries that go with it.

All of these are on the documentation site.

Was this helpful?

Still need help? Ask the team