Three capability dimensions — Risk, Operations, and Oversight. Risk is the weakest at sixty-three point four. This is not a single member's gap — it's the average across the whole team. Eight members scoring below seventy on Risk. This is where Isabella needs to focus her next development cycle.

Thirteen members. Oliver Grant — AI Governance Lead — at eighty-eight, the highest in the team. Four Navigator sessions this month, five courses completed. Down at the bottom, Sophie Laurent — Internal Auditor — registered but no baseline. No HRI, no Navigator access, no courses. She's been provisioned by the domain auto-provisioning rule. The platform is waiting for her to complete Module 0.

HRI broken down by function. Risk and Technology at the top — the team's most advanced learners. HR and Procurement at the bottom, both in Developing band. Six HR and Procurement members combined with average HRI below sixty. That's where the team's Risk capability gap is concentrated.

Thirteen Navigator queries this month across the team. Every query grounded in the platform's scenario library, standards index, and regulatory feeds. Twelve distinct learners active in the last thirty days.

This is what a Navigator query looks like in the log. Oliver Grant — the team's highest-scorer — asked about EEOC obligations for a credit model flagging minority zip codes. The response grounded in two indexes: the regulatory standards library and the scenario bank. Latency: under two seconds. The query, the response, his HRI at query time, and the timestamp are all in the audit record.

One button. Everything the regulator needs.

Scope, date range, four data types. She clicks generate.

In under ninety seconds.

Section one: every member's HRI for the full period. The trajectory. Where they started, where they are now. Oliver Grant at eighty-eight — started at fifty-eight in January. Sophie Laurent with no score — the platform flags her automatically so the regulator can see she is registered but unscored.

Section two: the capability profile. Risk at sixty-three point four — the team's weakest dimension — with eight members named individually. Not an average hiding a problem. Eight specific people who need targeted Risk capability development before the next review.

Section three: the decision audit trail. Every Navigator query, every response, every learner's HRI at the moment they asked. The source indexes. The timestamp. This is the link between the AI-generated guidance and the human decision — documented, timestamped, and ready for the regulator.

This is the Readiness Control Plane. Not a report Isabella runs before a review — a live picture she checks any time. Every member scored. Every capability gap surfaced. Every Navigator decision logged. The same view she sees today is what she hands to the regulator next month.

Five components. Identity. Intake. Orchestration. Learning delivery. And the readiness analytics layer — the scores, signals, and audit evidence that turn learning activity into regulatory proof.

Operations. Manager and decision owner.

And her decision context: reviewing AI-generated lending risk scores. Four answers. That's everything the Orchestration Engine needs.

The Orchestration Engine runs immediately. Four steps. Decision context, capability mapping, path manifest, enrollment. Path ID: finserv-ops-mgr-v1. Built for her specific combination of industry, function, and role.

Jordan's catalogue — filtered by her intake profile. Financial services courses only. No healthcare, no public sector. Each Start button opens that course's Module 0 before the content is accessible. This is how the baseline is set.

Module 0 runs before the course content opens. Five scenarios drawn from this course's specific subject domain — lending risk, compliance obligations, AI oversight. Not generic AI questions. Jordan's answers establish her HRI baseline for this course.

Each scenario presents a real decision context. Not abstract theory — the exact type of situation Jordan faces when an AI model flags something and she has to decide what to do with it.

Five scenarios. Each one testing a different aspect of her decision context.

Twenty-six. Beginner band. Knowledge component ten point four out of forty. Decision component fifteen point six out of sixty. Her HRI is now live on the platform — and on Isabella's org dashboard. And at this exact moment, the Decision Navigator has unlocked. She can access it now, regardless of her score.

After Module 0, Jordan is taken directly into the course content. The platform generates a single-use auto-login for the learning platform — no second login prompt. She lands on the course.

Her path has three modules. The first two are foundations. The third is specific to her role — Operations, Financial Services, decision owner.

