> **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, not as current documentation.

## Problem

The shared agentic workflow (PR#148) asks every werk repository for a plan as a Werkbaum file, updated by each PR.
Werkator has none.
Its history is spread over about 130 PR documents, the release notes, ADRs, RFCs and the rewrite plan.

## Non-Goals

- The PR documents, ADRs and RFCs stay the record; the plan points to them.

## Solution

- `docs/werkator.werkbaum` holds the plan: 16 themes and 197 nodes, from the rewrite plan of v0.9.0 to PR#150.
  Each node names the PRs, plan steps, ADRs or RFCs that built it, so the plan points to the record instead of repeating it.
- A merged node is `[^]`, because mih09 deploys every merge to `main` itself; vm4006 lags behind and is a node of its own.
- Open work comes from the "Follow-up PRs" and open questions of the PR documents, the open RFC steps and plan step 18.
  What a later PR already did is left out.
- 31 dropped approaches stand as `[-]` nodes; the block behind `---` gives each reason and where it was decided.
- Dependencies between open nodes use `:#id`, e.g. RFC 0006 step 5 on steps 3, 3b and 4.
  Two sizing rules wait for data, not for a node; their notes say so.
- PR#150 merged before this PR, so its node `#restart2` is `[^]` here.
- The file parses without warnings with the parser of the Werkbaum frontend (`parse` of `frontend/src/parser.js`).

## Follow-up PRs

- Each PR updates the plan: the status of its nodes, new plans and dropped approaches.