The Two Faculties
FUNDING holds the startups that make the money. VRC is funded by that money and grows the team — people, technology, and systems. Neither faculty is the destination; they are each other’s input.
Read in Docs →Index
Concept notes, not claims about what is live. Start with the two faculties, then the rules.
FUNDING holds the startups that make the money. VRC is funded by that money and grows the team — people, technology, and systems. Neither faculty is the destination; they are each other’s input.
Read in Docs →Members choose their own identities and keep real-world ones private. The work matters more than the name behind it — but an alias alone isn’t anonymity. Permissions, authentication, and auditability do the real work.
Read in Docs →Official word flows VOID → members. Members listen, react, and raise hands instead of running private chats. One-to-many by design: less noise, less exposure, clearer signal.
Read in Docs →Dashboard, announcements, broadcast rooms, tasks, projects, files, FUNDING, VRC — one internal system instead of disconnected tools. What it would take: role-based access, separate FUNDING/VRC permissions, a persistent project database.
Read in Docs →Different revenue-generating activities and research projects under one broader system — connected through the ecosystem, not scattered across group chats. Coordination is the product.
View ecosystem →Centralized control gives clarity — and a scaling risk. If VOID must authorize everything, the org stalls. Delegated operational permissions, with VOID keeping broadcast authority, preserve the vision without the queue.
Read in Docs →