The word is the product
Most startups treat vocabulary as branding. Pick the fun word. Ship the MVP. Argue about it later. That is fine for startups building products where the word does not shape behavior.
For Rhiz, the word shapes the product. A company that says 'network' in its copy ends up with a network. A company that says 'Connection' ends up with something else. The vocabulary is not downstream of the strategy. It is the strategy.
This article is the full argument for why Rhiz uses Connection as a noun and refuses to use 'network' in user-facing copy.
What 'network' trains users to do
'Network' is a word with decades of accumulated product meaning. When a user sees it, they reach for the behavior they have learned on the platforms that taught them the word.
- Follow counts.
- Mutual connection badges.
- 'Expand your network' prompts.
- Cold outreach framed as 'networking'.
- Broadcast-mode posts designed to reach maximum eyeballs.
None of this is neutral. Every one of these behaviors is a reach optimization. A user operating inside a 'network' frame is, by default, optimizing for reach. The product surface rewards it. The vocabulary reinforces it. The graph gets shaped by it.
If Rhiz used 'network', every surface would inherit the gravity. The front door would pull users toward reach metrics. The coordination surfaces would reward broadcast. The 'Connection' button would, over time, evolve into a follow button. This is not paranoia. It is pattern matching on what has happened to every platform that used the word.
What 'Connection' trains users to do
'Connection' is a specific word with a different shape. When a user sees 'Connection' in Rhiz copy, what is being implied is:
- A specific, named relationship with another member.
- Formed inside a cohort, not across a broadcast.
- Consented, verified, and recorded as protocol events.
- Carrying context the user can actually read.
The user's default behavior inside this frame is different. They do not try to maximize the number. They try to sharpen the existing ones. They reach out to specific people for specific reasons. They read the cohort context before they act.
This is not because users are better. It is because the word is different, and the product surface is different, and the metrics behind the surface are different. The vocabulary does half the work.
Structural Sync replaces networking
The verb form matters too. 'Networking' as a verb is the same reach-optimized behavior dressed in action language. A user 'networking' at an event is trying to meet as many people as possible, get business cards, follow up in bulk.
'Structural Sync' is what Rhiz uses instead. Structural Sync is coordinating on structure. What someone is working on, at what pace, under what constraints, and how that overlaps with what you are working on. It is the high-context, low-volume version of the interaction. You cannot Structural Sync with fifty people in an evening. That is the point.
Every surface that would say 'networking event' says 'coordination' or 'cohort gathering'. Every surface that would say 'grow your network' says 'deepen your Connections'. The language is internally consistent.
Why the discipline matters
If only half the team uses the vocabulary, drift happens fast. One marketing page says 'network'. One product tooltip says 'connect with your network'. One onboarding email says 'expand your professional network'. A user reads three surfaces and the vocabulary is incoherent.
Worse, the vocabulary drift carries product drift with it. The team that used 'network' on the landing page starts thinking of the product in network terms, and within a quarter the graph ranking is reach-optimized, because the word did its job.
This is why Rhiz enforces the vocabulary as a non-negotiable at every layer. Not because 'Connection' is nicer-sounding. Because 'network' carries fifteen years of reach-shaped product residue and will eat the product from the inside if you let it.
What a Connection actually is
A Connection in Rhiz is a specific relationship formed in a specific cohort under specific consented terms. It has:
- Two principals, both cohort-rooted.
- Formation context, including the cohort and the moment.
- Consent events recording what each side agreed to.
- Visibility into shared trajectory, where each principal has consented to share it.
That is very different from a follow, a mutual connection, or a contact. It is closer to what 'professional relationship' meant in the pre-platform era, except the terms are recorded, enforceable, and machine-readable.
What this gives agents
Agents acting on behalf of Rhiz members read Connections, not networks. When an agent decides whether to forward a message, schedule a meeting, or surface an introduction, it reads the Connection metadata: who was this Connection formed with, in what cohort, under what consent, with what history.
A reach-based graph could not give an agent any of that. The Connection vocabulary and the Connection structure go together.
Where to go next
- Read the cohort-based Connection hub.
- Read the protocol design hub for what the Connection primitive actually is.
- Begin a Voice Awareness Session, where your Connection graph starts.
The word is the product. Pick the right word and the product follows.