Why Amendary
An honest look at where we fit
Amendary does one thing: when you ship code, it keeps the documentation you already have in sync. That is a narrow job on purpose. Here is how it relates to the tools it is often compared with, said plainly and without knocking them, they are good at what they are for.
The wedge
Most doc tooling helps you write docs or answer questions from them. The expensive problem is different: docs you already wrote slowly going wrong as the product changes, and nobody noticing until a customer hits it. Amendary watches your releases and changes, finds the sentences a change made wrong on the pages you mapped, and corrects them with the evidence attached. Maintenance, not authoring.
AI coding assistants and workflows
For example Claude in your editor or CI, and general agentic coding workflows.
- What they are for
- Write and change code, and can be scripted to touch docs as part of a task you trigger.
- Where Amendary differs
- Runs on its own on every release against the specific Notion pages you mapped, drafts a grounded correction, and either applies it or queues it for review. It is a standing maintenance loop with an audit trail, not a prompt you have to remember to run.
Doc Q&A and support bots
For example tools that answer questions from your code or docs.
- What they are for
- Answer a reader's or a ticket's question using your docs and code as a source.
- Where Amendary differs
- Does not answer questions. It changes the source page itself so it is correct next time, so the answer a bot (or a person) reads is right, rather than a bot papering over a stale page.
Documentation platforms and generators
For example hosted doc sites and from-code doc generators.
- What they are for
- Give you a place to host docs, or generate reference docs from code or an API spec.
- Where Amendary differs
- Works on the docs where they already live (Notion), and maintains prose that no generator produces, the how and why a person wrote, not just the auto-generated reference. Amendary can generate a set to start from, but the point is keeping it current after.
What that means in practice
- Amendary never changes your code. It writes to a repo only when you turn on GitHub docs for it, and then only docs, as a commit or a pull request you review.
- It only ever reads and edits the pages you explicitly map. Nothing else is touched.
- Every correction is grounded in a specific change, logged, and reversible.
- Confident, fully grounded corrections apply automatically; anything uncertain waits for you.
See how it works or the roadmap.