SOP library
The living, versioned, freshness-aware procedure store for every workflow in your company.
Lifecycle
Every SOP moves through a defined lifecycle. Transitions are permissioned by role and recorded on the audit log.
| State | Description |
|---|---|
| draft | Extracted from a session and waiting for human review. Not visible in search by default. |
| review | Assigned to a Curator. Comments and edits are tracked per revision. |
| approved | Live and surfaced in search. Edits create new versions; the previous version is retained. |
| stale | An entity the SOP depends on has changed. Mnemos surfaces a side-by-side diff to the owner. |
| archived | Withdrawn from search. Retained for audit. Cannot be edited; can be cloned to a new draft. |
Versioning
Every approved edit creates a new immutable version. Versions are addressable individually, the SOP's root URI always points at the latest approved version. Citations from AI search resolve to the version that was live when the answer was generated, so historical answers remain explainable.
Freshness
Each SOP carries a freshness score driven by three signals:
- Dependency change — a referenced entity (system, person, policy) has been modified.
- Age — time since last human review, weighted by the project's review cadence.
- Contradiction — a newer session or integration event contradicts a claim in the SOP.
When freshness drops below the project threshold, the SOP enters the stale state and the owner receives a review task with a generated diff.
Review cadence
Curators can set review cadences per project (default 180 days for most projects, 60 days for compliance-tagged content). Cadences are enforced via scheduled review tasks; SOPs overdue by more than two cadences are surfaced in the workspace risk dashboard.
If you change the underlying transcript or document an SOP was extracted from, the SOP is not automatically rewritten — the original artifact is still the citation target. Always edit the SOP itself; the platform will record the divergence from source.