Documentation changelog
What changed in this knowledge base, newest first, starting with the initial build on 6 August 2026.
Last updated 2026-08-06
Summary#
This page records changes to the knowledge base itself, which is a different thing from changes to the platform. Release notes tells you what changed in Metric Vault; this page tells you what changed in the pages that describe it. Use it to see whether an article has been revised since you last read it, and to understand what a given entry did and did not cover.
Overview#
The knowledge base is one source set covering the whole platform: the customer help center, the administrator manual, the developer guide and the reference the support team works from. It is organized into fifteen categories, and every article follows one of eight fixed shapes, so once you know how a tool page or a troubleshooting page is laid out you can predict where any fact will be on any other page of that kind.
Three rules govern how it is maintained, and they explain most of what you will see below.
- One fact lives in one place. If two articles need the same explanation, one owns it and the other links to it. Duplicated explanations drift apart, and a reader who finds the stale copy has no way to tell.
- Every number is traced to the running platform. Credit costs, quotas, seat limits, cache lifetimes and error text come from the product, not from marketing material or memory. When a value changes in the platform, the article that states it changes in the same piece of work.
- Article addresses never change. A page can be retitled and rewritten, but its address stays the same, so a link you saved or a link a support agent sent you keeps working.
Each entry below gives the date, what changed, and whether anything you might have bookmarked moved.
2026-08-06 — Initial build#
The first complete version of the knowledge base, written from the platform itself rather than from existing marketing or support material.
| Aspect | What was delivered |
|---|---|
| Scope | The whole product: every dashboard tool, plans and billing, account and team management, integrations, automation, reporting and sharing, the free tools and browser extension, the public API, security and privacy, troubleshooting, and this reference layer |
| Structure | Fifteen categories, each with a landing page. Growth is absorbed by adding subcategories, never by adding depth, so nothing is ever more than three clicks from the home page |
| Article types | Eight, each with a required shape: concept, task, tool, reference, journey, troubleshooting, architecture and landing |
| Plan | 293 articles planned, listed with their type, audience and subject before any were written, so coverage can be measured against the plan rather than guessed at |
| Sourcing | Every article was written against the platform's own behavior. Button labels, field names and error messages are quoted exactly as they appear on screen, and numbers were read from the running system |
| Cross-linking | Articles declare their relationships rather than carrying hand-written link lists, and every inline link is checked. A link to a page that does not exist stops the build, so the set cannot rot into dead links |
| Internal sections | The administrator and developer categories are marked as internal and are written in a different register: precise, mechanical and specific. They sit in the same tree so a support engineer can move from what a customer sees to what the system did in one step |
| Screenshots | Every place an image belongs is marked with a labelled placeholder, so illustration is a single pass rather than a hunt |
Known gaps in this first version#
Being straight about the edges is more useful than implying completeness.
| Gap | Detail |
|---|---|
| Screenshots | Marked but not yet captured. Articles read correctly without them |
| Translation | The knowledge base is written in English. The product interface ships in six languages; these pages do not yet. See Supported languages |
| Coverage | Articles are tracked against the plan, and any that are still to be written are known and listed rather than silently missing |
| Publication | The pages are maintained as one source set; where and how they are published is a separate decision from writing them |
Conventions established#
These hold for every article added from here on.
| Convention | Rule |
|---|---|
| Exact strings | Interface labels and error messages are quoted character for character, in code style |
| Exact numbers | Costs, quotas, limits and lifetimes come from the platform. Nothing is approximated to cover a gap |
| No unearned claims | If the platform does not do something, no article says it does. Where a feature is absent, the article says so plainly |
| The "why" first | Every article explains why a thing exists before explaining how to use it |
| Complete references | A reference page is exhaustive for its subject. A reference that sampled would be worse than none, because you could not tell whether the row you wanted was missing or absent |
How this page is maintained#
An entry is added whenever a change affects what you would read, not for every correction of a typo. Specifically, expect an entry for:
- A new article, or an article removed.
- A documented number, limit or price changing.
- A behavior being documented differently because the platform changed.
- A structural change, such as a category or subcategory being reorganized.
Each article also carries its own updated date, which is the more precise signal for a single page. This page is for changes worth knowing about across the set.
Reporting an error in the documentation#
If a page contradicts what you see on screen, the page is wrong and we want to know. Send the article title, the sentence that is wrong, and what the product actually does, to hello@metricvaultai.com. See Contacting support.
Documentation errors are treated the same way as product errors: the article and the underlying fact are checked together, because a page that disagrees with the platform usually means one of the two changed without the other.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.