Docs that stay correct after every change

• Once a day, Amendary reads what landed in each connected repo and checks it against the pages you watch, in Notion or in a repo’s docs folder or wiki.
• When a change makes a passage wrong, it drafts the correction: the section rewritten as it should read, with the blocks that change, are added or are removed.
• A Notion page set to Product updates grows instead of being corrected: a short, dated, customer-facing entry for what shipped.
• When a change adds something a set of watched pages should cover and none of them needed a fix, the check may propose one new page for that set. It always waits for you.

1. You watch a page and map it to the repo it describes. A page you do not watch is never read for a check.
2. Engineering docs follow each landed commit on the default branch, one merged pull request or direct commit at a time. Customer-facing pages follow the repo’s change trigger: commits by default, or a branch, published releases or tags.
3. Amendary keeps a short index of what each page says about the code. A change is matched against it, and only the sections it touches are drafted.
4. The correction goes to the page’s own home: a Notion edit, or a commit or pull request for a page in a repo.

The full mechanism, including what the model sees, is on How it works.

• It never changes code. It writes docs to a repo only where an owner turned GitHub docs on for that repo.
• It never checks an open pull request on its own. A change counts once it has landed.
• It never treats Markdown, docs, help, legal or marketing files as evidence of what the product does.
• It never writes over a passage that someone edited after the correction was planned.
• It never writes a product update for docs, website or internal-only changes, and never one entry per commit.

Every correction shows the old text, the new text, and the commit or release behind it, with a link. New workspaces start in review mode, so every correction waits in the Queue. The free trial is always review-only.

On a paid plan an owner can turn on auto mode. Corrections then apply on their own, except a correction that states a version, path or URL the change does not back up, removes a value the change does not mention, removes or shrinks content, may replace a decision record, or adds text outside a narrow grounded case. Those wait, and so does every proposed new page. The full list is in Queue & reviews.

Every applied change is in the audit trail, and Undo restores the original text for 30 days after a check that nobody edited it since.

• Repos and mapped pages per plan: Starter 2 repos and 15 pages, Team 5 repos and 50 pages, Scale 15 repos and 150 pages. The free trial covers 1 repo and 3 pages for 7 days.
• Checks run once a day. A workspace has a daily model budget; a change that does not fit waits for the next check and the check says so.
• Product updates live in Notion only. An entry has at most three short bullets, a repo gets at most one entry per day for its commits (releases and tags keep their own), and a repo feeds one product-updates page.
• At most three new-page proposals per repo per day.

Included in the flat subscription. A check never spends credits, however many corrections it drafts. See Pricing.