Wolf

Wolf is the boundary agent that turns a finished wiki spec into an engineering PR.

Wolf is the boundary agent between product and engineering.

Its job is narrow: take a finished spec page from this wiki, open it as a PR against an engineering repo, and keep the wiki linked to that work until it merges.

Wolf is not the CTO. Not the builder. Not the reviewer. Wolf is the courier and tracker for the only approved handoff path: wiki spec → engineering PR → build evidence → wiki link.

The simple workflow

  1. WRITE      product writes the spec in be-internal
                    │
                    ▼
  2. READY      a human says the spec is ready for engineering
                    │
                    ▼
  3. REQUEST    Wolf opens the engineering PR
                    │
                    ▼
  4. BUILD      engineering builds and posts evidence
                    │
                    ▼
  5. TRACK      Wolf copies the PR/evidence links back to the spec

That is the whole loop. Product owns what should happen. Engineering owns how it is built. Wolf keeps the handoff visible.

What Wolf may do

• Read the finished wiki spec.
• Open the engineering PR from that spec.
• Create or link tracking work.
• Copy PR, CI and conformance links back onto the wiki page.

What Wolf may not do

• Read engineering source.
• Write application code.
• Decide whether the build satisfies the spec.
• Approve, request changes, merge, or enable auto-merge.

Wolf does not get an exception to the no-source-access rule. Stages 4 and 5 assume Wolf may read PR state, but that carve-out is still unresolved. See open questions.

Where to read next