Keep your SOPs always up to date
Keep your SOPs always up to date with Amnesia: a practical, on-prem approach built for Azerbaijani teams.
Maintain Living, Source-Grounded SOPs
Standard operating procedures often become obsolete the moment they are finalized, leading to operational drift and costly errors. Amnesia, developed by Allmaz, eliminates this decay by transforming your approved source documents into a network of interlinked, browsable wiki pages. By treating your authoritative documents as the single source of truth, Amnesia ensures that your team always accesses procedures grounded in verified information, removing the risk of outdated or misinterpreted guidance. To maintain maximum efficiency and accuracy, Amnesia employs a strict 'no source, no claim' architecture. This hard constraint prevents the introduction of invented facts or hallucinations, ensuring that every statement in your wiki traces back to a validated document. Furthermore, the system utilizes a hash manifest to track source states, regenerating only the specific pages affected by a change. This targeted update process keeps your knowledge base current without the need for manual overhauls or full-system rebuilds.
Why Teams Trust Amnesia for SOP Management
Automated Currency: Only pages tied to modified sources are regenerated, ensuring procedures stay current without manual effort.
Absolute Traceability: Every claim is linked directly to an approved source document, eliminating guesswork and unverified content.
Zero-Hallucination Guarantee: A strict no-invented-facts rule ensures that no information appears in the wiki unless it is explicitly backed by a source.
Human-Centric Control: Human-curated scope and structure ensure the knowledge base is organized around your actual operational workflows.
Transparent Compliance: A git-mirrored audit trail provides a complete, timestamped history of every change for seamless auditing.
Seamless Navigation: Interlinked wiki pages allow team members to move between related procedures while maintaining full operational context.
Engineering Reliability into Your SOPs
Source-Grounded Wiki Pages
Amnesia compiles your SOPs into interlinked, browsable wiki pages where every claim points back to an approved source document. If a source does not exist, the claim does not appear — full stop.
Hash-Manifest Selective Regeneration
A hash manifest tracks the state of every source file. When a source changes, only the pages that depend on it are regenerated, keeping updates fast and targeted without touching unaffected content.
No-Invented-Facts Rule
Amnesia enforces a strict policy: no source, no claim. This hard constraint prevents hallucinated or outdated information from ever reaching your team's procedures.
Human-Curated Scope and Structure
Your team defines which sources are approved and how the wiki is organized. Amnesia works within that human-set structure, ensuring the output reflects deliberate editorial decisions rather than automated guesswork.
Git-Mirrored Audit Trail
Every change to your SOP wiki is mirrored in a git repository, giving compliance teams, managers, and auditors a transparent, timestamped record of what changed, when, and why.
On-Premises Deployment
Amnesia is built to run on your own infrastructure, keeping sensitive operational knowledge inside your environment and under your control.
From Approved Sources to a Living Wiki
Frequently Asked Questions
What happens if a source document is removed or revoked?
Because every claim must trace back to an approved source, removing or revoking a source causes the claims that depended on it to be flagged or removed during the next regeneration cycle. Nothing unsupported remains in the wiki.
Does Amnesia regenerate the entire wiki every time something changes?
No. Amnesia uses a hash manifest to identify exactly which source files have changed and regenerates only the wiki pages that depend on those files, leaving unaffected pages untouched.
Who controls which documents are treated as approved sources?
Your team does. Amnesia operates within a human-curated scope, meaning people in your organization decide which documents are authoritative before any content is compiled.
How does the audit trail work for compliance purposes?
Every change to the SOP wiki is mirrored to a git repository. This provides a timestamped, diff-level history of all updates, which is essential for compliance reviews, onboarding, and resolving version disputes.
Can Amnesia be deployed in secure or air-gapped environments?
Yes. Amnesia is designed for on-premises deployment, ensuring that your source documents and compiled wiki pages remain entirely within your own infrastructure.
Eliminate Outdated Procedures Today
Talk to the Allmaz team about deploying Amnesia for your organization and see how source-grounded, automatically maintained SOPs can reduce the overhead of keeping your team's knowledge current.
Request a demo