Roadmap

Capabilities in the product today.

Help centers

Keep help articles correct in Notion, a GitHub docs folder, Zendesk Guide or Intercom Articles. Each one follows one source of what shipped: a GitHub repo or your public changelog (see What shipped).

Help-center languages

An approved fix to a source article is carried into every translation your plan covers, and code checks each language before it is sent. A language missing from a Zendesk or Intercom article can be drafted and saved as a draft (see Languages).

Notion

Map selected pages to repositories and maintain all five document types in place.

GitHub docs

Maintain Markdown folders and wikis. Writes are opt-in per repository and arrive as a commit or pull request; application code is never changed.

What shipped

Read what ships in your GitHub repos, with a change trigger per repo, or each new entry on your public changelog (see Pages & mapping), path filters and source evidence.

Review and undo

Review every change, or auto-apply grounded corrections on a paid plan or with your own key, with conflict-checked undo (see Queue & reviews).

Document generation

Generate new docs from repository history into Notion, GitHub, Zendesk or Intercom. See the estimate first and review before publishing. New Zendesk and Intercom articles are saved as drafts. Generated docs are then watched like any other page (see Generate docs).

Diagrams

Amendary designs a diagram for each engineering page a generate run writes, or for a mapped Notion page you pick, from the page and its repo’s code. It checks every label and waits for review before adding it. In early access (see Diagrams).

Cleanup

Check pages and articles in Notion, GitHub, Zendesk or Intercom against today’s code and the history of several repos. Learn which to keep, fix or retire, with the proof. It never edits a page. In early access (see Cleanup).

New page proposals

When a change adds something a set of watched pages should cover and none of them needed a fix, the daily check proposes one new page for that set. It always waits for review.

Agent-triggered checks over API and MCP

Point to a GitHub PR or commit range through the REST API or the MCP tool check_change and poll a documentation preview with evidence and correction IDs. Scoped keys, durable retries and bounded token spend are included; previews wait for human review.

Decision records

Generate architecture decision records from merged pull requests and commits, one per real decision, and keep their evidence current.

Read API and remote MCP

A REST API and MCP endpoint for corrections, check status, usage and mapped-document freshness (see API and MCP). Broader client compatibility is being tested.

The next product capabilities, not internal milestones.

Coverage gaps

Flag shipped behavior that no mapped page covers anywhere in the workspace, not only inside one set of watched pages, and suggest where a new page or section is needed.

Cross-page consistency

Find the same outdated claim across several mapped pages and prepare a separate, evidenced correction for each one.

Review feedback

Capture why a correction was accepted or dismissed and use it to avoid repeat suggestions for that repository.

Diagrams in more places

Suggest a diagram for pages in a GitHub docs folder or wiki, diagrams for generated pages in a wiki, and a new version proposed on its own when a name a diagram shows is renamed or removed.

Freshness reports

Show coverage and last-checked revisions by repository, audience, owner, and destination, with an export for release and compliance workflows.

The integration backlog. Ordering may change; these do not have delivery dates yet.

MDX

Map and maintain MDX documentation sites without moving their source content into Amendary.

Slack

Send check summaries to a channel and link to the review in Amendary.

Historical catch-up

Choose a date to check repository changes against mapped docs, previewing scope and usage first. Runs follow the team's review setting, resume safely, and leave the scheduled cursor unchanged.

Where the product can go after the source and destination foundation is in place.

Documentation graph

Connect product claims to the code, release, diagram and pages that depend on them, so one shipped change can update every affected surface without scanning everything.

Composable workflows

Let teams combine triggers, evidence sources, destinations, review rules, and notifications while Amendary continues to enforce grounding, permissions, audit, and undo.

Verified docs for agents

Extend today's mapped-page metadata and freshness tools with bounded live document content, provenance, OAuth compatibility where clients require it, and tested client integrations.