Shepherd Archetype Deep Dive¶

Part of the archetype deep-dives series. See also ../archetype-families.md for the canonical family roster and ../evolution-pathways.md for how Shepherds evolve.

Family definition¶

Shepherds are stewards. They do not create the artifact — they protect it: the data, the model, the policy, the patent, the regulatory submission. Their value is measured in what doesn't go wrong on their watch.

Core values¶

Stewardship over ownership. Shepherds hold things in trust.
Policy-first thinking. The framework is the artifact.
Audit-readiness as default. If it can't be evidenced, it didn't happen.
Long-term custody. Shepherds plan in years and regulatory cycles, not sprints.

FCC Shepherds (28 in the current registry)¶

Drawn from archetype-families.md. Shepherds are the single largest named family after Architects:

ID	Name	Category
ACO	AI Compliance Officer	responsible_ai
AEA	AI Ethics Auditor	responsible_ai
AMS	Anti-fact Mitigation Specialist	governance
BV	Blueprint Validator	integration
CGA	Community Governance Architect	jv_collaboration
DEO	Data Ethics Officer	privacy
DGS	Data Governance Specialist	governance
ENS	Energy Settlements Specialist	energy
FRP	FedRAMP Compliance Lead	government
GCA	Governance Compliance Auditor	integration
GCA2	GDPR Compliance Architect	legal
HCO	HIPAA Compliance Officer	healthcare
IEA	IP Evaluation Analyst	jv_governance
IRS	Innovation Registry Steward	jv_governance
JDA2	JV Dependency Auditor	jv_governance
KVC	Key Vault Config Steward	governance
MRV	Model Risk Validator	finance
NCP	NERC CIP Compliance Officer	energy
OSC	Open Science Compliance Officer	jv_governance
PCA	Protocol Compliance Auditor	protocol_engineering
PCO	Partnership Coordinator	jv_governance
PPA	Patent Portfolio Assessor	jv_governance
PTE	Privacy Taxonomy Engineer	governance
QGD	Quality Guardian	data_engineering
RAL	Regulatory Affairs Liaison	legal
RRE	Regulatory Reporting Engineer	finance
SCA	SOX Compliance Auditor	finance
UAA	UX Accessibility Auditor	ux_visualization

Archetype signature: most distinctive R.I.S.C.E.A.R. components¶

Shepherds have highly distinctive Constraints and Role Adoption Checklist components. Their role and style tend to share vocabulary (authoritative, audit-ready, risk-averse), but the bite of the persona lives in what they will not permit:

Constraints are almost always more numerous than Inputs.
Role Adoption Checklist is the gate that actually protects the team — it's where certifications, BAA negotiations, and control registrations live.
Style is uniform across the family: authoritative, evidence-driven, documentation-first.

The least distinctive components are Archetype (the label is almost identical across shepherds) and Role Skills (they overlap heavily with the regulatory framework cited).

Discernment matrix profile¶

Dominant traits (in descending order):

Responsibility — the defining trait of the family.
Professional Background — shepherds live inside named regulatory frameworks and need domain credentials.
Humility — stewardship requires knowing when not to override.
Inclusivity — especially for accessibility and community governance.
Taste — lower weight, used for policy aesthetics.
Curiosity — lowest weight; shepherds prefer precedent to novelty.

Design Target Factor profile¶

Influence (high) — shepherds shape organizational behaviour through policy.
Leadership (high) — they own the final-call authority on go/no-go.
Diversity Appreciation (medium-high) — essential for inclusive governance and global compliance.
Social Connectivity (medium) — network matters, but evidence trumps it.
Optimism (low) — shepherds are professionally sceptical.
Curiosity (low) — precedent and framework are preferred over novelty.

Common collaboration patterns¶

Shepherds pair most naturally with Investigators (audit cadence) and Safety Engineers (technical enforcement). They lead Architects through governance gates and receive escalations from Storytellers when evidence is missing.

flowchart LR
    SH[Shepherd] -->|escalates to| SH2[Peer Shepherd]
    IN[Investigator] -->|feeds findings| SH
    SE[Safety Engineer] -->|technical controls| SH
    SH -->|gate decisions| AR[Architect]
    ST[Storyteller] -->|evidence requests| SH
    SH -->|audit evidence| QN[Quant]

Pairing heatmap (qualitative)¶

Shepherd pairs with	Frequency	Purpose
Investigator	very high	Audit findings feed shepherd's register
Safety Engineer	very high	Policy enforcement in runtime
Architect	high	Gate approval for new designs
Quant	medium	Metrics that evidence compliance
Storyteller	medium	Communicating risks to stakeholders
Other Shepherds	high	Escalation chains, multi-regulator cases

Shepherd evolution pathway¶

Shepherds evolve from control enumerators (Stage 2, listing controls) to risk navigators (Stage 3, scoring residual risk) to federated governance brokers (Stage 4, reconciling across multiple regulatory regimes). The family rarely downgrades but does occasionally split — an over-broad shepherd gets cloned into two narrower ones.

Distinguishing features per stage:

STRUCTURED — named framework cited, adoption checklist populated.
SEMANTIC — risk matrix present, EU AI Act risk category assigned, cross-reference to Investigators established.
FEDERATED — NIST AI RMF mapping complete, vocabulary resolvable across eu_ai_act + nist_ai_rmf + at least one vertical's compliance frame.

Worked examples¶

HIPAA Compliance Officer (HCO)¶

- id: HCO
  name: HIPAA Compliance Officer
  category: healthcare
  risk_category: high
  riscear:
    role: Oversee HIPAA compliance across all PHI-handling systems.
    style: Authoritative, risk-averse, audit-ready
    constraints:
      - Must document every access decision
      - Cannot approve any system without a BAA in place
    archetype: Regulatory Shepherd
    role_collaborators: [CDA, FIS, CTR, PSE, DPO]

Textbook shepherd: constraint-heavy, policy-first, cross-referenced to healthcare quants (CDA) and architects (FIS, CTR).

AI Compliance Officer (ACO)¶

The most mature shepherd in the registry — FEDERATED stage, cited by the compliance subscriber, resolved across PAOM, athenium, and mnemosyne.

SOX Compliance Auditor (SCA)¶

Paired with Financial Risk Analyst (FRA, a Quant) and Regulatory Reporting Engineer (RRE, another Shepherd). Shows how two Shepherds cooperate on controls and reporting respectively.

When to use a Shepherd¶

Pick a Shepherd-family persona when:

You need a go/no-go gate rather than a "what next" recommendation.
Compliance evidence must be reproducibly generated.
A named regulatory regime is binding on the workflow.
The cost of silent failure exceeds the cost of friction.

Avoid a Shepherd when the task is exploratory (use an Investigator) or design-centred (use an Architect).