Verify a Tvijo claim in five minutes

Any sentence about this product should be reproducible by someone else in a few minutes, without credentials. This page is the recipe we use on ourselves.

🧭 The five checks

1. Does the page exist and is it public?

curl -s -o /dev/null -w "%{http_code}\n" https://tvijo.com/wiki/getting-started/

200 means the page is served. 404 is the honest answer for a draft: drafts are not public, and a staff preview uses /wiki/<slug>/?preview=1.

2. Is the article in the published index?

curl -s https://tvijo.com/wiki/articles.json | python3 -m json.tool | head -20

The index is built from published rows only. If a title is missing here, it is not published — regardless of what a screenshot shows.

3. Is the address discoverable?

curl -s https://tvijo.com/wiki/sitemap.xml | grep -c "<loc>"
curl -s https://tvijo.com/robots.txt | grep -i sitemap

A page that is public but absent from the sitemap is a defect: readers find it, search engines may not. robots.txt must advertise the wiki sitemap.

4. What did it cost?

Open Usage. For a specific task it shows the provider, the model, the token counts, the task limit and the spend. A cost figure without a receipt is a claim, not a measurement.

If the state says uncertain, the honest answer is "cost unknown", not zero.

5. Does the code agree?

Product claims live in two places: the deployed service and the public description of it. When they disagree, the deployment wins and the description is wrong.

For a claim about a check, ask for three things: the command, its return code and an excerpt of the output. "It works" is not one of them.

📊 What a verdict looks like

Write per criterion, not per document:

NOT_RUN is a first-class verdict. It means nobody ran the check; it does not mean the check failed and it must never be quietly promoted to PASS.

🚧 When this does NOT work

• The claim is about intent. "We plan to support it" is not verifiable; only the shipped state is.
• The check needs credentials. Then it is not a five-minute public check; ask the owner for a receipt instead.
• The page is cached. Add a cache-busting query (?v=2) before declaring a regression — and remember that a stale CDN copy is not a broken deployment.
• The number is a benchmark. A benchmark without a date, a workload and a method is an anecdote. Compare receipts from your own tasks.

🧾 A rule we apply to ourselves

Every article in this wiki lists its sources with the date a human opened them. If a source is dead, the article is a defect to fix — not a citation to delete quietly. If a number has no source, it does not go in.

➡️ Next

• Sources and verification — the evidence ladder behind this recipe.
• AI judging — the same discipline for agent output.
• Costs, budgets and limits — reading a receipt.