Residents.
Residents are the humans learning, making and belonging inside the Hubverse graph — a people-directory node, not an org chart.
Residency Program →Collectives →
Route /residents · Section Community · Status Ready for Design · DRAFT
Proximity needs reasons to become belonging.
- Cities place extraordinary humans beside each other without creating reasons for their questions and practices to meet.Collision
- Feeds can create contact without the trust, contribution and repeated encounters that make belonging real.Belonging
- Visitors cannot always tell the difference between a resident, guest, team member, collective host or partner.Roles
- A people directory becomes theatre when names, roles and current status are not verified.Directory
- A human should know whether to Join, explore Residency, enter a Collective or Apply before sharing personal context.Direction
Residents makes the people layer legible, then routes each human toward a useful door.
Residents makes the people layer visible
See the role types and relationships that make up the people layer without mistaking structure for a published roster.
Connect place, practice and repeated participation through The Hub Bengaluru and adjacent community nodes.
Choose a clear door to join, learn, build, host, publish or experiment with others.
- Every resident can teach the next.
- Every residency can seed a collective.
- Every contribution can become a case.
- Every clear relationship can densify the graph.
What exists today
- The Hub Bengaluru campus, a physical host since 2016.
- Published Join, Collectives, Residency Program, Careers and Apply routes.
- Published case and partnership surfaces.
- This Residents structure page in draft.
- Residency-linked participation formats.
- An honest people-layer frame without an unapproved named roster.
- A published named resident directory with owner-approved biographies and images.
- Distributed resident doors beyond Bengaluru — direction, not shipped.
Truth rule: this page publishes structure and doors, not unapproved people. A named resident directory remains PROPOSED until every identity, image and biography is owner-approved.
Where Residents sits.
- Section
- Community
- Type
- Community
- Priority
- P2
- Status
- Ready for Design · DRAFT
- Hubverse
The umbrella graph connecting people, ventures, collectives, learning, work, belonging and shared infrastructure.
- The Hub Bengaluru
The LIVE physical campus where people can meet, work and participate; no named resident roster is implied.
- Residency Program
A PILOT place-based format connecting learning, making, daily life and belonging.
- Collectives
Practice-led groups that can give residents and builders a shared question, craft or contribution.
- Join the Community
The lower-friction door for entering conversations and discovering a useful next node.
- Team · Careers · Apply
Distinct doors for understanding operators, exploring defined work loops or sharing participation intent.
- Partners
A directory node showing ring presence and relationship context, not an employee or resident category.
How participation works
Orient
Read Residents, About Hubverse and the related community nodes to understand the people layer and its truth labels.
Choose a door
Use Join, Residency Program, Collectives or Apply according to the participation you seek.
Move through the graph
Bring a clear question, relevant context and what you can contribute. A submission does not confirm a place or status.
Enter here if the people layer matters to your next move.
Residents exploring place-based participation or a defined 111-day loop.
Builders seeking useful proximity, sharper questions and people to learn beside.
Collective hosts creating a shared practice without overstating who belongs to it.
Partners exploring the people layer before proposing a scoped way to fund or host.
Visitors who need the difference between Team, Residents and Join the Community made clear.
Named public roster withheld until owner-approved — this draft publishes structure and doors only.
Questions & friction
Residents, Team or Join?
Residents explains the participant and people layer. Team explains operating roles. Join the Community is the lower-friction action door.
Residents or Residency Program?
Residents describes people and role types. Residency Program describes a PILOT place-based participation format.
What is LIVE today?
The Hub Bengaluru campus has existed since 2016. Published community, career, application, case and partnership routes exist today; residency formats remain PILOT.
Is there a public named directory?
No owner-approved named resident directory is published here. Names, images, quotations and biographies remain absent by design.
Do I need to be in Bengaluru?
Bengaluru is the current LIVE physical context. Distributed resident doors remain PROPOSED, so choose Join or Apply to clarify fit.
Is this page final?
No. It is a DRAFT marked Ready for Design and remains noindex until its structure and evidence are approved.
Find the people, practice and door that fit.
Join the CommunityResidents is one community node. The marquee and universe switcher below continue the graph toward people, programs, proof and other useful doors.