Academy Governance Alignment

●Draft

Status: Draft
Version: 0.1.0
Last Updated: 2026-05-16
Owner: Academy Nucleus

---

Purpose

This document explains how Academy relates to Governance, Business, and ACS.

Scope

It covers policy legitimacy, partner and DAO educational requests, ACS-assisted review, authority boundaries, and escalation rules.

Overview

Academy is not isolated. It may become one of the first user-facing nuclei where Axodus education, token utility, Marketplace commerce, and governance policy intersect.

It needs clear boundaries between product operation, business intake, AI-assisted review, governance approval, and human accountability.

Governance Role

Governance may define or approve high-impact reward policy, locked reward utility rules, tutor quality policy, Marketplace course policy, sensitive course categories, abuse escalations, certification use for governance or product access, and material policy records.

Governance is required when reward budgets or emission policy change, locked rewards gain governance or Marketplace utility, certification affects governance rights or product access, tutor policy affects ecosystem quality, partner programs have major impact, Marketplace fee distribution changes at policy level, or abuse incidents require public accountability.

Governance is not required for routine course copy edits, low-risk metadata updates, minor UI text updates, ordinary non-sensitive publication if policy allows it, or internal quality feedback without policy changes.

Business Role

Business may receive partner training requests, DAO education program requests, custom Academy track requests, tutor partnership requests, sponsored Learn-to-Win campaigns, BBA education campaigns, certification program requests, or Marketplace course bundle requests.

Business outputs should include intake forms, request classification, scope, deliverables, commercial terms, governance touchpoint mapping, risk classification, and execution plan.

ACS Role

ACS may analyze course content, detect missing risk disclosures, identify misleading claims, assist assessment generation, classify course category and difficulty, suggest learning paths, review tutor profiles, detect reward abuse patterns, summarize learner feedback, and support governance review.

ACS cannot final-approve sensitive courses, final-approve rewards, replace tutor validation, replace governance policy, guarantee content accuracy, or autonomously mint or unlock rewards.

Policy Flow

1. Policy need is identified.
2. Academy or Business creates a policy request.
3. ACS assists analysis.
4. Risk level is assigned.
5. Responsible governance layer is identified.
6. Human review occurs.
7. Governance review or vote occurs if required.
8. Policy is approved, rejected, or revised.
9. Academy runtime and documentation are updated.
10. Accountability record is created if material.

Partner and DAO Education

Partner course requests should flow through Business, Academy review, ACS risk and claims review, Marketplace terms if commercial, reward policy review if rewards are requested, governance review if sensitive, implementation, listing or access creation, learner feedback, and reporting.

DAO education requests should record DAO context, identify learning paths, map DAO-specific risks or plugin context, and trigger governance review if the course affects official federation or product access.

Authority Boundaries

• Academy operates learning paths, course content, progression, and assessments within policy.
• Business scopes partner and DAO programs but cannot approve governance-sensitive reward policy alone.
• ACS analyzes and recommends but cannot approve, govern, mint, or unlock.
• Governance approves policy and supervises high-impact changes but cannot ignore contract security or guarantee outcomes.