The change loop
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.
A worked agent change
- 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.
- 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.
- 03
Open PR
Fill the PR template — document IDs affected, summary, impact assessment, training implications. This is the change record per PP.405.PROC.
- 04
CI runs
validate.yml checks structure on the PR branch. Failures block merge. Agent retries or escalates.
- 05
Human review
CODEOWNERS — QA/RA designate + CTO — read the PR, approve or request changes. Agent cannot self-merge.
- 06
Merge
Approved PR fast-forwards to main. The PR page becomes the permanent change record.
- 07
Publish ≤5 min
VPS systemd timer pulls, diffs against the current manifest, atomically swaps the bundle.
- 08
Visible to staff
Footer on qms.modelmatic.eu shows the new commit SHA. No staff action needed.
Why this is agent-ready today
| Component | Why it matters for agents |
|---|---|
| Markdown + ID conventions | Agents can parse and index without bespoke schema. <Area>.<Group>.<TYPE> · e.g. PP.405.PROC. |
| manifest.json | One generated catalogue an agent reads to discover the corpus. The sync keeps it honest. |
| PR template with PP.405.PROC fields | Forces agents to produce structured change records — not free-text commits. |
| CODEOWNERS | Hard guardrail. Agents propose; humans approve. Always. |
| Atomic publish via manifest | Agents can read manifest.json and reason about exactly which commit is live. |
| validate.yml as first CI agent | Phase 4 extends this: terminology, dead-link, cross-reference checks. |
Deliberately not built yet
- No agent runtime is wired in — There is no document-controller skill making PRs today. The infrastructure is ready; the agent is Phase 4.
- No auto-merge — Every change goes through human review until a specific class of low-risk changes is identified and gated separately.
- No semantic CI — validate.yml checks structure only. Terminology, dead links, cross-reference consistency come next.
- No signed approval records — PR history is the audit trail today. Production needs records/approvals/*.pdf alongside.