Renames the user-facing product name Certifai → Prüfwerk in the documentation only.
Scope of this PR (safe layer)
docs/** prose, the VitePress title / name / footer message, the glossary, guides, and reference pages. 15 files, brand text only.
Deliberately NOT in this PR (infra-coupled — needs a coordinated migration)
Renaming these in code without renaming the matching live resource in lockstep would break auth/provisioning/deploys (cf. the tramiton→firmwerk breakage):
Renames the user-facing product name **Certifai → Prüfwerk** in the documentation only.
## Scope of this PR (safe layer)
- `docs/**` prose, the VitePress `title` / `name` / footer message, the glossary, guides, and reference pages. 15 files, brand text only.
## Deliberately NOT in this PR (infra-coupled — needs a coordinated migration)
Renaming these in code without renaming the matching live resource in lockstep would break auth/provisioning/deploys (cf. the tramiton→firmwerk breakage):
- Docker network `certifai` (PLC provisioning), Keycloak realm/client `certifai` / `certifai-dashboard` (auth), Harbor image project `repo.breakpilot.com/certifai/*` (deploys)
- The `compliance-*` crate package names and the `compliance-scanner-agent` repo itself
- The `Certifai SPS Approach` collective folder + `certifai-requirements.md` filename
These are tracked for a separate decision (brand vs full identifier rename, incl. the ASCII spelling `pruefwerk` for identifiers).
The Nextcloud Collectives pages (requirements, CRA coverage, EMB3D design, Readme) were rebranded to Prüfwerk in the same pass.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01EgxGHn22YEfQz5fLHSHkLv
The product is renamed Certifai -> Prüfwerk. This changes only the user-facing
brand text in the documentation (docs/**, VitePress title/name). It does NOT
touch functional identifiers that happen to contain "certifai" (the Docker
network, Keycloak realm/client, Harbor image project, the compliance-* crate
names, or the repo name) — those are infra-coupled and need a separate,
coordinated migration.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EgxGHn22YEfQz5fLHSHkLv
sharang
merged commit 710fdcab6f into main2026-09-02 08:00:13 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Renames the user-facing product name Certifai → Prüfwerk in the documentation only.
Scope of this PR (safe layer)
docs/**prose, the VitePresstitle/name/ footer message, the glossary, guides, and reference pages. 15 files, brand text only.Deliberately NOT in this PR (infra-coupled — needs a coordinated migration)
Renaming these in code without renaming the matching live resource in lockstep would break auth/provisioning/deploys (cf. the tramiton→firmwerk breakage):
certifai(PLC provisioning), Keycloak realm/clientcertifai/certifai-dashboard(auth), Harbor image projectrepo.breakpilot.com/certifai/*(deploys)compliance-*crate package names and thecompliance-scanner-agentrepo itselfCertifai SPS Approachcollective folder +certifai-requirements.mdfilenameThese are tracked for a separate decision (brand vs full identifier rename, incl. the ASCII spelling
pruefwerkfor identifiers).The Nextcloud Collectives pages (requirements, CRA coverage, EMB3D design, Readme) were rebranded to Prüfwerk in the same pass.
🤖 Generated with Claude Code
https://claude.ai/code/session_01EgxGHn22YEfQz5fLHSHkLv