QMS · How it works

How a QMS change reaches staff

The publish loop for jaspermodelmatic/mm-qms-plugin — the audit-able path between an editor opening a pull request and Modelmatic staff seeing the updated effective document. Click any step to see what runs.

01

The change loop

passfail → PR redAuthor opens PRGHA validate.ymlfilename + wiki-link conventionspass?PR blockedfix · re-pushCODEOWNERS approve + mergeQA/RA · CTOqms-sync.timer pulls mainevery 5 min · scoped deploy keyAtomic publishmanifest.json · mv swapLive · footer shows new SHA
process stepdecisionsuccessfailure
02

Same loop, human or agent

Everything past the PR is identical. The branch and pull request is the universal entry point — the pipeline doesn’t know whether git push came from a developer’s laptop or from an agent runtime. That is the point of the GitOps pattern.

The guardrails sit in CODEOWNERS (humans approve every change) and validate.yml (CI rejects malformed structure). Both apply equally to both kinds of author.

03

A worked agent change

  1. 01

    Trigger

    A Slack mention, a scheduled review, a finding from another agent, an audit observation. The agent gets a task with a document ID and a rationale.

  2. 02

    Branch + edit

    Clone, branch (e.g. agent/document-controller/2026-05-29), edit one or more controlled documents (e.g. PP.405.PROC), commit with the agent’s identity in the message.

  3. 03

    Open PR

    Fill the PR template — document IDs affected, summary, impact assessment, training implications. This is the change record per PP.405.PROC.

  4. 04

    CI runs

    validate.yml checks structure on the PR branch. Failures block merge. Agent retries or escalates.

  5. 05

    Human review

    CODEOWNERS — QA/RA designate + CTO — read the PR, approve or request changes. Agent cannot self-merge.

  6. 06

    Merge

    Approved PR fast-forwards to main. The PR page becomes the permanent change record.

  7. 07

    Publish ≤5 min

    VPS systemd timer pulls, diffs against the current manifest, atomically swaps the bundle.

  8. 08

    Visible to staff

    Footer on qms.modelmatic.eu shows the new commit SHA. No staff action needed.

04

Why this is agent-ready today

ComponentWhy it matters for agents
Markdown + ID conventionsAgents can parse and index without bespoke schema. <Area>.<Group>.<TYPE> · e.g. PP.405.PROC.
manifest.jsonOne generated catalogue an agent reads to discover the corpus. The sync keeps it honest.
PR template with PP.405.PROC fieldsForces agents to produce structured change records — not free-text commits.
CODEOWNERSHard guardrail. Agents propose; humans approve. Always.
Atomic publish via manifestAgents can read manifest.json and reason about exactly which commit is live.
validate.yml as first CI agentPhase 4 extends this: terminology, dead-link, cross-reference checks.
05

Deliberately not built yet