Education partners / readiness before promises

A partnership path for course-grounded study support.

Examo is exploring institution and educator partnerships while being explicit that organization tenancy, school SSO and district-grade policy controls are still being developed.

Discuss a scoped pilot Read the trust overview

FIELD NOTE 01

Start with a bounded pilot

A pilot should define the cohort, permitted content, support owner, success measures, retention period and escalation path before students are invited.

Named owner
Measurable learning workflow
Time-bounded evaluation

FIELD NOTE 02

Do not outsource academic judgment

Examo is a study-support product. High-stakes grading, admissions, proctoring and disciplinary decisions require separate governance and should not be delegated to Loki.

Human decision-maker
No covert monitoring
Documented limitations

FIELD NOTE 03

Enterprise controls are a gate

Tenant isolation, scoped RBAC, SSO, roster lifecycle and institutional contracts must be completed and reviewed before broad school deployment.

Tenant-aware access
SSO and lifecycle
Contractual data controls

Direct answers

Questions people should ask before signing up.

Review the evidence register

Is Examo institution-ready today?

Not for an unrestricted production rollout. Carefully scoped pilots can be discussed while enterprise controls are completed.

Does Examo grade students?

The current product provides study practice and feedback; it should not be the sole basis for high-stakes educational decisions.

How do we discuss a pilot?

Use the partnership form and include the proposed cohort, jurisdiction, content types and desired outcomes.

Make the next step concrete

Use the product, inspect the controls, and judge it against your real course.

Discuss a scoped pilot