LIVE RHIZ PAGEOWNED BY ISRAEL WILSONMOVING: CAPTAIN HOMEUPDATED 2026-07-25RHZ-CAPTAIN-SUBSTRATE-V1

Captain, first member

Israel Wilson

The product proves itself here.

I am Israel Wilson, founder of WeRhiz. I am building Rhiz so people and institutions can turn intent into coordinated action with the right context, consent, and memory attached.

This home is the first member artifact rendered directly from Rhiz's per-member markdown substrate. It is not a presentation about the system. The fields, asks, offers, proof, and sovereignty controls below are the system operating in public.

Living member context

11 fields, 7 points each, 77 points of identity.

identity

01 / 11
  1. 11. Founder and CEO of WeRhiz.
  2. 22. Builder of Rhiz.
  3. 33. Captain and first member on the new substrate.
  4. 44. Product thinker working across coordination, identity, and trust.
  5. 55. Operator responsible for turning the product into a durable institution.
  6. 66. Steward of the Rhiz product canon.
  7. 77. Revise this point with the captain's own language.

direction

02 / 11
  1. 11. I'm building Rhiz as sovereign infrastructure for people and organizations whose work depends on relationships, trust, and coordinated action.
  2. 22. Make useful coordination visible, portable, and accountable.
  3. 33. Build sovereign homes that members can understand and control.
  4. 44. Turn relationship context into concrete moves and outcomes.
  5. 55. Establish Rhiz as durable coordination infrastructure.
  6. 66. Deepen the substrate through real operating loops.
  7. 77. Revise this point with the captain's current direction.

strengths

03 / 11
  1. 11. Seeing systems and the human commitments inside them.
  2. 22. Naming a product thesis and carrying it across disciplines.
  3. 33. Connecting strategy, design, engineering, and distribution.
  4. 44. Holding an ambitious vision while demanding working proof.
  5. 55. Translating scattered context into a coherent operating model.
  6. 66. Building trust through visible artifacts and accountable action.
  7. 77. Revise this point with a strength others can verify.

friction

04 / 11
  1. 11. Too much product truth still lives across separate documents and systems.
  2. 22. The product must become simpler without losing its depth.
  3. 33. Real coordination loops need stronger proof at the public edge.
  4. 44. Founder context can outpace what the interface makes legible.
  5. 55. Legacy surfaces can obscure the current system.
  6. 66. Distribution must grow without weakening consent or sovereignty.
  7. 77. Revise this point with the captain's most important current friction.

values

05 / 11
  1. 11. People should own their identity, relationships, content, and coordination memory.
  2. 22. Technology should increase human agency, never diminish it.
  3. 33. Relationships are infrastructure and deserve the same rigor as software.
  4. 44. Build systems that produce measurable outcomes, not activity.
  5. 55. Sovereignty comes before convenience.
  6. 66. Simplicity is earned through deep understanding.
  7. 77. Tell the truth, even when it costs you.

pulse

06 / 11
  1. 11. Shipping the first public home on the member markdown substrate.
  2. 22. Consolidating Rhiz around ecosystem coordination.
  3. 33. Proving founder workflows through the system itself.
  4. 44. Turning audits and decisions into live product evidence.
  5. 55. Building the coordination graph through real participant activity.
  6. 66. Preparing proof that investors, candidates, and partners can verify.
  7. 77. Revise this point with what is moving this week.

questions

07 / 11
  1. 11. Which accountable ecosystem outcome should Rhiz prove next?
  2. 22. What is the narrowest loop that creates undeniable coordination value?
  3. 33. Which institutions already feel this problem acutely enough to act?
  4. 44. Where does member sovereignty still depend on trust instead of a visible control?
  5. 55. What context should stay private even when coordination improves by sharing it?
  6. 66. Which proof artifact most changes a serious partner's mind?
  7. 77. Revise this point with the captain's live question.

network

08 / 11
  1. 11. Founders building trust-dependent ventures.
  2. 22. Institutional operators accountable for ecosystem outcomes.
  3. 33. Designers and engineers building humane coordination tools.
  4. 44. Capital partners who understand infrastructure and institution-building.
  5. 55. Community leaders stewarding permissioned fields.
  6. 66. Candidates who want to build the relational context layer.
  7. 77. Revise this point with a connection field the captain wants activated.

operations

09 / 11
  1. 11. Product and canon decisions flow into one Amorphous engine.
  2. 22. Meaningful actions persist through protocol-owned contracts.
  3. 33. Public proof must link to live surfaces.
  4. 44. Founder work should become reusable Rhiz capability.
  5. 55. No fake actions ship.
  6. 66. Every new loop must make context or coordination more useful.
  7. 77. Revise this point with the captain's operating cadence.

