Use cases · Amnesia

Onboard staff with a runbook wiki

Onboard staff with a runbook wiki with Amnesia: a practical, on-prem approach built for Azerbaijani teams.

Onboard Staff with a Source-Verified Runbook Wiki

Getting new hires up to speed is a critical yet time-consuming process that often drains the productivity of senior staff. Amnesia, developed by Allmaz, solves this by compiling your existing standard operating procedures (SOPs) into interlinked, browsable wiki pages. Instead of digging through scattered documents or relying on fragmented verbal instructions, your team can access a centralized knowledge base where every process is easy to find and navigate, ensuring that staff members have the right information at the exact moment they need it. Built specifically for organizations that prioritize data integrity and security, Amnesia operates on a strict 'no-invented-facts' rule. Every claim within the wiki is traced back to an approved source, eliminating the risk of hallucinations or inaccuracies. Designed for on-premises deployment, Amnesia provides Azerbaijani teams with a reliable, auditable, and fully controlled environment, turning static documentation into a living, trustworthy asset that supports operational excellence from day one.

Capabilities

The Advantages of Amnesia for Staff Onboarding

Accelerate autonomy for new hires through a structured, browsable wiki that reduces dependency on senior personnel.

Ensure absolute accuracy with source-traced claims, meaning staff only act on information verified by approved documents.

Maintain operational relevance via human-curated scope and structure, ensuring the wiki reflects your actual organizational workflows.

Simplify compliance and accountability with a git-mirrored audit trail that records every change with a full timestamped history.

Optimize system performance using hash-based regeneration, which only updates pages affected by source changes to maintain stability.

Guarantee data sovereignty through on-premises deployment, keeping sensitive operational procedures within your own infrastructure.

How Amnesia Transforms SOPs into a Living Wiki

Interlinked Wiki Pages

Amnesia compiles your standard operating procedures into connected, browsable wiki pages. Staff can follow links between related processes rather than reading documents in isolation.

Source-Traced Claims

Every statement on every page is tied to an approved source. If a claim cannot be traced to a verified document, it does not appear — a hard rule with no exceptions.

Human-Curated Structure

Your team defines the scope and organisation of the wiki. Amnesia builds within that structure, ensuring the result matches your operational reality rather than an automated guess.

Hash-Based Selective Regeneration

A hash manifest tracks source documents. When a source changes, only the affected pages are regenerated — leaving the rest of the wiki untouched and stable.

Git-Mirrored Audit Trail

All changes to the wiki are mirrored in a git repository, giving you a full, timestamped history of what changed, when, and why — ready for audits or rollbacks.

On-Premises Deployment

Amnesia runs within your own infrastructure, keeping operational procedures and staff data under your control without reliance on external cloud services.

From SOPs to a Ready Wiki in Clear Steps

1Your team defines the scope and structure of the wiki, deciding which procedures to include and how to organise them.
2Approved source documents — your existing SOPs and runbooks — are ingested as the sole basis for content.
3Amnesia compiles the source material into interlinked wiki pages, with every claim tied to its originating document.
4A hash manifest records the state of each source so the system knows exactly which pages need updating when documents change.
5Staff browse the wiki to find and follow procedures; the git-mirrored audit trail logs every change for accountability.
6When a source document is updated, only the pages that depend on it are regenerated, keeping the rest of the wiki stable.

Frequently Asked Questions About Amnesia

What happens if a procedure is not covered by an approved source document?

Amnesia will not generate content for it. The 'no-invented-facts' rule is absolute: if a claim cannot be traced back to a verified, approved source, it is excluded from the wiki to prevent inaccuracies.

How does the system handle updates to our existing SOPs?

The system uses a hash manifest to track every source document. When a document is updated, Amnesia identifies only the specific wiki pages that draw from that source and regenerates them, ensuring the rest of the wiki remains stable.

Can we control which procedures are included in the wiki?

Yes. The scope and structure are entirely human-curated. Your team decides exactly what information is included, how it is categorized, and what remains excluded from the knowledge base.

Where is the wiki data stored and how is it secured?

Amnesia is designed for on-premises deployment. This means all your SOPs, the generated wiki, and the associated metadata stay within your own secure infrastructure, removing reliance on external cloud providers.

How do we track changes for compliance or auditing purposes?

Every change made to the wiki is mirrored to a git repository. This provides a comprehensive, timestamped audit trail that allows you to see exactly what was changed, when it happened, and who was responsible.

Ready to Give Your Team a Runbook Wiki They Can Trust?

Talk to Allmaz about deploying Amnesia for your organisation. We will help you turn your existing SOPs into a structured, source-verified wiki that supports staff from their first day onward.

Request a demo