Persona Interaction Atlas¶
A comprehensive map of all 102 core personas showing cross-reference relationships, collaboration patterns, and interaction flows across the FCC ecosystem.
Overview¶
The FCC framework defines 102 core personas across 20 categories, connected by 106+ cross-reference entries across 5 relationship types. This atlas provides a visual and structured guide to how personas interact.
Relationship Types¶
| Type | Symbol | Description | Count |
|---|---|---|---|
| Handoff | → |
Forward transfer of deliverables between phases | ~40 |
| Feedback | ← |
Backward quality improvement loop | ~25 |
| Coordination | ↔ |
Peer-level lateral interaction | ~20 |
| Governance | ⊳ |
Compliance monitoring and oversight | ~12 |
| Champion-of | ★ |
Elevation from champion to base persona | ~9 |
Category-by-Category Interaction Map¶
Core Personas (5)¶
┌─────────┐
│ RC │ Research Crafter
│ Find │
└────┬────┘
│ handoff (research inventory)
v
┌──────────┴──────────┐
│ │
┌────┴────┐ ┌────┴────┐
│ BC │ │ UG │ User Guide Crafter
│ Create │ │ Create │
└────┬────┘ └────┬────┘
│ │
│ handoff │ feedback
v v
┌─────────┐ ┌─────────┐
│ RB │ │ DE │ Documentation Evangelist
│ Create │ │ Create │
└─────────┘ └─────────┘
Key interactions: - RC → BC: Research findings flow to blueprint design (handoff) - RC → UG: Research summaries inform user guide content (handoff) - BC → RB: Blueprint specs guide runbook creation (handoff) - DE ← BC: Documentation standards feedback to blueprints (feedback) - DE ↔ UG: Standards alignment and content consistency (coordination)
Integration Personas (8)¶
┌─────────┐ ┌─────────┐ ┌─────────┐
│ CIA │ │ STE │ │ RIC │
│ Catalog │ │Taxonomy │ │Research │
│ Indexer │ │Engineer │ │Inventory│
└────┬────┘ └────┬────┘ └────┬────┘
│ │ │
└──────────────┼──────────────┘
│ coordination
v
┌──────────────┴──────────────┐
│ │
┌────┴────┐ ┌────┴────┐
│ UMC │ │ TS │
│UI Mockup│ │Traceab. │
└────┬────┘ └────┬────┘
│ │
│ handoff │ handoff
v v
┌─────────┐ ┌─────────┐ ┌─────────┐
│ BV │ │ GCA │ │ PT │
│Blueprint│ │Governan.│ │Perform. │
│Validatr │ │Auditor │ │ Tuner │
└─────────┘ └─────────┘ └─────────┘
Key interactions: - CIA ↔ STE ↔ RIC: Knowledge structure coordination (coordination) - CIA → RC: Catalog structures inform research indexing (handoff) - STE → BC: Taxonomy feeds blueprint classification (handoff) - BV ← BC: Blueprint validation feedback (feedback) - GCA ⊳ all: Compliance monitoring across integration (governance)
Governance Personas (4)¶
┌─────────┐ ┌─────────┐
│ DGS │──────────│ PTE │
│ Data │ coordin. │Privacy │
│Governan.│ │Taxonomy │
└────┬────┘ └────┬────┘
│ governance │ governance
v v
┌─────────┐ ┌─────────┐
│ AMS │ │ KVCS │
│Anti-fact│ │Key Vault│
│Mitigat. │ │Config │
└─────────┘ └─────────┘
Key interactions: - DGS ⊳ all personas: Data governance oversight across entire framework - PTE → STE: Privacy taxonomy feeding semantic taxonomy (handoff) - DGS ↔ PTE: Governance policy coordination (coordination) - AMS → DE: Anti-fact findings inform documentation standards (handoff) - KVCS ⊳ technical personas: Configuration governance monitoring
Stakeholder Personas (5)¶
┌─────────┐
│ CO │ Collaboration Orchestrator
└────┬────┘
│ coordination
┌─────────┼─────────────────┐
│ │ │
v v v
┌───────┐ ┌───────┐ ┌───────┐
│ EC │ │ RS │ │ SCP │
│Execut.│ │Roadmap│ │Content│
│Commun.│ │Synch. │ │Publis.│
└───────┘ └───────┘ └───┬───┘
│
v
┌───────┐
│ SMC │
│ SAFe │
│Metrics│
└───────┘
Key interactions: - CO ↔ all stakeholders: Cross-team collaboration coordination - EC ← RC: Executive summaries from research findings (feedback) - RS → all: Roadmap alignment propagated across teams (handoff) - SCP → DE: Published content standards feedback (handoff)
Champion Personas (4)¶
★ RCHM ★ BCHM
Research Champion Blueprint Champion
├── RC (Find) ├── BC (Create)
├── CIA (Find) ├── BV (Critique)
├── STE (Find) ├── UMC (Create)
└── RIC (Find) └── TS (Create)
★ UGCH ★ RBCH
User Guide Champion Runbook Champion
├── UG (Create) ├── RB (Create)
├── DE (Create) ├── GCA (Critique)
├── SCP (Create) ├── DGS (Critique)
└── EC (Create) └── CO (Create)
Champion coordination flows: - Each champion coordinates 4 base personas via orchestration edges - Champions communicate laterally: RCHM ↔ BCHM (research-to-blueprint handoff) - Champions aggregate team outputs for cross-team review cycles - Champion-of relationship ensures champion evolves alongside base persona
Data Engineering Personas (6)¶
┌────────┐ ┌────────┐ ┌────────┐
│ SQC │───→│ TA │───→│ PO │
│SQL Qry │ │Transfrm│ │Pipeline│
└────────┘ └────────┘ └────┬───┘
│
┌──────────────────┤
│ │
┌────┴───┐ ┌────┴───┐
│ IS │ │ QG │
│Integr. │ │Quality │
└────────┘ │Guardian│
└────┬───┘
│
┌────┴───┐
│ AS │
│Automat.│
└────────┘
Key interactions: - SQC → TA → PO: Data pipeline construction chain (handoff) - IS → SQC: Integration specs inform query design (handoff) - QG ⊳ all data eng: Quality enforcement across pipeline (governance) - AS ↔ PO: Automation script ↔ pipeline orchestration (coordination)
ML Lifecycle Personas (9)¶
┌────────┐ ┌────────┐ ┌────────┐ ┌────────┐
│ DSA │───→│ EDAN │───→│ FA │───→│ MA │
│ Data │ │ EDA │ │Feature │ │ Model │
│Sourcing│ │Navigtr │ │Architct│ │Architct│
└────────┘ └────────┘ └────────┘ └────┬───┘
│
┌──────────────────┤
│ │
┌────┴───┐ ┌────┴───┐
│ ES │ │ IO │
│Experim.│ │Infernce│
│Scientst│ │Orchstr.│
└────────┘ └────┬───┘
│
┌──────────────┤
│ │
┌────┴───┐ ┌────┴───┐ ┌────────┐
│ IR │ │ IA │ │ MOS │
│Insight │ │Interpr.│ │ModelOps│
│Reportr │ │Analyst │ │Steward │
└────────┘ └────────┘ └────────┘
Key interactions: - DSA → EDAN → FA → MA: Model development pipeline (handoff) - ES ← MA: Experiment results refine architecture (feedback) - IO → IR + IA: Inference outputs split to reporting and analysis (handoff) - MOS ⊳ all ML: Model lifecycle governance (governance) - IA ← ES: Interpretability insights refine experiments (feedback)
ML Models Personas (11)¶
┌──────────────────────────────────────────────┐
│ Model Specialists │
│ │
│ NNS LRE GBTS RFA IFS │
│ Neural Logist. Grad. Random Isolatn │
│ Net Regress Boost Forest Forest │
│ │
│ DBS QLA SNNS CS CFE FS │
│ DBSCAN Q-Learn Siames Clustr Collab Forecst│
└──────────────────────────────────────────────┘
Key interactions: - All model personas ← MA: Model architecture specifications (feedback) - All model personas → ES: Experiment results for evaluation (handoff) - NNS ↔ SNNS: Neural architecture knowledge sharing (coordination) - CS ↔ DBS ↔ IFS: Clustering/anomaly detection coordination (coordination) - CFE ↔ CS: Recommendation and clustering synergy (coordination)
DevOps Personas (3)¶
- PB → DVE: Pipeline specs inform infrastructure setup (handoff)
- USS → PB: User stories drive pipeline requirements (handoff)
- DVE ↔ MOS: Infrastructure and ML ops alignment (coordination)
App Development Personas (2)¶
- AM ↔ UMC: App prototypes align with UI mockups (coordination)
- NCC → AM: Notebook collaboration patterns inform app design (handoff)
Specialized Personas (27)¶
Across 7 specialized categories:
| Category | Personas | Key Cross-Category Links |
|---|---|---|
| Open Science | OSA | OSA ↔ RC (research sharing) |
| Responsible AI | RAA | RAA ⊳ all ML (ethics oversight) |
| JV Collaboration | JSC, JDA | JSC ↔ CO (collaboration alignment) |
| Docs-as-Code | DPA, TSC | DPA → DE (pipeline standards) |
| Privacy | PIA | PIA ↔ PTE (privacy coordination) |
| Knowledge Graph | OA, KGB | OA → STE (ontology alignment) |
| Local-First AI | EDS, LMO | EDS ↔ DVE (edge deployment) |
Cross-Category Interaction Patterns¶
Research → Engineering Pipeline¶
RC (Find) → BC (Create) → PB (Build) → GCA (Critique) → DVE (Ops)
│ ▲
└── RCHM orchestrates ──────────────────┘
ML Model Development Flow¶
Governance Oversight Network¶
DGS ──⊳── All data-touching personas
PTE ──⊳── All privacy-relevant personas
GCA ──⊳── All compliance-critical personas
RAA ──⊳── All ML personas
KVCS ──⊳── All config-managing personas
Plugin Persona Interactions¶
┌──────────────┐
│ PAOM │ 13 personas
│ (Patterns) │
└──────┬───────┘
│
├── handoff ──→ FCC Core (pattern application)
│
┌──────┴───────┐ ┌──────────────┐
│ AOME │ ←──→│ CONSTEL │
│ (Vocabulary)│ │ (TMF KG) │
│ 5 personas │ │ 5 personas │
└──────────────┘ └──────────────┘
The CrossPluginOrchestrator validates the dependency triangle:
- PAOM provides pattern archetypes
- AOME provides vocabulary taxonomy alignment
- CONSTEL provides TMF knowledge graph relationships
- All three contribute personas via fcc.plugins.personas entry points
Upstream/Downstream Dependency Chains¶
Longest Upstream Chains (personas with most dependencies)¶
| Persona | Upstream Count | Key Upstream Personas |
|---|---|---|
| DE (Documentation Evangelist) | 6+ | RC, BC, UG, RB, SCP, all champions |
| GCA (Governance Compliance Auditor) | 5+ | DGS, PTE, BV, KVCS, RBCH |
| IO (Inference Orchestrator) | 4 | MA, ES, FA, DSA (transitive) |
| PO (Pipeline Orchestrator) | 3 | SQC, TA, IS |
Longest Downstream Chains (personas feeding most others)¶
| Persona | Downstream Count | Key Downstream Personas |
|---|---|---|
| RC (Research Crafter) | 8+ | BC, UG, CIA, RIC, EC, and transitive chain |
| MA (Model Architect) | 11 | All 11 ML Model specialists |
| DGS (Data Governance Specialist) | 10+ | All data-touching personas via governance |
| CO (Collaboration Orchestrator) | 5 | EC, RS, SCP, SMC, plus coordination |
Peer Collaboration Clusters¶
Personas that primarily interact via coordination (peer-level):
| Cluster | Personas | Domain |
|---|---|---|
| Research Cluster | RC, CIA, STE, RIC | Knowledge discovery and organization |
| Documentation Cluster | DE, UG, RB, SCP | Content creation and publishing |
| Governance Cluster | DGS, PTE, GCA, KVCS | Compliance and oversight |
| ML Pipeline Cluster | DSA, EDAN, FA, MA | Model development |
| ML Deployment Cluster | IO, IR, IA, MOS | Model operations |
| Infrastructure Cluster | PB, DVE, AS | Build and deploy |
Querying the Cross-Reference Matrix¶
The CrossReferenceMatrix class supports programmatic queries:
from fcc.personas.registry import PersonaRegistry
from fcc.personas.cross_reference import CrossReferenceMatrix
registry = PersonaRegistry.from_directory()
matrix = registry.cross_reference_matrix
# Find all downstream personas from Research Crafter
downstream = matrix.downstream("RC")
# Find all governance relationships
governance = matrix.by_type("governance")
# Find peers of Blueprint Crafter
peers = matrix.peers("BC")
# Find all upstream dependencies for a persona
upstream = matrix.upstream("DE")
# Query interactions between two specific personas
interactions = matrix.between("RC", "BC")
See GLOSSARY.md for definitions of all relationship types and persona IDs.