Choose Your Learning Route

The Academy can be read from start to finish, but most teams arrive with a specific responsibility: deciding whether Mandaitor is strategically relevant, designing the authority layer, reviewing evidence, or preparing a pilot. These role-based learning routes let each stakeholder start with the lessons that answer their immediate question while still preserving a shared vocabulary across the team.

Use this page as your Academy intake map.

Choose the route that matches your current responsibility, complete the suggested lessons, and then use the capstone workbook to turn the learning path into a concrete pilot decision. Cross-functional teams can assign one route per stakeholder and compare notes in the same review session.

Partner delivery routes are gated.

This public page helps customers and evaluators choose a learning path. Partner-specific delivery routes, workshop scripts, facilitator notes, completed templates, and certification tasks should be kept in the gated Partner Academy described in the public and partner Academy model.

Pick the route that matches your job to be done

Each route points to the same Academy chapter library but changes the reading order, emphasis, and expected output. The goal is not to create separate documentation for every audience. The goal is to make the shared Mandaitor model easier to adopt from different entry points.

Strategic evaluation

Founder / Decision-maker

Is verifiable delegated authority strategically important enough to influence product, risk, or go-to-market decisions?

Outcome

A concise authority-boundary narrative that explains why Mandaitor matters for agentic workflows.

Suggested effort

45–70 min

1. 01
   Foundations of Verifiable DelegationFrame the difference between access, capability, and delegated authority before evaluating product fit.
2. 02
   Agentic AI from First PrinciplesConnect autonomous tool use to the need for explicit authority boundaries and runtime checks.
3. 03
   Compliance Dashboard ExplainedUnderstand what executives and reviewers can see when agent actions become inspectable.
4. 04
   Governance, Risk, and ComplianceTranslate the Mandaitor model into risk, control, and accountability language.
5. 05
   Capstone Pilot WorkbookComplete the authority-boundary milestone to decide whether a first pilot is worth pursuing.

Artifacts to produce

• One-sentence pilot thesis
• Named authority boundary
• Decision criteria for continuing or pausing evaluation

Start with Foundations

Implementation architecture

Builder / Platform Engineer

How should mandates, policies, verification decisions, and evidence fit into a runtime architecture?

Outcome

A technical route from policy design to evidence-producing authorization checks.

Suggested effort

75–110 min

1. 01
   Mandate Policies and Policy EnforcementModel principals, delegates, actions, resources, constraints, obligations, and lifecycle states.
2. 02
   Agentic AuthorizationPlace the verification decision before tool calls, API requests, and workflow actions.
3. 03
   Trust ChainsSeparate cryptographic validity from local business acceptance and issuer trust.
4. 04
   Evidence Packs and Audit EventsTurn verification outcomes into reviewable artifacts that support debugging and assurance.
5. 05
   Capstone Pilot WorkbookComplete the policy and evidence milestones for a bounded implementation scenario.

Artifacts to produce

• Initial mandate-policy sketch
• Runtime verification control point
• Evidence fields required for review

Start with Policies

Oversight and assurance

Reviewer / Compliance Officer

Can I inspect what an agent was allowed to do, why it was allowed, and which evidence supports that decision?

Outcome

A review model for dashboard signals, evidence packs, and governance controls.

Suggested effort

60–95 min

1. 01
   Compliance Dashboard ExplainedRead review queues, risk signals, and evidence status through the product surface.
2. 02
   Governance, Risk, and ComplianceMap Mandaitor evidence to control ownership, risk treatment, and compliance review.
3. 03
   Evidence Packs and Audit EventsUnderstand what evidence should be present before accepting an agentic action as reviewable.
4. 04
   Product Learning PathSee how review expectations connect to adoption planning and staged product evaluation.
5. 05
   Capstone Pilot WorkbookComplete the dashboard-review milestone and define the first review gate.

Artifacts to produce

• Minimum evidence checklist
• Reviewer questions for policy exceptions
• Dashboard review gate for the pilot

Start with Dashboard Review

Pilot execution

Implementation Lead / Pilot Team

How do we convert Academy concepts into a bounded first pilot with owners, gates, and readiness criteria?

Outcome

A complete workbook-driven pilot plan that aligns product, engineering, security, and governance stakeholders.

Suggested effort

120–180 min

1. 01
   Product Learning PathUnderstand the adoption route from product evaluation to a bounded implementation path.
2. 02
   Foundations of Verifiable DelegationAlign the team on the shared authority model before debating implementation details.
3. 03
   Mandate Policies and Agentic AuthorizationUse the policy and runtime lessons to scope the pilot workflow and control points.
4. 04
   Evidence, Dashboard, and Governance LessonsConnect operational evidence to reviewer workflows and executive readiness decisions.
5. 05
   Capstone Pilot WorkbookComplete the full workbook, pilot checklist, ownership model, and expansion gate.

Artifacts to produce

• Pilot scope and success criteria
• Named owners across product, engineering, security, and governance
• Go / no-go gate for expansion beyond the first workflow

Start with Product Adoption

Compare route emphasis

Use the matrix when you are assigning Academy work across a team. A route can be completed individually, but it becomes more useful when each role brings a different artifact into the capstone conversation.

Role	Start with	Core lessons	Capstone use	Reference use
Founder / Decision-maker	Foundations	Agentic AI, Compliance Dashboard, Governance / Risk / Compliance	Authority-boundary milestone and pilot thesis	Glossary terms for mandate, delegate, evidence pack, and governance control
Builder / Platform Engineer	Mandate Policies	Agentic Authorization, Trust Chains, Evidence Packs	Policy model, verification point, and evidence milestones	Glossary terms for policy, constraint, verifier, trust chain, and Proof-of-Mandate
Reviewer / Compliance Officer	Compliance Dashboard	Governance / Risk / Compliance, Evidence Packs, Product Learning Path	Dashboard-review milestone and first review gate	Glossary terms for audit event, evidence pack, control owner, and review workflow
Implementation Lead / Pilot Team	Product Learning Path	All Academy lessons, with policy, evidence, dashboard, and governance lessons used as workshop inputs	Full workbook, pilot checklist, ownership model, and expansion gate	Glossary as the common vocabulary for cross-functional planning

How to run a cross-functional learning review

For a team workshop, assign one route to each stakeholder and ask everyone to bring the artifact listed in their card. The founder or decision-maker brings the authority-boundary thesis. The builder brings a first policy and verification design. The reviewer brings evidence and dashboard expectations. The implementation lead then consolidates the inputs in the capstone workbook.

This structure keeps the Academy focused on learning while making the next adoption step explicit: move from role-specific understanding to a shared pilot plan.