For educatorsSLE — K-12 teacher

Your day with SLE.

Eight hours, thirty learners, one of you. Here is what a teaching day looks like with ArthurAI School Learning Edition in the room — not as a chatbot grafted onto your gradebook, but as an Agentic Learning OS the school deploys around you.

  1. 6:45 AM

    The lesson plan generates while you have coffee.

    ArthurAI™ has already produced today's lessons against your district's scope-and-sequence. Each student's lesson is personalized to their Learning Cognitive Profile — visual or verbal, sequential or global, sensing or intuitive. You open the dashboard, scan the suggested lesson scope for first period, and adjust two of them where the AI's pacing doesn't match what you saw last week. You attest the rest. The class is ready.

  2. 8:15 AM

    First period. The AI tutor takes the questions you can't get to.

    While you're working with the small group on long division, three other students hit the AI tutor with questions about the reading. The tutor knows what lesson they're in. It answers in the student's selected language — two of them are stronger in Spanish than in English, and that's fine. Tutoring is disabled during the practice questions, so the AI can't write the answer for them.

  3. 10:00 AM

    Differentiation that doesn't take a planning period.

    The student who struggled with last week's vocab quiz gets a different scaffold today — same competency, more visual support, more spaced practice. The student who is ahead gets a stretched real-world application step. You didn't build either of those by hand. The AI did, against the LCP, against the lesson scope, and you reviewed both before they reached the kids.

  4. 12:30 PM

    Lunch. You see your class data the way a teacher should see it.

    The faculty analytics show the class as a whole — who's on pace, who's stuck on which competency, who hasn't logged in this week. The AI is not flagging students for intervention. You are. The AI shows you what it sees; you decide what it means.

  5. 2:30 PM

    End of class. Grading is transparent.

    Today's quiz auto-scores the multiple-choice items. The AI suggests a rubric-aligned score on the short-response items, with citations to the student's text. You read each one. You attest. The grade enters the gradebook with your signature, not the AI's.

  6. 3:30 PM

    Parent message. The disclosure is in-line.

    A parent emails about why their seventh-grader has different reading material than her cousin. You forward the district's AI-disclosure language (the same paragraph that appears on every AI-assisted surface in the platform), explain the LCP-driven personalization in two sentences, and link the parent to the sign-off they made at the start of the year. Disclosure is by construction here — not a modal nobody reads.

  7. 5:30 PM

    You're home.

    Tomorrow's lessons are already generating. You'll review them in the morning. The day didn't grow by an hour because you used AI; it actually got shorter.

What sits underneath this
  • Learning Cognitive Profile (LCP) — 30-question diagnostic across 4 dimensions (Visual-Verbal, Active-Reflective, Sensing-Intuitive, Sequential-Global) drives the personalization you see all day. LCP architecture →
  • Six-step lesson flow — Introduction, Key Concepts, Detailed Explanation, Practice Questions, Real-World Applications, Summary. Each step generates against the lesson scope. Lesson flow →
  • The AI tutor — context-aware, multi-language, with text-selection support and conversation persistence. Tutor architecture →
  • Engineered compliance — FERPA school-official posture, COPPA school-as-agent model for under-13 cohorts, AB-1791 disclosure language for California districts. Compliance posture →
The motto

The AI reasons. The teacher decides.