Academy Safeguarding and Minor Protection

Academy is a human-first educational and cybernetics learning environment. Safety is not treated as an optional moderation layer or an afterthought. It is part of the operating model, the interaction model, and the system charter.

Purpose

This document defines how Academy protects minors, constrains adult interaction pathways, supports guardian oversight where appropriate, and maintains documented escalation paths for harmful or sensitive situations.

Core commitments

Academy is designed to:

• protect minors by default
• avoid private, unreviewable adult-to-minor interaction patterns
• preserve guardian visibility where appropriate
• support sensitive reporting pathways
• route serious issues into documented safeguarding and escalation workflows
• keep the platform aligned to a human-first charter

Interaction principles

The core operating principles are:

1. No private adult-to-minor direct communication outside the documented safeguarded model.
2. Learning interactions involving minors must be structured, attributable, and reviewable.
3. Guardian participation or visibility is supported where policy requires it.
4. Sensitive or harmful situations must have a documented reporting and escalation path.
5. Safety controls are part of the product architecture, not only community policy.

Minor protection model

For minor participants, Academy uses a safeguarded interaction model rather than an open-ended social platform model.

This means:

• interaction pathways are constrained by role and context
• communication models are documented
• adult access is bounded by policy
• platform records and routing controls support review and escalation

Guardian and family oversight

Academy supports guardian-linked participation models where appropriate. Guardian-linked workflows are intended to provide transparency, safety, and clarity without collapsing the participant’s ability to learn or report concerns.

Guardian visibility does not eliminate the need for sensitive-report pathways. A participant must still be able to raise certain concerns safely through documented safeguarding channels.

Reporting and escalation

Academy maintains a documented pathway for:

• safety concerns
• boundary violations
• harmful or coercive conduct
• situations requiring review, intervention, or escalation

Sensitive reports may require restricted handling rather than immediate broad visibility. The platform must distinguish between ordinary review and sensitive safeguarding workflows.

Platform enforcement stance

Academy does not rely only on good intentions. Safety depends on:

• constrained interaction models
• attributable actions
• auditable records
• clear role boundaries
• escalation procedures
• policy-linked system behavior

Human-first charter

Academy’s educational and cybernetics work is bounded by a human-first charter. Platform use that is coercive, abusive, exploitative, or anti-human is outside the intended use of the system.

Related documents

• Academy Interaction Contract
• Guardian Rights, Sensitive Reports, and Escalation
• Privacy
• Terms