MetaPet Schools Family Participation Protocol
This protocol explains how the first pilot should handle family communication and student participation.
Recommended Default
For the first pilot, the recommended default is parent/carer opt-in before direct student use. If a school uses a different approved local process, that process should be documented clearly before the pilot starts.
Communication Flow
Send the parent note and parent/carer privacy notice before the first lesson.
Tell families the class purpose, the low-data setup, and who to contact with questions.
State the participation deadline and how families respond.
Confirm the class participation list before students use the runtime directly.
If A Family Does Not Opt In
Do not assign that student as the primary device user.
Offer observation, discussion, paper reflection, or partner participation that does not require direct runtime interaction.
Keep the student included in class discussion where appropriate without forcing direct tool use.
Shared-Device And Alias Guidance
Use aliases only.
Do not create a direct-use alias for a student who is not participating directly.
If devices are shared, clear local school data at the end of the agreed pilot window or earlier if the school requires it.
If a teacher is unsure whether a student should use the device directly, do not proceed until the class list is confirmed.
Teacher Language
Suggested classroom explanation:
> This is a short classroom learning tool. Some students may use the device directly and some may join by observing, discussing, or working with a partner. That is fine.
Record Keeping
Keep the family response list outside the student-facing runtime.
Do not store participation status inside the classroom alias list unless the school has a documented reason to do so.