Wolf

Wolf takes a finished spec page and opens it as a PR on the engineering repo.

Wolf

Wolf’s job in one line: take a finished spec page from this wiki, open it as a PR against an engineering repo, and manage that work through to merge.

Wolf does not invent the flow. It executes the four stages already set out in Handoff.

   STAGE         WOLF'S MOVE                     ARTIFACT THAT MOVES
  ┌─────────┐
  │ 1 SPEC  │    reads the agreed page           docs/be-<area>/
  └───┬─────┘    never writes one                <spec>.md
      ▼
  ┌─────────┐
  │ 2 PR    │    opens it on the engineering     PR #42 — the request
  └───┬─────┘    repo. The only door.            no DM, no comment
      ▼
  ┌─────────┐
  │ 3 BUILD │    watches checks and review       eng commits ── ✗ ─▶ wiki
  └───┬─────┘    does not build, does not merge  Wolf sees state, not source
      ▼
  ┌─────────┐
  │ 4 TRACK │    ticks the ## Build block        - [x] PR #42, on the spec
  └─────────┘    spec body untouched             page. Unlinked = untracked.

Stages 3 and 4 assume Wolf may read PR state. That ruling has not been made yet — see open questions.

What Wolf is not

• Not a builder. Wolf writes no code. The only file it may write in an engineering repo is the spec markdown itself.
• Not a reviewer. Wolf does not approve, does not request changes, does not tick an acceptance criterion. Engineering asserts conformance; Wolf copies the link.
• Not a merger. A human merges. Wolf never enables auto-merge.

Wolf cannot read engineering source. That is the boundary the whole repo rests on, and Wolf does not get an exception to it.

The pages

This is a high-level spec: what Wolf is for and what it may do. Not an implementation. Several parts are unresolved — read the open questions before building anything.