Almirah deliberately does not invent its own change management. It relies on git. Everything the framework manages — specifications, test protocols and runs, decision records, risk registers — is plain-text Markdown, and plain text is exactly what git was built to version. There is no proprietary database to protect, no change-request module to configure: the repository itself is the change-management system.
Because every document is a text file, every change is a commit: attributed, timestamped, diffable, and permanent. The questions an auditor asks — what changed, when, by whom, and why — are answered by the tools every developer already knows:
# full history of a specification
$ git log --oneline specifications/req/req.md
# exactly what changed in the requirements between two releases
$ git diff v1.2.0..v1.3.0 -- specifications/
# who introduced this requirement, and in which commit
$ git blame specifications/req/req.mdBaselines come free as well: a tag or a release branch freezes the entire document set — requirements, tests, decisions, and risks — as one consistent snapshot that can be rebuilt into HTML at any time.
Any git-based code review tool can be used to guarantee that changes in specifications, tests, decisions, and risks are reviewed and approved before they land. The flow is the one your team already uses for code:
$ git checkout -b update-alarm-requirements
# edit the specifications, protocols, or decision records ...
$ git add specifications/ && git commit -m "Clarify alarm limit requirements"
$ git push -u origin update-alarm-requirements
# open a pull / merge request — the review IS the change control boardBranch protection and mandatory reviewers turn your review policy into an enforced rule rather than a convention: nothing reaches the baseline unreviewed, and the approval itself is recorded — who approved, what exactly, and when. Markdown diffs read like prose, so a reviewer sees the changed requirement sentence, not an opaque export.
For changes that need more context than a commit message — a rationale, alternatives, affected documents — Almirah pairs git with decision records: the change request is itself a versioned Markdown file whose “Affected Documents” table links to the requirements it updates. The decision, the discussion, and the resulting document edits travel through the same review, and the traceability between them is rendered by Almirah.
Git is a distributed, open format with an ecosystem of hosting and review tools — use any of them, self-hosted or cloud. If a tool goes away, the full change history goes with you, because it lives in the repository, not in the tool.