Hub / Guides / Build vs go-to-market

Public lane

When not to post

Yes. Keep the build lane and the go-to-market lane on different gates. Code can ship on a recorded review while public posts stay on hold until the human owner gives an explicit go. Mark each ticket build or public, and do not treat a merge as an announcement. On this plant that go has not been given.

Why is a green build a bad time to post?

The build is green and somebody posts. The post is a different product from the merge. It has a different audience, a different owner, and a different definition of done. Multi-agent teams leak announcements from the same channel that merges code. Launch copy gets ahead of the receipt, and the public record describes a go that nobody called.

How do the build lane and the public lane stay apart?

Keep two lanes. They can share a company and a week. They do not share a gate.

Build lane

Implement, review, merge, deploy. The gate is a recorded PASS plus the release floor in the release guide. The thing you can see is the ticket: owner, stage, and the receipt. A coordinator does not deploy, publish, or spend. The shipping role merges after review. The reviewer does not merge.

Go-to-market lane

Posts, listings, and launch language. The gate is an explicit go from the human owner for that item. The coordinator may draft the public brief and run a plain-language read so someone outside the team can follow it. Specialists, when you staff them, handle posts, listings, and audio. They still wait for the go. A draft is not armed. An advance request is not a public post. Exact public copy ships only as an armed order that names its own gates.

The fleet runs on one plane and one queue. Two lanes sit on that plane. The build lane merges code. The public lane sends posts only after GO. A pass on the build lane leaves public posts on hold. What AI fleet ops means puts public claims after the gate passes.

Public posts wait until the owner says go. We mark that moment after GO. Until then the public lane stays on hold. On this plant the go has not been given. This manual is the operating text for the consulting practice. It does not announce a public launch. The short name is in the glossary.

How do you keep a post from shipping early?

  1. Mark every ticket build or public when you open it. A public ticket needs the owner's go before anyone posts.
  2. Write the public voice in the house file: which account, how often, and how replies sound.
  3. Let the coordinator draft and run the plain-language read. Internal shorthand fails that read. Fix the words before they are armed.
  4. Store exact public copy as an armed order with its gates. Leave drafts labeled as drafts. An advance request stays on the build ticket.
  5. Ship the code on its release gates. Leave the post unsent while the public lane is on hold.
  6. On this plant, do not describe a go that has not been given. If you need the lane opened, that is a consult with the owner, not a sentence in a pull request.

Where do the lanes get mixed?

How do you request a consult?

Bring the queue you have, the role list, and what should ship next week. A consult maps the gaps and the first gate.

Request a consult

What else do operators ask?

What is the difference between the build lane and the go-to-market lane?

The build lane merges and deploys code under release gates. The go-to-market lane publishes posts, listings, and launch copy. A pass on the build lane leaves the public lane closed.

When are we allowed to post?

When the human owner gives an explicit go for that public item. Until then the lane stays on hold. A draft, a ticket comment, or a review pass is not that go.

Who writes public copy, and who sends it?

The coordinator can draft the brief for a public item and run a plain-language read. The post still waits for the owner's go. Specialists, when you have them, handle posts, listings, and audio inside that go.

Why keep the lanes apart?

A demo that works is a build fact. A public claim is a different fact, with a different owner and a different gate. The receipt has to exist before the claim does.

Is this website a launch announcement?

This site is the operating manual for the consulting practice. The go-to-market lane for this plant is on hold.