This is the content that builds toward her certification. Each module she completes moves her HRI. Each scenario generates evidence. Her progress is not just a completion record — it's the audit trail.

Jordan's current HRI is forty-four — Developing band. This is after two courses completed since her Module 0 baseline of twenty-six. She's moved eighteen points since she started.

Three capability dimensions. Risk is the weakest at forty-one — the same pattern visible across the whole Pantheon team. The platform has already surfaced her top gap and queued the recommended next course.

Three data points. Module 0 baseline at twenty-six in January. First course completion moving her to thirty-five in February. Second course to forty-four in March. The trajectory is clear — and the platform knows what she needs to do next to keep it moving.

And her regulatory framework scores — NIST AI RMF, ISO 42001, OECD Principles, UNESCO Ethics. All in the Developing range, consistent with her overall HRI. These are the scores that appear in Isabella's evidence pack.

The Navigator has been accessible to Jordan since the moment she completed Module 0. She's been using it alongside her courses.

She's back in her workflow. A lending risk score has come in — AI-generated, flagged for human review. She opens the Navigator and asks: what should I check before signing off?

The response is calibrated to her role, her industry, and her current HRI level. Four specific checks — not generic AI safety advice, but the verification standard for a loan officer in financial services acting on an AI-generated risk score. Grounded in the regulatory standards index and the scenario bank.

The query, the response, Jordan's identity, her HRI at the time, and the sources used — all logged automatically. When Isabella generates the evidence pack next month, this query is in Section three of that document.

Click into any client and you see exactly what their compliance lead sees. Pantheon Financial — enterprise, thirteen members, average sixty-six. Four Advanced learners. Thirteen Navigator queries this month. Priya can see this without asking Isabella for a report.

Back to the portfolio view. Twenty-six members in the Developing band — the largest group. Fourteen Intermediate. Six Advanced. Eleven Beginner. This is the portfolio's capability maturity picture in one chart.

Navigator usage by client. Pantheon leads with thirteen sessions — also the highest average HRI in the portfolio. Clearwater at zero sessions and thirty-five HRI. The pattern is clear: learners with higher HRI use the Navigator more. Higher engagement drives higher scores. Priya can show this correlation to any prospect.

The full Azure stack. Eighty-three cents this month across four live services. GPT-4o at fifty-nine percent — every Navigator query runs through it. Four AI Search indexes covering scenarios, standards, learning content, and regulatory feeds. Four thousand seven hundred and thirty-eight documents grounding every response. Zero errors this month.

Full white-label. Platform name, logo, color palette — all configurable. What the client sees is a product that looks like it was built by Priya's firm.

Logo, primary and secondary colors. The preview updates live.

Custom domain, auto-provisioned SSL, custom email sender. End clients log in at readiness dot PartnerCo dot com. Every notification comes from PartnerCo's domain. The infrastructure is AITrust Readiness — the experience is entirely theirs. Priya's firm is selling an AI governance practice, not a software licence. The platform is the delivery infrastructure behind that practice.

The standard library ships with one hundred and sixty-five scenarios across regulated verticals. But Pantheon's compliance team has internal policies that aren't in the standard library. Priya can upload those directly.

SCORM, xAPI, or PDF. She selects Pantheon as the target tenant. The content applies only to Pantheon — no other client sees it.

And she maps it to the capability dimensions it addresses, with weighting. Pantheon's weakest dimension is Risk at sixty-three point four. She weights this custom content heavily toward Risk. When this module is scored, it moves the needle on the specific dimension the team is weakest on. The HRI score reflects what the content actually trains — not a generic average.

This is what the partner model looks like at scale. Not one client's compliance problem — a practice running continuously across six clients, five industries, and thirty Navigator queries a month.

The same five-component architecture that powers a single org deployment powers the multi-tenant partner deployment. All isolated per tenant. All manageable from one partner portal. Priya's firm builds the practice. The platform runs it.