How a living article works
Most technical writing is a snapshot: accurate the day it was published, silently stale the day the field moved on. Stay Current inverts that. Each subject the product covers — a topic — has exactly one current essay, called its article. There is no separate “latest” and “archive” to reconcile: the article you land on is always the one the product stands behind today.
An article states a stance — the one-sentence committed position it argues, restated at the top of the essay so a reader never has to infer where the product lands. When new research changes the picture enough to matter, the article is rewritten and its version increments: a plain integer, one higher than the last, with no separate numbering scheme to learn. Publishing a new version is called a cut — the moment research is judged to have moved the stance (or the facts beneath it) enough to warrant a new one. A topic without any recent finding worth publishing simply keeps its current version; nothing is cut for its own sake.
Every cut leaves two trails. The changelog is the topic's append-only timeline: one entry per version, in plain language, stating what moved, what it means, and whether the stance held, bent, or reversed. The provenance is the evidence behind the current article — the sources consulted and the synthesis drawn from them — rendered at the essay's close so a reader can check the work without asking. Together, currency and provenance are meant to be visible without asking: the trust header above every article states its version and research date before a single word of the essay itself.
The first research run on a new topic creates it; every run after that either cuts a new version or logs that nothing changed enough to warrant one. Either way, the record is kept — a living article is not just current, it can show its work for how it got there.