| name | docs-update |
| description | Keep the charter's documents, status labels, README index, and CHANGELOG in sync after adding, editing, promoting, or retiring a Markdown document in this repo. Use after any non-trivial change to a document. |
/docs-update — keep the document set coherent
A small, repeatable pass to run after you change a document, so the repository stays internally consistent. This repo is documents-only: "done" means the prose and its surrounding index, labels, and change log all agree.
When to use
After you add, rename, substantially edit, promote (e.g. DRAFT → PUBLISHED), or retire any .md document under docs/.
Procedure
- Status banner. A top-of-file status banner — a plain
> **Status: …** blockquote (not a typed callout) — belongs on the normative docs (Charter Commitments, evaluation protocol, certification model, one-pager) and the outreach/parliamentary drafts (Non-Paper, Aktionsplan, Postulat), labelled DRAFT; on PUBLISHED <date> pages; and on the docs/wip/ notes, labelled WORKING NOTES — see AGENTS.md. If the doc is one of those, confirm its banner is present and accurate; otherwise (briefings, evidence, strategy, background) it carries no banner. The README index notes each document's status either way.
- README index. Open the README. It presents Our AI Charter / the Public AI Network (this whole effort) — its overview, AI-infrastructure pillar, published articles, and the strategy/outreach/evidence — with AI Assurance & Certification as the trust-and-evidence building block, each document's status labelled inline. Move or add the document to the right section with a one-line description that matches its current framing. Remove stale entries.
- Cross-links. Check that links between documents (and from the README) resolve — relative paths and correct filenames. Fix anything a rename broke.
- CHANGELOG. Add a dated entry (ISO
YYYY-MM-DD) in the CHANGELOG: what changed and, for the protocol/charter, the version bump. Keep entries terse and factual.
- Public-repo check. Confirm nothing private/internal or any secret was introduced — this is a public repo (see AGENTS.md).
- Commit. Use a conventional commit, e.g.
docs(protocol): tighten the support rubric or docs: promote charter-commitments to published.
Output
A short summary: which document changed, its label before/after, the index/changelog edits made, and any broken links found and fixed.
