Living, not static

A knowledge base that maintains itself

Documents drift out of date the moment they’re written. Amnesia regenerates only the pages whose sources changed — using a hash manifest — so the knowledge base stays current without a full rewrite.

Overview

Self-updating

Static documentation is out of date almost as soon as it’s published. Amnesia keeps the knowledge base living: when a source document changes, a hash manifest lets it regenerate only the pages affected — so procedures stay current without anyone rewriting the whole base by hand.

What it does

Current without the rewrite

Regenerates only the pages whose sources changed.

A hash manifest tracks what actually changed.

The knowledge base maintains itself as sources evolve.

No full manual rewrite to stay current.

Changes are mirrored to a git-based audit trail.

How it works

How updates work

1Source documents change
2A hash manifest detects which sources changed
3Only the affected pages are regenerated
4The change is mirrored to the audit trail
FAQ

Common questions

Does the whole base rebuild on every change?

No. A hash manifest lets Amnesia regenerate only the pages whose sources actually changed.

How does it stay current?

It regenerates affected pages as source documents evolve, so procedures stay up to date without a manual rewrite.

Is there a record of changes?

Yes. Changes are mirrored to a git-based audit trail.

Explore more

More of what Amnesia does

Get started

See Amnesia turn your SOPs into a living knowledge base

Request a demo to see Amnesia turn your SOPs into a living, cited knowledge base your teams can trust under pressure.