A release shipped.
Which article needs a human?
Paste abstract public release changes and a small public article index. Exact product-area rules produce a review queue with reasons and uncertainty—never a claim that a document is wrong or an instruction to publish.
Release-triggered knowledge review queue
| Change | Area / type | Candidate article | Action class | Deterministic reason | Human receipt |
|---|
Holds and next checks
A candidate means “inspect this public article.” It does not mean the article is stale, incorrect, legally required, safe to archive or ready to publish. Product-area labels and public source pages can themselves be wrong.
Knowledge and privacy boundary: this browser-only tool never signs into a help center, crawls a private site, reads tickets, rewrites content, publishes changes or certifies correctness. It maps only user-entered public aliases and URLs. A human owner must inspect the current release, affected behavior, audience, existing article, dependencies, localization and approval workflow before any change.
$9/mo Release-to-Knowledge Review Membership
Export a reusable monthly queue, product-area map, human review receipt, localization handoff and CSV schema. Membership buys repeat structure—not monitoring, account access, rewriting or publishing.
- seed release-to-article candidate ledger
- blank multi-product monthly intake queue
- area ownership and localization matrix
- update/create/archive/no-impact review receipts
- second-release return-use evidence card
- human edit and publication sign-off
Research gate, category leaders and substitute pressure
PMF pre-judgment 76/100 · recurring support drift is costly, but Guru, Intercom and help-center platforms are strong substitutes