Sheet 1 showed you what you own. This sheet shows you how the work actually moves: what goes in, where it is held, and who signs off. Read it like a set of process drawings.
Three stages. Nothing moves past the third one without a person saying yes.
The drawing stops at the checkpoint on purpose. Everything up to that point is running today. What happens after a yes depends on the channel, and we will draw that sheet once it is genuinely running rather than promise it here.
A project is a folder that holds a set of chats plus the knowledge behind them. There are exactly two kinds. This is the piece worth reading twice.
The thing everybody gets wrong: putting a project in the shared column does not publish your conversations.
Chats inside a project are private by default, even a shared one. Your teammates see the project's knowledge and instructions, not what you typed. A specific chat becomes visible only when the person who owns it chooses to share it.
One rule of thumb. If getting it wrong would only cost you an afternoon, keep it private. If getting it wrong would cost the company, it belongs in the shared project where it can be reviewed.
Knowledge gets in three ways. All three land in the same place, so the answer is the same no matter who asks or where they ask it.
Nothing here rewrites itself invisibly. Every change is dated and can be read back or rolled back.
The questions that came up on our call, answered in one line each.