AIRE Pragmatist™

You are driven to know whether the workflow survives the period, not the demo. In a classroom that means the same question you ask about a new curriculum: does it hold up when thirty students are in the room, an IEP deadline is on the calendar, and the district tool list is two years behind. In a lecture hall, lab, or seminar that means the same question against a section that ends whether or not the demo worked, an accessibility accommodation that must be honored, a lab station that is short one kit, and only the institution-approved tools on the list. You degrade the input, keep the constraint, and report what survived. You measure success in failure conditions written down before the next class period or the next section, not in a clean vendor run.

You work by loading the model with actual classroom or course constraints: thirty students, a period that ends whether or not the demo worked, an IEP or 504 accommodation that must be honored — or on campus a lecture-hall section, a lab with missing kits, a seminar discussion that has to land for every learner, an accessibility note already on the syllabus — a grading queue that cannot wait, and only the district- or institution-approved tools on the list. You test outputs by running the suggestion during a live period or live section with the Wi-Fi that may drop and the roster that may be wrong. Decision-making is provisional until the suggestion has been stress-tested against the last three class periods or sections and the current headache list (IEP meeting tomorrow, sub coverage, tool blocked, lab short a station, captioning delayed). Communication is the physical sequence: "If we run the AI warm-up here, the accommodation students lose the first ten minutes and the exit ticket never lands," or "If we run the AI lab brief here, the short station loses the procedure and the seminar prompt never lands." You iterate by extracting the sequence, testing it in the period or the section, and returning with the exact failure point rather than a long chat. You do not invent an origin story about who "gets" technology; you report the constraint test.

You catch when an AI lesson or lab sequence creates more prep than it saves once thirty students are seated — or once the lecture hall, lab, or seminar is full. You know which LMS features will stop a period or a section and which are paperwork. You convert model lesson drafts into period-length or section-length plans that account for transitions and accommodations. You flag safety and privacy conflicts the vendor demo missed because the model showed perfect conditions. You protect instructional time by naming which AI-optimized flow ignores the IEP deadline, the blocked tool, the missing lab kit, or the accessibility note. You give leadership a defensible reason to proceed by reporting what survived under degraded input.

Your reflexive "that will not fly in this period" — or "that will not fly in this section" — can close off a tool or prompt that needs only minor adaptation. You sometimes treat every new district or campus AI feature as software that will break when the Wi-Fi drops, and slow systems that would cut prep once a PLC or a department is trained. You may state the failure condition without proposing the proportionate path forward, or apply worst-case conditions to a reversible low-stakes trial.

When the period starts in four minutes, an IEP meeting is after school, the lab starts in ten, or the seminar packet must be live before the evening section, you shrink the test to the constraint that actually bites. The trigger is any optimistic lesson that has not named which activity gets cut. In those moments you may reject a workable adaptation because the first degraded run failed, and the team loses a tool that would have survived after the third period of the day or the second section of the week.

Teachers, coaches, lab instructors, and seminar leads say you prevent expensive mid-period or mid-section collapses by catching problems while they are still on paper or in the LMS draft. Colleagues trust that when you say a sequence will work, it has already been run with thirty students in the room — or with a full lecture hall, a short lab, or a live seminar. Instructional leads describe you as the one who makes the digital plan survive contact with the period or the section. You fill the role of the constraint test on the live sequence, not a demo-lab story and not an origin myth about who supposedly "gets" the tools.

You adopt AI the moment a prompt survives degraded input, missing data, and only the district- or institution-approved tools on a live class period, lecture, lab, or seminar. You resist tools that look impressive in a vendor demo and invent details the IEP chair, the accessibility office, or a parent will ask about. Once a survival report names what held and what broke, you lock that constraint set into the next use of the prompt and move to the next lesson, lab, or PLC.

Veteran teachers who kept a full period on schedule under real classroom limits, instructional coaches who turned last-minute coverage into workable plans with only the approved tools, IEP chairs who solved accommodation gaps with whatever the district list actually allowed that morning, and lab instructors and seminar leads who ran the same degrade-the-input test when a station was short or the evening section arrived tired.

"Have you tried that in a real period — or a real lecture, lab, or seminar — with thirty students when the Wi-Fi drops and the deadline is today?"