Morning Brief
One page before first bell: who is absent, what changed overnight, which flags need a human today.

The school runs on it. The students learn to build it.
Twenty-three agents that read the student information system read-only, do the repeated office work before first bell, and catch a slipping student in week two instead of at the progress report. Plus an apprenticeship cohort that ships reviewed work into the same codebase.
Deans, front office, counselors, teachers, students, parents
DIDM has this live on a named account or on its own operation. The proof line below is measured, not modelled.
The dean opens twelve tabs before first bell to answer one question. A student starts sliding in week two and nobody sees it until grades post six weeks later. The front office answers the same handbook question forty times a term. A teacher who wants a differentiated version of an assignment builds it at nine at night.
Blackbaud, PowerSchool or your SIS, read-only · Google Classroom · your handbook and course catalogue · the school's own tenant, always
Read-only, through credentials you issue and can revoke in a click.Not one assistant asked to do everything. Six narrow agents that run on a schedule, hand their work to a person, and log what they did. You can read every one of their instructions.
One page before first bell: who is absent, what changed overnight, which flags need a human today.
Watches per-assignment work and flags a real slide inside two weeks, split into counselor caseloads capped at fifteen.
Answers the handbook question with the section and the date, and hands anything it cannot source to a person.
Turns one assignment into the versions a mixed classroom needs, and catches errors in the answer key on the way through.
A capped, logged workspace per student with a spend ceiling and a portfolio that shows what they actually built.
Shows families only what a teacher or counselor released — words, never raw numbers.
One agent reads everything that changed overnight and says it out loud in under a minute. Items that need a person are named. Nothing in it was decided by the fleet.
“Good morning. Six thirty, and here is your day before it starts. Attendance overnight: fourteen absences, three of them a third consecutive day, which puts them on your desk rather than the office's. Second: the slip detector flagged four students this week — two are new, and one of those is a student whose work dropped off eleven days ago in two subjects at once. Counselor queues are split and capped. Third: the front office handled thirty-one handbook questions overnight and passed two up, both about the new phone policy, because the handbook does not actually answer them yet.
Sample script · invented names and figures · Schools
This is the depth every one of the ten pages goes to; schools is simply the one that is furthest along. Scout reads the systems a school already runs on, notices what a person would want to know, and writes it down for that person. It pinpoints where a student is slipping or excelling, fast, and puts a tutoring path or a different route in front of the people who decide. Nobody on staff is replaced; everybody is earlier.
One boring, repeated, checkable task, chosen by the office. Scout does it before the day starts; the office checks it.
Read-only view of grades and attendance. Scout flags a slide in week two; a counselor decides.
Differentiated versions, first-draft feedback, parent notes the teacher approves. Volunteers only.
An apprenticeship cohort builds on a real system with read-only keys and reviewed changes.
Demo Day in the gym. Local businesses meet the builders.
The same rule our own agents live under at the agency: unattended things hold read-only keys; anything that writes needs a person in the loop, per task.
That is the whole first conversation. We map deans, front office, counselors, teachers, students, parents, pick the task your people would most like back, and show you what the first agent would do before it does anything.