Create a network
The one workflow the source PRD describes without hedging. Everything here is deliberately thin: a network with a single member does nothing, so the screen after creation is about invitation, not browsing.
Depends on the naming decision. If the trading reading is not chosen, this screen does not get built — the
existing event-scoped setup flow already covers convening.
Network details
Name and description are visible to anyone who can see the network exists.
The PRD lists “other fields (TBD)” here. Category, region and member cap are the
obvious candidates, but none are specified — left out rather than invented.
Who can see this network
New networks default to Private. Tightening is always allowed; loosening notifies every member.
Loosening from Secret is a confirmed, notified act because it changes who knows the network
exists at all — not merely who can join.
Cascade Regional Parts Co-op
The post-create state appears here. It is built around a single call to action.
Why the empty state carries the screen
- Invitation is the only action that changes the network's value.
- Browsing, search and settings are all noise until a second member exists.
- The secondary action — setting a sharing policy — is the other half of being useful, and defaults to sharing nothing.
Illustrative placeholder data, in-memory state.