Sources, dates and what “verified” means

Every article in this wiki carries a source list. Each entry has a link and a checked date. That date means one specific thing: a human opened this source on that day and confirmed the sentence it supports. It is not the date the source was written, and it is not the date the article was generated.

🔹 Three levels of evidence

We keep them separate because they answer different questions:

A claim supported only by level 1 is written as a description of the documentation, not as a fact about the running system. For example: "the release notes state X" — not "X is true".

🔹 Status labels on product claims

When an article describes a capability, the wording follows the state of the deployment:

• Available — you can use it today, and we have seen it work.
• Experimental — it exists, it is usable, but the behaviour or the packaging may change. Test builds and MCP integrations are in this class.
• Planned — designed or agreed, not shipped. Written in the future tense, with no promise of a date.

A capability that is gated behind a disabled flag, an unmerged branch or a missing deploy is not "available". That distinction is the most common way product documentation lies by accident.

🔹 Numbers without a source are not numbers

Rules we apply to figures:

• A measurement carries the date it was observed and the command or query that produced it.
• "Not measured" is written as not measured. Never as 0, and never as an estimate dressed up as a measurement.
• A percentage without a denominator is not a result.
• "Improved" needs a before and an after, from the same method.

📚 Checking a source yourself

1. Open the link from the article's source list.
2. Search the page for the exact claim (not the general topic).
3. Compare the date: an old source can support a historical statement, not a current one.
4. If the source contradicts the article, the article is wrong — that is a correction, not a debate.

If a link is dead, the article keeps the citation but the check date stops being renewed; a dead source is a defect to fix, not a source to delete quietly.

🚧 What we never publish

• Internal hostnames, private IPs, tunnel addresses.
• Keys, tokens, session strings, account ids.
• Customer or contact data.
• Private journals and operational logs.
• Screenshots that contain any of the above.

A public repository is not a licence to publish its contents: each component is checked for its own licence before we quote or redistribute it.

🚧 When this does NOT work

• You need a legal guarantee. A wiki article is not a contract; the contract is a signed document.
• You need the newest behaviour within minutes of a deploy. Check dates are human-scale — that is the price of verification.
• You need a single source of truth for pricing. Prices come from your own receipts, not from an article.

➡️ Next

• How this wiki is edited and published — the workflow behind the labels.
• AI judging — the same evidence ladder applied to agent results.
• Glossary — definitions of the terms used here.