1.2 KiB
1.2 KiB
PR#52: the plan of werkrevisor as a Werkbaum in the repository
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.
The Problem
The plan of werkrevisor is spread over PR documents, the design of 2026-10-08 and session notes. Dropped approaches, e.g. the finding benchmarks, are known only to those who were there. Nobody sees at a glance what is live, what is merged but unused, and what comes next.
Non-Goals
- No change of the code or the configs.
- No history of every PR: a node names its PRs only where they explain it.
The Solution
- docs/werkrevisor.werkbaum holds the plan in Werkbaum notation, from the gate to the planned overall verdict. It shows the status of each part, the dropped approaches with their reasons, and the planned work.
- New in the plan: a risk category whether a change is reversible, or whether a bug can corrupt data. Its block records the research on the number of questions per Jev request.
- AGENTS.md: each PR updates the Werkbaum.
Prerequisite PRs
- PR#51: werkrevisor 0.24.0, merged.