How we write these docs

The Tovari docs explain what the app does, and they're also what the in-app help chat reads when it answers your questions. Here's how a page gets written, checked and kept current.

Who is responsible for these pages?

Jason Ewing, Tovari's founder, is responsible for what every page says. If you find a mistake, email support@tovarifinancial.com and we'll fix it.

How are pages drafted?

Pages are drafted with the help of an AI model working from Tovari's own source code. Starting from the code means a page describes what the app actually does, not what we meant it to do.

How are they checked?

Every docs change is checked against the code it describes before it's published. Some facts, like the Safe to Spend planning windows and the bank import history options, are also tied to the code by automated tests, so those pages can't quietly drift from the app.

What do the dates mean?

Each page shows when it was first published and when it was last updated. Both dates come from the page's own change history, so a date only moves when the page itself changes.

Where do outside facts come from?

When a page depends on another company or a published standard, such as Plaid for bank connections, it links to that source's own documentation in a Sources list at the end.