The holy grail

The two workflows this company has written down, and where they collide.

Two workflows exist on paper. They are not the same workflow. A is a pipeline — it routes an idea through stages until it converges. B is an org chart — it routes a request through people until someone owns it.

A — the wiki’s workflow

   ssh dev-box ⚠  ──►  ~  ──►  claude
                                 │   "idea about zoom transcripts"
                                 ▼
                       be wiki new zoom-etl              ⚠ be-cli
                                 │
                                 ▼
                    ~/be-wiki-zoom-etl          ⚠ be-wiki-template
                    its own repo · /dump /interview /brief
                                 │
              teammates pull ────┤────► readers file question-*.md
                                 │
                                 ▼
                           C O N V E R G E
                    no open questions · briefs match
                                 │  graduate
                                 ▼
        be-internal/docs/be-<type>-<name>/    ◄── LIVE. push = deploy
                                 │
                                 ▼   spec:  draft ──► ready
                            [ W O L F ]   courier · writes no code
                                 │
                                 ▼
                   PR on engineering repo   ◄── "the only door"
                                 │
                                 ▼
              eng builds ──► ## Build ticked on the spec page

 ⚠ = documented in the present tense · does not exist in the org

Source: how does it work, the entry point, handoff.

B — the planning docs’ workflow

                              Ryan
                                │
                                ▼
                         ┌────────────┐
                         │   HERMES   │  no GitHub · no cloud · no keys
                         └─────┬──────┘  delegates, never touches
                               │
      ┌────────┬──────────┬────┴─────┬──────────┬──────────┐
      ▼        ▼          ▼          ▼          ▼          ▼
     Mia     Jules     Vincent     WOLF       Butch    Marcellus
   social   accounts   VP prod     CTO         FDE        ops
                                    │           ▲
                     spins up own   │           │
                     sub-agents ────┤           │
                                    ▼           │
                                SPEC.md ────────┘  hands off
                                    │       Butch builds (v0)
                                    ▼
                            Linear issue  ⚠ unwired · key pending
                                    │
                                    ▼
                              Vercel deploy

Source: the be-internal-planning archive — charter and user-flow docs, written 2026-08-29. Not in this repo.

Where they collide

Stage	A says	B says	Verdict
Entry	`ssh`, type `claude`	talk to Hermes	open
Roster	5 agents by task	6 people by function	open
Wolf	courier, no code	CTO who builds	open
Tracker	GitHub issue	Linear	A — Linear unwired
Target	`be-internal`, live	`be-internal-wiki`, new	A — it exists
Stack	Astro, static	Next.js, RSC, Neon	A — verified

Nothing yet says which one a person follows on Monday. Until that is decided, A is the one that runs.