[Amendary]

Roadmap

Updated as things ship, not on a fixed calendar

The core idea does not change: when you ship code, Amendary keeps the docs you have mapped in sync. Everything below serves that. Dates are deliberately absent, we would rather move an item up when it is real than miss a date on a page.

Shipped

Running in the product today.

  • Release and daily change detection, with corrections drafted and evidence attached.
  • Auto-apply for confident, fully grounded corrections; everything uncertain waits in the queue.
  • Core and supporting repos: one repo's docs can be judged with another repo's changes as context.
  • Docs from scratch (add-on): generate a documentation set with tables, callouts, diagrams, page icons and an index.
  • Per-run cost, token and cache visibility in Settings, plus a platform usage view for admins.

Next

Built or in progress, rolling out behind a flag before it is general.

  • New document types beyond prose: on-call runbooks and incident how-to-fix playbooks generated from your repo, and a dated Product updates changelog that grows as you ship: one page per month or week, entries appended as bullets, following your review mode.
  • Grounding warnings surfaced in review, so you can see any operational value (a command, path or flag) that is not backed by the repo before you publish it.
  • Generated pages registered for maintenance automatically, so a runbook stays current instead of going stale the day after it is written.
  • Docs that live in GitHub, as a docs folder or the repo wiki: discovered as pages, kept current like Notion pages, corrections written back as a commit or a pull request you review. Opt-in per repo, independent of Notion.

Exploring

Directions we think are right, not commitments.

  • More change sources beyond GitHub: GitLab and Bitbucket, so the same release-driven loop works wherever your code lives.
  • More documentation targets beyond Notion and GitHub: Confluence, and MDX docs sites, so Amendary maintains docs where you actually keep them.
  • A public API and an MCP server, so your own agents can ask Amendary to check a repo, read pending corrections, and apply approved ones directly, no dashboard round-trip.
  • Diagrams as a first-class output (for example generating figures, not only text).
  • Roadmap pages that the release loop keeps current on their own.
  • A GitHub Discussions bot: watch discussions, answer from your docs, and resolve them when the docs already cover the question.
  • A Slack integration for the roadmap: post and update roadmap items in Slack as they move.
  • Reviewer feedback captured with one-click reasons, to measure and improve useful-correction rate.

A note on writing to code repos

Writing docs to GitHub is opt-in per repo and off by default. When you turn it on you choose the target (a docs folder or the repo wiki) and whether changes are committed directly or opened as a pull request you review and merge. A repo with GitHub docs off is never written to, and code is never changed anywhere.

Have something you need? Tell us, real requests move items up this list.