An alternative to SOPs on a shared drive
An alternative to SOPs on a shared drive: a local, on-prem alternative for Azerbaijani business — see how Amnesia compares.
Beyond the Shared Drive: A Trusted Home for Your SOPs
Most organizations rely on shared drives to store their standard operating procedures, resulting in a fragmented landscape of stale files and contradictory instructions. These nested folders often hide critical information and offer no mechanism to verify where a specific instruction originated, leaving teams to guess which version of a document is the current gold standard. This lack of traceability creates operational risk and erodes confidence in the company's internal knowledge. Amnesia, by Allmaz, transforms this chaos into a structured, interlinked wiki where every claim is anchored in truth. By compiling approved source documents into a browsable knowledge base, Amnesia enforces a strict 'no-invented-facts' rule, ensuring that no statement exists without a verified source. With a git-mirrored audit trail and a hash-manifest system for precise updates, Amnesia provides a living, human-curated repository that your team can trust implicitly.
The Advantages of a Verified Knowledge Base
Absolute Traceability: Every page and claim links directly back to an approved source, eliminating unsourced assumptions.
Intuitive Navigation: Replace tedious folder hunting with an interlinked wiki structure for seamless browsing of related procedures.
Efficient Updates: A hash-manifest system ensures only pages with changed sources are regenerated, preventing unnecessary wholesale rewrites.
Compliance-Ready Auditing: A git-mirrored trail provides a timestamped record of every change, satisfying strict internal and external governance needs.
Intentional Organization: Human-curated scope and structure ensure the knowledge base reflects deliberate business decisions rather than automated noise.
Data Sovereignty: Local and on-premises deployment keeps sensitive business intelligence entirely within your own secure infrastructure.
Core Capabilities of Amnesia
Interlinked Wiki Pages
SOPs are compiled into browsable, cross-referenced wiki pages so staff can navigate related procedures without leaving the knowledge base.
Hard No-Invented-Facts Rule
No source, no claim. Every statement on every page must trace back to an approved source document. If the source does not exist, the claim does not appear.
Hash-Manifest Regeneration
Amnesia tracks a hash manifest of your source files. Only pages whose sources have actually changed are regenerated, so updates are precise and auditable.
Git-Mirrored Audit Trail
Every edit is mirrored to a git repository, giving you a full, timestamped history of changes that satisfies internal governance and external audit requirements.
Human-Curated Structure
Scope and page hierarchy are defined by your team, not inferred automatically. The knowledge base reflects deliberate editorial decisions from the people who know your business.
Local and On-Premises Deployment
Amnesia is built for Azerbaijani businesses that need their data to stay on their own infrastructure — no third-party cloud required.
From Source Documents to Trusted Wiki
Frequently Asked Questions
What happens if a source document is removed or updated?
Amnesia utilizes a hash manifest to detect changes instantly. Any pages relying on a removed or updated source are flagged for review and are only regenerated once the new or replacement source is approved.
Can Amnesia invent or infer information not found in our sources?
No. The 'no-invented-facts' rule is a hard constraint. If a claim cannot be traced directly to an approved source document, it is prohibited from appearing in the wiki.
Does our sensitive data leave our internal infrastructure?
No. Amnesia is specifically designed for local or on-premises deployment, ensuring that all documents and generated wiki pages remain within your own controlled environment.
Who determines how the wiki is organized?
Your team maintains full control. The scope and hierarchy are human-curated, meaning the organization of your knowledge base is a result of deliberate editorial choices rather than automated guesses.
How is the audit trail managed for compliance?
Every modification is mirrored to a git repository. This provides a permanent, timestamped history showing exactly what changed, which source triggered the update, and when the change occurred.
Replace Your Shared Drive With a Knowledge Base You Can Trust
Talk to the Allmaz team about deploying Amnesia in your organisation — on your infrastructure, on your terms.
Request a demo