Lead author: Ethan Seow (C4AIL) Contributors: Dominic Ligot (CirroLytix), James Stanger (CompTIA), Chiew Farn Chung (ClassDo) Status: First Draft — March 2026

6.1 Before and After: The Compliance Officer

To make the HR redesign concrete, consider a single role through the Four-Column lens — the Compliance Officer from section 2.4.

Before (pre-AI): The Compliance Officer spends roughly 40% of her time scanning regulatory updates, drafting gap analyses, and writing compliance reports (intellectual labour). Another 10% on site inspections (physical). The remaining 50% is a blend of interpretation, enforcement decisions, and audit design — but HR measures her on reports produced, audits completed, and hours logged. Her performance review rewards volume. Her compensation is pegged to seniority. Her career path is Analyst → Senior → Manager → Director, each step measured by scope (more reports, more audits, bigger team).

After (AI-augmented): AI handles the regulation scanning, gap analysis, and report drafting — the 40% that was intellectual labour. Her site inspections continue. Her role now centres on the 30% that was always the real value but was never measured: interpreting regulatory ambiguity where the answer is not in the text, making enforcement decisions that balance compliance against business reality, and judging when a technical pass actually signals systemic risk. She also takes on new work: designing the compliance automation architecture and the audit trail that proves the AI-generated compliance reports are trustworthy.

The HR system must change to match:

Dimension Before After
Performance metrics Reports produced, audits completed, hours logged Judgment accuracy (did her interpretations hold up?), architecture quality (does her compliance engine work?), escalation hit rate (when she flags something, is she right?)
Compensation basis Seniority + scope Domain expertise premium + verified outcome metrics
Career path Linear: more reports → bigger team Branching: Depth (domain expert in regulatory interpretation) or Architecture (compliance system designer)
Development investment Annual compliance update course Co-creation with AI under senior regulatory counsel, portfolio of judgment calls reviewed by peers, Guildhall participation

The volume metrics she was measured on — reports per quarter, audits per year — measured her intellectual labour output. That output is now AI’s job. If the HR system still measures it, it will either measure the AI’s productivity (meaningless) or incentivise her to bypass the AI and do the work manually (counterproductive). The new metrics must measure what she actually contributes: the judgment, the intent, the accountability.

6.2 Performance Management

The Compliance Officer example generalises across roles. The measurement system must align with the labour type, not the job title.

Floor Users are measured on validation accuracy (do they catch AI errors?), interrogation quality (do they ask the right questions?), and throughput (do they maintain pace within structured workflows?).

Architects are measured on template quality (do their designs work?), specification maintainability (can others use and extend their work?), and verification engine effectiveness (does the system catch what it should catch?).

Orchestrators are measured on system-level output (does the AI-augmented workflow produce verified value?), pipeline health (are Architects developing? Are juniors getting judgment reps?), and adaptation speed (how quickly does the system respond to changes?).

What nobody is measured on: Hours worked. Volume of AI output generated. Number of prompts run. These metrics incentivise intellectual labour production — the exact thing being commoditised. Measuring prompts-per-day is like measuring keystrokes-per-hour in the typing pool.

6.3 Compensation

The compensation model reflects the shift in labour value.

Floor roles: Stable, predictable compensation with domain-expertise premiums. The Floor User with 20 years of regulatory knowledge is more valuable than the Floor User who can write better prompts, because domain knowledge is the validation substrate.

Architect roles: Premium compensation for architectural capability, tied to system output rather than individual productivity. The Architect who builds a verification engine that saves 10,000 review hours is compensated for the system outcome, not the hours they personally worked.

Orchestrator roles: Significant premium, performance-linked to verified business outcomes. The Orchestrator is the scarcest role and the highest-leverage — their value comes from designing systems that govern workflow quality at scale, not from personal output.

The Translator premium: Bilingual capability (domain + AI fluency) attracts a measurable salary premium — early market data suggests 15-25%, varying by sector and geography (Lightcast/Revelio Labs). The premium exists because the capability is genuinely scarce and immediately valuable.

6.4 Career Paths

Three legitimate tracks, none subordinate to the others:

The Depth Track: Floor User → Senior Floor User → Domain Expert. For professionals who choose mastery within their domain and do not seek architectural or leadership roles. This is “The Choice to Have a Life” — operationalised as a legitimate career track with its own compensation ladder and recognition structure.

The Architecture Track: Floor User → Translator → Architect → Orchestrator. For professionals who develop both technical and accountability capability. The critical pipeline for organisational AI maturity.

The Capability Track: Any level → Trainer. For professionals who have crossed the accountability threshold and can develop others. This track requires demonstrated accountability, not just technical expertise.

Promotion criteria: Portfolio-based, not tenure-based. The AI Guildhall provides the portfolio platform (Level 3 Submissions, Level 4-5 Reviews). CompTIA certifications provide objective technical waypoints. But advancement to Ceiling roles requires demonstrated accountability — evidence that you have made consequential decisions and lived with the results.

6.5 Governance Model — Who Decides What

The Five Roles model creates a governance question: who has authority over verification standards, triage thresholds, and AI deployment decisions? The answer requires separating three layers of governance that most organisations currently conflate.

Layer 1: Departmental line management (unchanged). Each department manages its own people, budgets, and priorities. Floor Users report to their departmental managers. This layer is not disrupted by the Five Roles model — it is extended.

Layer 2: AI governance function (new). Orchestrators (and senior Architects) form a cross-functional governance body responsible for verification standards, Queue A/B/C triage thresholds, Logic Pipe design review, and AI deployment approval. This function is analogous to an internal audit function or a clinical governance board — it sets standards that departments must meet, but does not manage departmental operations. The governance function reports to the CAIO or equivalent executive sponsor.

Layer 3: Capability development (new). Trainers operate with dual reporting — to their departmental line manager for operational work, and to the capability development function for their development responsibilities. This dual-reporting structure is standard in matrix organisations (clinical educators in hospitals report to both the ward and the education directorate). The critical design principle: separate the authority to set verification standards (governance function) from the authority to develop people (capability function). Combining them creates a single point of failure — and concentrates too much power in one role.

Conflict resolution: When departmental priorities conflict with governance standards — e.g., a department wants to bypass verification steps to meet a deadline — the escalation path runs to the executive sponsor (CAIO or equivalent). The governance function has veto authority on verification standards but not on business priorities. This mirrors the relationship between a CFO’s financial controls and operational departments: the controls are non-negotiable, but what gets funded is a business decision.