Article
One page of a help center, such as a Zendesk Guide or Intercom article. Amendary checks the source-language version and carries each fix into its translations.
The terms used across the dashboard and the help pages, each defined once. Link to an entry with its anchor.
Watching a page or article is how you tell Amendary it matters. A destination lists its pages, but a listed page does nothing until you watch it. An Engineering docs page also needs a map to a repo. A page you do not watch is never read or edited. Unwatch stops watching the page and the watched pages under it, and drops their repos.
Mapping ties a watched page to the repo it describes, so a change in that repo can trigger a check of that page. A Notion page can be mapped to several repos, and a mapping can be narrowed to a path inside the repo. A GitHub page maps only to the repo it lives in. A help-center article is mapped for you to the repo its help center follows, or to no repo when it follows a changelog URL.
The role of one mapping, set on the Pages tab. Describes this repo: the page is about that repo, and its changes start checks. Background only: the page leans on that repo for context, and its changes start no check unless Check when this repo changes too is ticked. A repo’s context notes and paths are edited on the Repos tab once it is Background only on a page.
Who a watched page is for: Engineering docs (checked against code changes) or Help center (checked against what shipped). The audience sets which doc types the page can have, its default tone and which review mode applies to it.
For Notion and GitHub pages: set the audience to “Checks paused”, or use the bulk action. The page is not checked or edited, and its repo mappings are kept. Setting an audience again resumes checks. Zendesk and Intercom articles are unwatched instead.
A watched page with at least one repo mapping, or a help-center article that follows a changelog URL. Only these are checked. A correction goes to the page’s own home: an article edit in Zendesk or Intercom, a Notion edit, or a GitHub commit or pull request.
Where your articles or docs live: Notion, GitHub (a docs folder or wiki), Zendesk Guide or Intercom Articles. Added on the Pages tab with Add destination. Generated docs go to the one destination you pick; corrections go to every watched page wherever it lives.
Customer-facing articles in one destination that follow one source of what shipped. Every Zendesk and Intercom article is Help center; a Notion or GitHub page is Help center when you watch it that way.
The changes a help center is checked against: a GitHub repo or a changelog URL, never both. It is set under Help articles follow on the destination’s card.
A public changelog page, or its RSS or Atom feed, that a help center can follow instead of a repo. Each new dated entry is checked like a release.
One page of a help center, such as a Zendesk Guide or Intercom article. Amendary checks the source-language version and carries each fix into its translations.
An article in another language. It is never checked on its own: it gets the fix of its source article, approved once.
The language an article is written in first. Only that version is checked against what shipped.
A repo setting on the Repos tab: commits on the default branch (the default), commits on a branch you name, published GitHub Releases, or new tags. The product-updates page and the articles of a help center that follows a repo follow it. A help center that follows a changelog URL is checked on new changelog entries instead. Engineering docs always follow commits on the default branch.
A short summary of one unit of change (a merged pull request, a direct commit, a release or a tag), kept with the changed paths and a link to the source. It orients the check and appears on the correction card as evidence. Raw diffs are processed and discarded; the summary is what is stored.
A correction is grounded when the change backs up what it says. Grounding is checked on the blocks the edit changes, against the shown change and the code after it. Only hard values gate publishing; soft values (bare numbers, Title Case phrases) are shown as “check these” and never hold.
A version, a path or a URL. A hard value in an edit that the change does not back up is “ungrounded” and holds the correction for a person, even in auto mode. Bare numbers and product names are soft values, not hard ones.
A label on a correction card saying the page or the change was too large to show the model in full, so it saw the sections around the change instead. It is a warning to inspect, never a hold on its own. A card whose matched sections were all shown whole does not carry it.
Where corrections, product-update drafts, proposed new pages and diagram proposals wait for a person. Its tabs are Needs review, Snoozed, Auto-applied and Resolved. Under Review first and during the free trial every correction waits there; in auto mode only the ones a hold applies to.
A reason a correction waits for a person in auto mode, such as a hard value the change does not back up or an edit that removes content. The card names it. The full list is in Queue & reviews.
The Apply automatically review mode, set per audience by owners on a paid plan. A correction nothing holds is applied to the page on its own and logged. Auto mode publishes; it does not queue. The free trial stays review-only whatever the saved mode.
Set on Settings > General, once for Engineering docs and once for Help center: Review first or Apply automatically. Product updates and every help center (Notion, Markdown, Zendesk and Intercom) follow the Help center setting. Review first is the default for every new workspace: nothing is written to a page until a person applies it from the Queue, including corrections that would pass every check in auto mode.
Amendary’s way of saying a mapped page no longer matches what shipped. It names the region of the page that is now wrong, shows it rewritten as it should read with the blocks that change, and attaches the evidence. Each region can be applied or dismissed on its own. See Queue & reviews.
A short, customer-facing entry describing what shipped, added under a dated heading on a Notion page set to the Product updates type. One entry per repo per landing day, where the day follows the team’s timezone. The page’s Amount setting is Highlights (every new feature and improvement, fixes left out) or Every change (one bullet per customer-facing change, shown as Breaking, New, Improved and Fixed). Pull requests with a label in the page’s “Skip pull requests with these labels” list are left out. Product updates are Notion-only and are never one entry per commit.
The type of a page, set on its row on the Pages tab: Docs & guides (the default), On-call runbook, Incident playbook, Architecture decisions or Product updates. The audience limits the choice: Product updates is for Help center pages only, and runbooks, playbooks and decision records for Engineering docs. It says how the page is checked and what generate produces for it. A page has one type for all the repos it is mapped to. See Document types.
How a page reads: Formal or Conversational. It is set per page on its row on the Pages tab. A page with no tone uses its audience default: Conversational for Help center, Formal for Engineering docs. A generate run uses the tone of the parent page it writes under.
The team’s timezone, on Settings > General (UTC until you change it). It sets where the team’s day starts: the date a product update lands on and when the daily usage limit resets. The daily check still runs once a day at the same time for every team.
What the runs you start on demand spend: generation (page sets, changelog backfills, diagram suggestions, missing-language drafts) and cleanups. Each run shows its estimate first, holds it, and refunds what it did not use. Daily checks and corrections never spend credits. The free trial has none; the first paid month includes a one-time grant (10 on Starter, 20 on Growth and 40 on Scale). See Billing & plans.
A picture of how the parts of a system connect, designed by Amendary for a Notion page from the page and its repo’s code. Every label must appear in what Amendary read. It is rendered on our server as an image and an SVG. A suggested diagram waits in the Queue and reaches the page only when a person selects Add to page; a generated engineering page gets one in the run’s review. In early access. See Diagrams.
An on-demand run that checks the pages you pick, in any destination, against today’s code and the full history of the repos you pick, and marks each page Keep or Probably remove, with a reason, a confidence and short guidelines on what to do. A page is Probably remove only when what it is about is gone from every repo checked, with the proof. A cleanup never edits a page. See Cleanup.
The per-repo opt-in that lets Amendary write docs to that repo, as a pull request (the default) or a commit to a docs folder, or directly to the wiki. It is off by default, one target per repo, and only owners can turn it on or edit it. A repo with it off is strictly read-only, and code is never changed either way.
Restores the text a correction replaced, from the original stored in Amendary, after checking the block has not been edited since; if it has, the undo is refused. Available on the Queue’s Auto-applied and Resolved tabs for 30 days after a correction is applied.
Connect Notion, GitHub, Zendesk or Intercom and pick the articles to watch. Your first check shows what Amendary would fix, with the change as proof.
Free for 14 days with no card, and every edit waits for your review. Or free forever with your own Anthropic API key. Code is never touched.