The management system as a repository.
Your agent interviews for state and evidence and keeps the bookkeeping. Your people approve every change. The merge history is the audit trail. ISO 27001 or NIST-keyed, in the git you already run.
Illustrative example
Engineering-led companies keep everything else in git. Now the management system too.
Document kits are a commodity and SaaS GRC keeps your evidence in its database. A repository gives you review, history and ownership for free, and lets your own agent do the interviewing.
What is in it
Controls, gaps, decisions and the interview plan, one file each, with the responsible person named on every control. No standard text is ever stored: the standard is read through the licensed add-on, never copied.
How a change lands
The agent proposes in a pull request. A second model reviews it for standard text and consistency. The responsible person approves on the exact commit, enforced by the repository, and the merge is the record.
Illustrative example
We run our own on it.
Ansvar's ISO 27001 management system is this repository, operated by our own agent sessions. BSI assessed it at Stage 1 on 31 August 2026 and recorded one minor finding. Stage 2 is scheduled for October 2026.
Ten weeks, €6,000, credited when you convert.
Install
The template repository lands in your GitHub with the approval rules on. You buy the standard through the add-on for the people who read it.
First interview wave
Your agent asks the owners for state and evidence, control by control, and records what it learns as pull requests.
First gap register
Gaps land with owners and plans. The register is a merge, not a spreadsheet.
Decide
Convert to the annual contract and the pilot fee is credited in full. Up to four delivery days from us are inside the pilot.
ISO 27001 or NIST-keyed
With maintained mappings
Put the management system where the work is.
A paid pilot, fixed in scope, credited on conversion.