David noticed: shared LMS sync to monitor TLR is the core Kerra loop

Kerra connects to a student course site, syncs shared course content, detects what changed, builds a change report, feeds that report into an internal monitor agent, and then lets specialist agents create calendar events, lecture notes, assignment workspaces, or other study artifacts.

the internal name "monitor TLR" refers to the monitor agent/run that decides what downstream work should happen after a course changes. much of his Codex history is him trying to make that loop reliable.

the questions David keeps asking are causal: what changed, which courses were active, which agent ran, what context did it receive, which tools did it call, what failed, what got written, and what did the student see?

that is the product heart of Kerra: course changes should become useful student work with minimal manual effort.