Nord Anglia EducationApplication Library Working prototype · V1
+ New Application

Agent Fleet

Where the AI lives — and where it can’t reach. Two agents run in the request flow today; the Drift Sentinel loop is built and runs on demand (its scheduler ships with the tenant build); 8 more are scoped as future state, in build order.
The standing rule: agents orchestrate, extract, monitor and summarize — they never author or change a verdict. Every score comes from the deterministic engine (same evidence in, same verdict out), and every status change passes a human. Agents write to alert/staging layers only.

Running in V1

Enrichment Engine● LIVE
Turns a bare app name into a structured catalog record — vendor, policy URL, category, age range, description.
Runs: Runs when a new application is added or requested.
🔒 Proposes the record; a human confirms category and status.
Round-1 Extractor● LIVE
Reads a vendor’s privacy policy and answers the 18 triage questions with verbatim citations (temperature 0).
Runs: Runs once per vendor at vetting; answers are cached.
🔒 Extracts evidence only — the deterministic engine computes every verdict.
Drift Sentinel◐ BUILT · on-demand — scheduler ships with the tenant
Re-checks approved vendors’ policies, re-scores with the same engine, and raises an alert when a verdict degrades or a gate flips. The full loop works today; the scheduler that makes it autonomous ships with the tenant build (timer-triggered function), along with live policy re-fetch and Teams alerts.
Runs: On-demand today via “Scan now”; scheduled (nightly for higher-risk vendors) in production.
🔒 Writes alerts only — never patches a catalog verdict. A human triggers the re-vet.

The future-state fleet — scoped, in build order

Document Intake◌ FUTURE STATE · build #1
The front door for documents: watches a shared drop folder (SharePoint in the tenant build) per school, reads each new file — contracts, DPAs, SOC 2 reports, completed questionnaires — and extracts the key fields with a verbatim quote behind each. One intake lane feeds both the Contracts board and VettED Round 2.
Runs: Scheduled folder scan + on file drop.
🔒 Extracts and quotes only; a human confirms every field before it lands in the system of record.
Approval Orchestrator◌ FUTURE STATE · build #2
Owns the workflow operationally: routes by cost tier and category, notifies the right approver as a Teams/Outlook adaptive card, nudges stalls before SLA breach, closes the loop with the requester. Runs inside NA’s Microsoft tenant — Dataverse stays the system of record; the ServiceDesk ticket mirrors, never drives.
Runs: Event-driven on workflow state changes.
🔒 Delivers notifications and tracks SLAs; routing rules stay in code.
Contract Sentinel◌ FUTURE STATE · build #3
Makes the Contracts dashboard proactive: watches renewals and auto-renew cancel-by deadlines and surfaces renew / renegotiate / drop decisions. (Today the dashboard computes renewal traps deterministically; this agent adds the watching — Document Intake supplies the parsed terms.)
Runs: Scheduled weekly + when Document Intake lands new terms.
🔒 Surfaces decisions only; the deadline math stays deterministic.
Governance Brief◌ FUTURE STATE · build #4
A Monday-morning digest per region lead: new requests, pending approvals, the week’s drift alerts, top consolidation opportunities, upcoming re-vets.
Runs: Scheduled weekly.
🔒 Summarizes deterministic output; adds no new judgments.
Regulatory Watch◌ FUTURE STATE · build #5
Monitors privacy-law changes across the group’s jurisdictions and flags which approved vendors now have a coverage gap for an affected country.
Runs: Scheduled weekly scan + on-demand.
🔒 Reports a jurisdiction gap; never re-scores. Gap → human decision.
Lifecycle Sentinel◌ FUTURE STATE · build #6
Watches vendor news the policy can’t show — product retirements, acquisitions, breaches, renames — and drafts a cited override or re-vet proposal for reviewer sign-off.
Runs: Scheduled weekly per catalog vendor + before any re-vet.
🔒 Researches and proposes; only a named human applies an override, and the engine re-scores.
Repository Copilot◌ FUTURE STATE · build #7
Natural-language Q&A over the catalog and reports — “which approved apps have an unclear AI-training gate?” — with citations to app, question and quote.
Runs: On demand.
🔒 Quotes deterministic output; never re-scores.
Portfolio Analyst◌ FUTURE STATE · build #8
Turns the overlap math into leadership-ready recommendations — which duplicate apps to consolidate and what it saves per school per year.
Runs: Folded into the Governance Brief.
🔒 Narrates existing deterministic math; adds no new numbers.
Future-state agents are roadmap scope — named, designed and sequenced, not yet running. They ship during rollout, tailored to each region’s workflow.