One base platform, three separate verticals: Organizational (cities, companies, conferences), Educational (schools, classrooms, teachers, students) and User (the individual avatar creator).
This page is the expanded version of the v2 architecture board: same login and tenant model, redrawn to show every role, every scope boundary and who can see what.
Two terms from the sprint plan, decoded
Both came straight out of the v2 delivery plan, not the architecture board itself. Here is what each one means and where it lives.
Walking skeleton flows
Not wireframes. It is an agile engineering term for the thinnest possible slice of the real system, login all the way through to a scoped session, built end to end before any feature logic sits on top of it. It proves the plumbing works before the team spends sprints on features.
Sprint 0 to 1, v2 delivery plan · the two flows named are SSO login and tenant switch (figure 1)
Tenant switch
The guess was right. It is the moment a person who belongs to more than one organization or school picks which one they are currently working inside. Everything after that, avatars, rosters, branding, insights, is scoped to the tenant they picked.
Confirmed by the architecture board's tenant isolation boundary and SSO org login node
How a login becomes a scoped session
This is the walking skeleton itself: the one flow every vertical shares before it ever reaches a role specific screen.
Figure 1. The two gold nodes, login and tenant switch, are the walking skeleton the developer seeds in Sprint 0 and 1. The resolver checks one shared identity and tenant membership table: zero memberships routes straight to the personal, tenant free User vertical; one or more routes through tenant switch (silent if there is only one) into either the Organizational or the Educational vertical.
Three verticals, one platform
Organizational covers cities, companies and conferences. Educational covers schools, classrooms, teachers and students. User is the existing individual model: create, train and share a personal avatar with no tenant at all.
The Organizational and Educational shapes are close cousins (an admin role, a scoped console, an isolated tenant), but Educational nests a second boundary inside the first: a classroom sits inside a school the same way a school sits inside the platform.
Figure 2. Organizational is one flat boundary: admin sees everything in the org. Educational nests a second boundary inside the first, so a teacher who switches tenants between two schools is doing the same thing an org admin does across two organizations, and a teacher who moves between classrooms inside one school is a smaller version of the same switch, scoped one level deeper.
Permissions by role
Full control, scoped control (their own team, classroom or org only) or none, across the actions people actually ask about.
●full◑scoped○none
Role
Create / edit avatar
Manage users / roster
Branding & guardrails
Insights & analytics
Billing
Chat / use avatar
Public, no login
HIVE Ops
●
◑
◑
●
●
○
○
Org owner / admin
●
●
●
●
●
●
○
Team / content manager
●
○
○
◑
○
●
○
Org member (staff)
○
○
○
○
○
●
○
Audience (public)
○
○
○
○
○
◑
●
School admin
●
●
●
●
●
●
○
Teacher (own classroom)
◑
◑
○
◑
○
●
○
Student
○
○
○
○
○
●
○
Consumer (individual)
●
○
○
○
●
●
○
Before this is official, not yet confirmed
Can a student personalize or create an avatar, or is every classroom avatar teacher owned and student facing only.
Does the Educational vertical need a guardian or parent role at all, and if so, what should it see.
Does Educational get the same white label branding and web embed as Organizational, or does its privacy posture call for console only access.
Billing unit for Educational: per school, per classroom, or per seat, the way Organizational already prices per org license.
Confirm tenant switch applies the same way to a teacher moving between classrooms in one school and between two different schools.