Education

What the university is asking for

Registration rules change every term. A student asks whether they may come back after two semesters away, and the answer sits in three places at once: the regulations, the exceptions the deanship approved last year, and the student’s own record. Three people are needed to assemble it, and it still arrives after the deadline.

• Answer a student from the regulations that actually apply to their case, with the article attached.
• Tell faculty what a rule change does to their sections before the term starts.
• Find every student a new registration rule touches, and say why each one is affected.
• Explain why the student portal is slow in registration week, with evidence from the servers.

How the work is done

An agent is a model, a set of approved skills, tools and a policy, applied to a scope.

Agents answer from your own regulations, documents and records, with the source attached.

Agents reach your systems through approved connectors — APIs, databases, applications — each with its own permissions.

Changes wait for human approval before they run.

The portal, the student system and the mail servers run on machines the university already owns. That is where a university starts, and the registration-week question is the one it answers first.

Read-only execution policy is the default on every enrolled host; the full policy is an explicit, per-host choice.

Every answer shows the exact commands that ran, their exit codes and output, per host.

A host joins the fleet with one install command and an enrollment token; revoking the host unpairs it.

Sign in with your own identity provider (OIDC with PKCE); no shipped default administrator password.

The whole stack self-hosts with one command; an air-gap bundle ships every image.