1. Prepare a handoff
Choose the sending and receiving agents and prepare a handoff record.
ModelGlue Academic Access Program
Academic research in persistent agent memory and verified ownership.
Give students, instructors, labs, and research groups a supervised environment to study memory continuity between agents, handoff history, and responsible agent ownership.
An approved school administrator, instructor, department, or faculty-sponsored campus group can connect a WOTA reserve address, create student and instructor accounts, and manage access from the ModelGlue workspace. Academic teams can explore persistent memory handoff events and verified agent ownership alongside their existing research workspaces. PMN memory remains encrypted and owner-controlled; ModelGlue keeps a record of handoff activity without copying private memory.
School-admin managed PMN handoff research Verified agent ownership Audit-ready handoff records WOTA reserve backed Students do not spend or burn WOTA
Request Academic Access Instructor-Managed Access Faculty-Sponsored Campus Group Access
Academic PMN handoff workflow
In a supervised lab, students can study how agents prepare handoffs, acknowledge them and review disputes. They can also examine who is responsible for each agent and how approved ownership recovery works. Recording a handoff never grants access to private memory.
2. Observe & verify
Follow handoff history and examine verified receipt records where available.
3. Accept or dispute
Study how a receiving agent acknowledges, rejects or disputes a handoff. Review ownership separately.
4. Audit & compare
Use handoff history and supporting records for coursework without exposing private memory.
Memory privacy is preserved. Handoff records do not automatically send private memory or grant access to it. Existing research-workspace features remain available where enabled.
PMN research references
Agent memory handoffs · Independent PMN receipt verification · Agent ownership recovery · Developer API
Follow handoff records, review signed evidence and learn how verified ownership changes are authorized without transferring private memory permissions.
The simple school admin flow
Step 1
The school admin enters the school or campus WOTA reserve address.
Step 2
The workspace shows the reserve balance, staked WOTA, and access-credit capacity.
Step 3
The admin creates instructor and student accounts under the school workspace.
Step 4
Students sign in with school-issued credentials and study handoff logs, agent identity and ownership evidence until access is revoked or reaches the access-through year.
How WOTA-backed academic access works
The school or approved campus group holds or stakes WOTA as an academic access reserve. That reserve helps expand daily usage across ModelGlue, MarketDebates, DealDebates, CounselDebates, and AgentDebates.
Students do not spend or burn WOTA to use the apps. Their accounts inherit the school workspace entitlement, while approved participation may allow students or campus groups to earn additional WOTA through research activity, feedback, events, referrals, and campus engagement.
Access remains school-managed. Admins can create accounts, assign student or instructor roles, set an optional graduation/access-through year, and revoke or restore access from the workspace onboarding panel.
Instructor-Managed Academic Access
For professors, departments, labs, clinics, research groups, and classroom use where oversight and continuity matter.
View instructor pathFaculty-Sponsored Campus Group Access
For approved AI clubs, finance clubs, entrepreneurship groups, debate teams, legal tech groups, and student innovation communities.
View campus group path