SocioProphet

Appearance

Academy Interaction Contract ​

This document defines the allowed interaction model for Academy participants, mentors, guardians, and platform operators.

Why this exists ​

Educational systems fail when interaction boundaries are implied but not encoded. Academy uses an explicit interaction contract so that role boundaries, reviewability, and safeguarding expectations are clear.

Roles ​

The main interaction roles are:

  • learner
  • mentor
  • guardian
  • operator / safeguarding reviewer
  • organization / provider representative

Interaction design goals ​

The interaction model is designed to:

  • reduce private, opaque, and unsafe communication patterns
  • keep learning pathways usable
  • preserve attributable records
  • support guardian-linked participation where appropriate
  • enable escalation and review

Adult and minor interactions ​

Adult-to-minor interactions must be bounded by the documented safeguarding model. Academy does not treat unrestricted private adult-to-minor communication as a normal operating mode.

Where minor participation exists, the contract must favor:

  • structured sessions
  • attributable records
  • guardian-aware or safeguarded pathways
  • documented reviewability

Learner interactions ​

Learner-to-learner interaction may be permitted within documented boundaries, but it is still subject to platform policy, escalation rules, and safety review.

Guardian-linked pathways ​

Where policy requires it, guardians are linked into visibility, approval, or oversight pathways. Guardian-linked pathways must be explicit rather than informal.

Reviewability ​

Important interaction pathways must be:

  • attributable
  • bounded by role
  • reviewable when policy requires it
  • supportable in escalation workflows

Sensitive situations ​

The interaction contract must not force all reports into ordinary visibility patterns. Sensitive safeguarding scenarios require special handling and documented escalation logic.

Enforcement ​

The interaction contract is meaningful only if product and operations actually enforce it. This includes:

  • role-bounded interactions
  • controlled communication paths
  • auditability
  • escalation support
  • policy-linked handling
  • Academy Safeguarding and Minor Protection
  • Guardian Rights, Sensitive Reports, and Escalation
  • Privacy
  • Terms