asks

10 / 11
  1. 11. Introduce me to organizations where relationships determine outcomes and coordination keeps breaking down.
  2. 22. I want paid design partners willing to solve one real problem with Rhiz and document what changes.
  3. 33. Direct critique from people who have built trusted infrastructure.
  4. 44. Candidates who can build across product, systems, and distribution.
  5. 55. Capital aligned with patient infrastructure and urgent execution.
  6. 66. Evidence about where coordination currently breaks.
  7. 77. Replace this stub with the captain's highest-priority ask.

offers

11 / 11
  1. 11. I help leaders turn scattered relationships, commitments, and opportunities into a working system that produces outcomes.
  2. 22. Bring me a real coordination problem, and I'll tell you directly whether Rhiz can solve it.
  3. 33. Product and systems thinking across identity, context, and action.
  4. 44. A sovereign operating surface shaped around a real outcome.
  5. 55. A builder's perspective on turning relationships into accountable movement.
  6. 66. A network of people committed to more useful coordination.
  7. 77. Replace this stub with the captain's strongest current offer.

Asks

What would move the work.

  • Introduce me to organizations where relationships determine outcomes and coordination keeps breaking down. I want paid design partners willing to solve one real problem with Rhiz and document what changes.

Offers

What is available now.

  • I help leaders turn scattered relationships, commitments, and opportunities into a working system that produces outcomes. Bring me a real coordination problem, and I'll tell you directly whether Rhiz can solve it.

Values

Principles that hold the work accountable.

  1. 01People should own their identity, relationships, content, and coordination memory.
  2. 02Technology should increase human agency, never diminish it.
  3. 03Relationships are infrastructure and deserve the same rigor as software.
  4. 04Build systems that produce measurable outcomes, not activity.
  5. 05Sovereignty comes before convenience.
  6. 06Simplicity is earned through deep understanding.
  7. 07Tell the truth, even when it costs you.
  8. 08Long-term trust is more valuable than short-term growth.
  9. 09Open standards create stronger ecosystems than closed platforms.
  10. 10Build durable foundations before adding features.
  11. 11Leave every person, community, and system stronger than you found it.
  12. 12Design for people who have been overlooked, excluded, or underestimated.
  13. 13Create leverage that helps others create leverage.
  14. 14Craft matters. Details compound into trust.
  15. 15Success is measured by the opportunities and outcomes your work creates for others.

Personal Canon

Principles for how the captain lives and builds.

  1. 01Relationships Above Transactions — Every meaningful opportunity begins and ends with people.
  2. 02Sovereignty — People should own their identity, work, relationships, and future.
  3. 03Opportunity for Everyone — Talent is universal. Opportunity isn't. Your work exists to close that gap.
  4. 04Build What Lasts — Create institutions and infrastructure that outlive their founders.
  5. 05Truth Before Comfort — Face reality, even when it's inconvenient or costly.
  6. 06Service Through Creation — Solve meaningful problems by building useful things rather than talking about them.
  7. 07Keep Your Word — Trust compounds through consistency.
  8. 08Learn Relentlessly — Curiosity is one of your greatest competitive advantages.
  9. 09Think From First Principles — Challenge assumptions and rebuild from fundamentals.
  10. 10Leave People Better — Every interaction should create more possibility than existed before.
  11. 11Justice Through Access — Expand access to knowledge, capital, networks, and technology for people who have historically been excluded.
  12. 12Craft Matters — Quality reflects respect for the people who use what you build.
  13. 13Collaboration Creates Abundance — The best outcomes emerge when capable people coordinate around a shared purpose.
  14. 14Growth Is a Responsibility — Keep becoming a better builder, leader, father, and human being.
  15. 15Measure Life by Impact — Success is measured by the opportunities you create, the people you elevate, and the systems you leave behind.

Sovereignty receipt

Verify the member controls.

Public proof object

Privacy

This home is on the new markdown substrate (not the legacy gift-page-seeds monolith).

Member preferences

LineageRead preview

Reading the member lineage union.

Capabilities present

  • coordination graph
  • sovereign intelligence + living member context
  • model neutrality

Substrate proof

  • Per-member markdown storage through the legibility adapter.
  • Eleven living fields with seven points each.
  • One canonical LineageRead across referrals, introductions, proposals, and outcomes.
  • Capability-aware rendering for the coordination graph, sovereign intelligence with living member context, and model neutrality.
  • Working export, deletion, privacy, model-training, model-routing, and outcome-visibility controls.
  • A public member home that does not read from the legacy gift-page seed monolith.