The front door to Rhiz is a conversation
Most product onboarding is a series of typed questions. Name, email, role, goal, interests. Pick a plan. Pick a color. The design optimizes for speed.
Rhiz onboards differently. The front door is a Voice Awareness Session, a roughly seventeen minute voice-first reflection. The output is a Prescient Report, a markdown-first personal profile that anchors the member inside the Rhiz graph. Everything downstream, the cohort rhythm, the Connections, the coordination, is calibrated against that Report.
The design decision to front-load a voice session is deliberate. Here is why.
Why voice
Voice captures things text does not:
- Sequencing. The order a person brings things up in voice is closer to the order those things actually live in their head. Typed forms scramble that sequencing.
- Emphasis. Which words someone stresses, where they slow down, where they speed up. All of this is signal.
- Hesitation. The places a person hesitates in voice often mark the places they are thinking hardest. Written text deletes hesitation.
- Self-editing reduction. When people type, they edit as they go. The final text is two or three revisions removed from what they actually think. Voice closes that gap.
For an onboarding that is supposed to capture who a member is, unfiltered signal is load-bearing. Text filters. Voice preserves. That is the entire argument.
What the seventeen minutes look like
The Voice Awareness Session has roughly four movements. Exact phrasing and ordering adapt to the member, but the structure is consistent.
- Orientation. What are you moving toward, in your own words. Not a job title. Not a goal sheet. How you describe the thing when nobody is listening.
- Friction. What is slowing you. What you are moving away from. Why the status quo does not hold.
- Rhythm. What a working week actually looks like right now, and what a working week would look like if you were coordinated with other people who understood what you are doing.
- Signal. Short response prompts that surface what you notice, what you are good at, and what has historically been underpriced in your life.
The session is voice-to-markdown, not voice-to-score. Nothing is being graded.
The Prescient Report
The Prescient Report is the output. It is markdown, not a dashboard. A few hundred words of structured prose that describe:
- Who you are, in language that sounds like you.
- What you are moving toward.
- What you are moving away from.
- The cohort context you are entering with.
- The edges of your current Connection graph, as they exist at onboarding.
The Report is readable by humans and by the agents acting on your behalf. That dual readability is important. The same artifact that a fellow cohort member reads to understand you is the artifact your agent reads to represent you. That is the kind of continuity markdown-first storage gives you.
The Report is not static. It updates as the member updates it. The first Report is the starting position, not the final one.
How the Report shapes everything downstream
Once the Report exists, everything downstream calibrates against it:
- Cohort rhythm. Weekly reflection prompts and coordination asks reference your Report context.
- Connections. The Connections you form inside the Collective are cohort-rooted, verified, and carry Report context from day one.
- Agent representation. Agents that act on your behalf inside Rhiz read the Report as their principal-signal source.
- Compounding context. Over the 77 day arc, the Report grows with you, so later Connections and later coordination start from a richer baseline than the first ones did.
Without the Report, everything downstream would have to rebuild context interaction by interaction. That is the Misalignment Tax that open networks impose. The Report is how Rhiz sidesteps it at onboarding.
Privacy
Voice data from a Voice Awareness Session is used to generate your Prescient Report. It is not used to train external models. Consent is recorded as a first-class event in Rhiz Protocol, so the member can see, revoke, and renegotiate the terms under which their voice data is stored.
This is not a marketing position. It is an architectural one. Rhiz Protocol was designed with consent as a load-bearing primitive, which means the privacy posture is enforced at the protocol layer, not at a policy page layer.
Where it fits
The Voice Awareness Session is the entry point to the Rhiz Collective. Before the cohort rhythm, before Connections, before any coordination, a member completes the session and reviews their Prescient Report.
After that, the 77 day arc begins.
Where to go next
- Begin a Voice Awareness Session.
- Read the Prescient Report spoke for a line by line walk through of a Report.
- Read the Collective hub to see what the 77 day arc actually contains.
The front door is a conversation. Everything downstream is easier because of what gets captured in those seventeen minutes.