# PR#110: werkrevisor Reviews werkkompass

> **WARNING:** This document describes only the change applied in this PR.
> It may already be outdated once the next PR is merged.
> Historic PR documentation is not maintained along with new PRs; treat it as a snapshot.

## Related Links

- [werkkompass PR#1](https://git.javagil.de/mi/werkkompass/pulls/1): the project foundation, the first PR to review.

## Problem

werkkompass, the interactive demo on Vibe Coding, Vibe Engineering and Agentic AI, is a new repository of the Werk family.
It follows the shared workflow, but werkrevisor has no host config for it, so its PRs get no review.

## Non-Goals

- No Werkator build of werkkompass besides `ai-review`; the human decided to add its CI later.
- No branch protection and no machine config on mih09; the human sets them up.

## Solution

- `config/werkkompass.toml` is the host config for `mi/werkkompass`, derived from that of werkregie,
  with `require_wip_transition` and `automerge`.
- Its categories fit one static `index.html`; `src/**` and `tests/**` stand for the planned build step.
- Judged paths are the CI and build files, including `scripts/**` and an npm manifest, should one come.
- The PR documents live in `docs/prs/`, in English.
- The review instructions describe werkkompass and point to the invariants of the content in its `AGENTS.md`.
- `docs/betrieb-git.javagil.de.md` counts seven repositories and deploys the rootfs to werkkompass too.
- The tests of the example configs include it.
- Version 0.42.3.

After the merge, the human sets up on Gitea and mih09:

1. `ai-reviewer` as collaborator with write access in `mi/werkkompass`.
2. The machine config `~/werkkompass/.git/werkator/.werkator.yml` on mih09 with the build `ai-review`,
   its secrets and `config/werkkompass.toml` as `WERKREVISOR_CONFIG_TOML`.
3. The branch protection of `main` with `tools/branch-protection`, contexts `ai-review/gate`, approvers `ai-reviewer,mi`.

## Open Questions

None.