Shared Session Architecture: a deeper overview.
This page gives schools, strategic partners, and qualified investors a conceptual view of JurneeGo’s shared-session design.
Boundary:
This overview discusses system behavior and governance principles, not source code or proprietary implementation detail.
This overview discusses system behavior and governance principles, not source code or proprietary implementation detail.
Why SSA exists
Most AI systems assume a single-user model: one person, one interface, one opaque session. For children, that model introduces risk because learning is inherently social.
SSA treats an AI learning interaction as a shared session object with authorized roles and visible presence.
Role intent
| Role | Purpose | Interaction principle |
|---|---|---|
| Child | Primary inquirer | Asks, reflects, follows curiosity |
| Parent / guardian | Guide and co-curator | Annotates visibly, does not secretly override |
| Teacher | Learning architect | Aligns inquiry to objectives and classroom context |
Governance principles
- Explicit consent before child access
- Role-specific visibility
- Visible adult presence
- Append-only auditability for key safety and session events
- Separation between AI output and curator annotations
Contact: hello@jurneego.ai