The people section should not read like a standard team grid unless that is actually useful. For Rhyzome, it can do something more interesting: explain what kind of builders are behind the project and why the product has the shape it has.

Some products are clearly driven by design culture. Others by infrastructure thinking. Others by a narrow feature-market lens. Rhyzome feels closer to a product built by people who care deeply about operational structure: how work gets modeled, how systems stay coherent, and how complexity can be made governable instead of merely hidden.

That kind of orientation affects the product in subtle ways. It shows up in how the platform treats workflow, responsibility, declarative logic, and change management. It also shows up in how the product avoids the temptation to present complexity as if it could simply be wished away.

Over time, this page could become more concrete. It could include founders, contributors, domain experts, implementation partners, or a broader network around the product. But even before it becomes biographical, it can already serve a useful purpose: making the product feel authored rather than anonymous.

For potential customers, that matters. In B2B software, especially in systems that touch real operations, people do not only evaluate features. They evaluate judgment. They want to know what kind of minds are shaping the tool they may build on.