How OotaOS writes the Knowledge Centre
The OotaOS Restaurant Knowledge Centre exists to answer restaurant owners' real questions about technology — clearly, honestly, and from first-hand experience of building the platform. This page explains how every article is made, so you can judge for yourself how much to trust one.
How topics are chosen
Topics come from real demand signals: questions restaurant owners ask in public communities, searches that reach our pages, and the problems our own customers bring to support. We write one strong page per question rather than many thin variations, and we skip topics we have nothing first-hand to add to.
How product claims are verified
Any sentence that says OotaOS does something is checked against the platform's internal feature register — the same machine-readable list our engineering tests enforce — before the article can be published. A feature that is partial, flagged off, or planned is not described as available. Automated checks block publication when an article references a feature the register does not list as implemented.
How changing facts are handled
Prices, provider capabilities, tax rules and regulations change. Claims like these carry visible sources with the date we last checked them, and every article declares a review interval. Articles touching tax, payments, legal or compliance topics additionally require a named human reviewer before they can be published — we never invent reviewers, and an unreviewed risk-bearing draft simply stays unpublished.
How articles stay current
Each article records the date it was published and the date it was last meaningfully changed. We update that second date only when the substance changes — never to look fresh. Articles past their review interval are flagged internally and either updated, merged into a stronger page, or retired with a redirect.
How AI assistance is used
We use AI tools in producing this content: for research assistance, drafting and editing. Every article is directed, fact-checked and approved by the named author, product claims are verified against the feature register by automated checks rather than trust, and nothing is published without human review. AI never invents customers, statistics or experience — if an example is illustrative rather than real, the article says so.
What we will not do
No fabricated case studies or statistics. No fake reviewers or invented authors. No pages that exist only to catch a keyword. No claims about features that are not live. No pretending an article is fresh when it is not.