Worked scenario · Administrative
Vendor agent in SIS / LMS / ERP
T4Baseline tier · Institutional
A vendor turns on agent features inside a core system the institution already licenses. The institution did not build it but remains accountable for its use.
The six lenses
| 01 Stakes & audience | Everyone who uses the core system. |
|---|---|
| 02 Data & reach | Full reach of the host system, often including restricted data. |
| 03 Autonomy & authority | Defined by the vendor; may change with releases. |
| 04 Accountability & ownership | System owner remains accountable; procurement and legal involved. |
| 05 Verification & monitoring | Limited visibility into vendor models; contractual reporting needed. |
| 06 Lifespan & scale | As long as the contract. |
The institution provides
- Procurement and legal review
- Standard contract language on data and model use
- Configuration control over agent features
The owner answers for
- Deciding which features to enable and for whom
- Testing features before broad release
- Tracking vendor release notes for scope changes
Failure modes to watch
- Features enabled by default in an update
- Institutional data used to train vendor models
- No exit path or data portability