Cross-Reference Visualization

This page provides Mermaid graph visualizations of the 106 cross-reference entries across all 24 FCC personas. The visualizations are organized as subgraph views by persona category, followed by network analysis highlighting structural patterns.

Full Network Overview

The complete cross-reference graph shows all 24 personas and their interactions. Relationship types are color-coded by edge style.

graph TD
    %% Core Personas
    RC([RC - Research Crafter])
    BC([BC - Blueprint Crafter])
    DE([DE - Documentation Evangelist])
    RB([RB - Runbook Crafter])
    UG([UG - User Guide Crafter])

    %% Integration Personas
    CIA([CIA - Catalog Indexer])
    UMC([UMC - UI Mockup Crafter])
    STE([STE - Semantic Taxonomy])
    TS([TS - Traceability Specialist])
    BV([BV - Blueprint Validator])
    RIC([RIC - Research Inventory])
    GCA([GCA - Governance Auditor])

    %% Governance Personas
    DGS([DGS - Data Governance])
    PTE([PTE - Privacy Taxonomy])
    AMS([AMS - Anti-fact Mitigation])

    %% Stakeholder Personas
    CO([CO - Collaboration Orchestrator])
    SMC([SMC - SAFe Metrics])
    EC([EC - Executive Communicator])
    RS([RS - Roadmap Synchronizer])
    SCP([SCP - Content Publisher])

    %% Core handoffs
    RC -->|handoff| BC
    RC -->|handoff| DE
    RC -->|handoff| RB
    RC -->|handoff| UG
    BC -->|handoff| DE
    BC -->|handoff| RB
    BC -->|handoff| UG
    BC -->|handoff| BV
    BC -->|handoff| UMC
    DE -->|handoff| RB
    DE -->|handoff| UG
    DE -->|handoff| SCP

    %% Core feedback
    DE -.->|feedback| BC
    RB -.->|feedback| BC
    UG -.->|feedback| BC
    RB -.->|feedback| RC
    UG -.->|feedback| RC

    %% Core coordination
    RB <-->|coordination| UG

Subgraph: Core Personas

The 5 core personas form the backbone of the FCC cycle with dense handoff and feedback connections.

graph LR
    subgraph Find Phase
        RC([RC - Research Crafter])
    end

    subgraph Create Phase
        BC([BC - Blueprint Crafter])
        RB([RB - Runbook Crafter])
        UG([UG - User Guide Crafter])
    end

    subgraph Critique Phase
        DE([DE - Doc Evangelist])
    end

    RC -->|research inventory| BC
    RC -->|annotated references| DE
    RC -->|operational scenarios| RB
    RC -->|user pain points| UG

    BC -->|blueprints for review| DE
    BC -->|operational blueprints| RB
    BC -->|onboarding scaffolds| UG

    DE -->|operational docs| RB
    DE -->|user-facing docs| UG

    DE -.->|standards and edits| BC
    RB -.->|operational feedback| BC
    UG -.->|usability feedback| BC
    RB -.->|operational findings| RC
    UG -.->|user feedback| RC

    RB <-.->|cross-link procedures| UG

Key observations:

• RC has the highest out-degree among core personas (4 downstream handoffs)
• BC receives the most feedback (3 upstream feedback connections)
• DE bridges Create and Critique phases, feeding both RB and UG
• RB and UG have a bidirectional coordination relationship

Subgraph: Integration Specialists

The 7 integration personas connect the core workflow to specialized concerns.

graph TD
    subgraph Integration Cluster
        CIA([CIA - Catalog Indexer])
        STE([STE - Semantic Taxonomy])
        TS([TS - Traceability])
        BV([BV - Blueprint Validator])
        UMC([UMC - UI Mockup])
        RIC([RIC - Research Inventory])
        GCA([GCA - Governance Auditor])
    end

    subgraph Core
        RC([RC])
        BC([BC])
        DE([DE])
        UG([UG])
    end

    CIA <-->|align schemas| STE
    CIA -->|indexed assets| RC
    CIA -->|catalog data| BC
    CIA -->|coverage gaps| GCA

    STE -->|terminology| RC
    STE -->|classification| DGS
    STE <-->|validate terms| DE

    TS -.->|trace requirements| RC
    TS -.->|trace blueprints| BC
    TS <-->|validate coverage| BV
    TS -->|compliance gaps| GCA

    BV -.->|validation results| BC
    BV -->|quality issues| DE
    BV <-->|coverage checks| TS
    BV -->|verification results| GCA

    UMC -.->|visual prototypes| BC
    UMC -->|mockups for review| BV
    UMC -->|visual assets| UG
    UMC <-->|design patterns| DE

    RIC <-->|supplement research| RC
    RIC -->|structured data| BC
    RIC -->|capability data| CIA
    RIC -->|coverage gaps| TS

    GCA -.->|audit docs| DE
    GCA -.->|validation review| BV
    GCA -.->|traceability review| TS
    GCA -->|governance status| CO

Key observations:

• GCA is the governance hub, receiving compliance reports from 3 governance personas plus integration specialists
• CIA and STE have a strong bidirectional coordination relationship
• BV and TS form a validation pair, cross-checking each other's work
• RIC bridges the automated and manual research workflows

Subgraph: Governance Pipeline

The 3 governance personas plus GCA form a dedicated compliance pipeline.

graph LR
    DGS([DGS - Data Governance]) -->|data compliance| GCA([GCA - Governance Auditor])
    PTE([PTE - Privacy Taxonomy]) -->|privacy compliance| GCA
    AMS([AMS - Anti-fact Mitigation]) -->|validation results| GCA

    DGS -->|governance context| BC([BC])
    DGS <-->|align schemas| STE([STE])
    DGS -->|integration data| PTE

    PTE -.->|classification alignment| DGS
    PTE <-->|classification/taxonomy| STE
    PTE -->|classification context| AMS

    AMS -.->|factual accuracy| DE([DE])
    AMS -.->|sensitive content| PTE
    AMS -.->|blueprint accuracy| BC

    GCA -->|compliance verdict| DE
    GCA -->|governance status| CO([CO])

    style DGS fill:#ff9800,color:#000
    style PTE fill:#ff9800,color:#000
    style AMS fill:#ff9800,color:#000
    style GCA fill:#ff5722,color:#fff

Key observations:

• All three governance personas report to GCA via governance relationship type
• The pipeline flows DGS to PTE to AMS, with each adding a compliance layer
• GCA has the final authority to approve or reject via DE

Subgraph: Stakeholder Hub

The 5 stakeholder personas manage communication, metrics, and publication.

graph TD
    CO([CO - Collaboration Orchestrator])
    SMC([SMC - SAFe Metrics])
    EC([EC - Executive Communicator])
    RS([RS - Roadmap Synchronizer])
    SCP([SCP - Content Publisher])

    CO -->|status updates| EC
    CO <-->|timelines| RS
    CO <-->|doc handoffs| DE([DE])

    SMC -->|metrics| EC
    SMC -.->|coordination data| CO
    SMC -->|quality metrics| BV([BV])
    SMC -->|trends| RS

    EC -.->|receive metrics| SMC
    EC -.->|receive status| CO
    EC -->|exec packages| SCP
    EC <-->|messaging alignment| DE

    RS <-->|timelines| CO
    RS -.->|trend data| SMC
    RS -->|roadmap data| EC
    RS <-->|research milestones| RC([RC])

    SCP -.->|exec packages| EC
    SCP -.->|approved docs| DE
    SCP -.->|user guides| UG([UG])
    SCP -->|distribution metrics| CO

Key observations:

• EC is the central communication node, receiving from CO, SMC, and RS
• CO and RS have a strong bidirectional coordination for timeline management
• SCP is the terminal node for publication, receiving from multiple sources

Subgraph: Champion Orchestration Layer

The 4 champions form a high-level coordination layer.

graph LR
    subgraph Research Domain
        RCHM([RCHM - Research Champion])
        RC([RC])
        CIA([CIA])
        STE([STE])
        RIC([RIC])
    end

    subgraph Design Domain
        BCHM([BCHM - Blueprint Champion])
        BC([BC])
        BV([BV])
        UMC([UMC])
        TS([TS])
    end

    subgraph Publishing Domain
        UGCH([UGCH - User Guide Champion])
        UG([UG])
        DE([DE])
        SCP([SCP])
        EC([EC])
    end

    subgraph Operations Domain
        RBCH([RBCH - Runbook Champion])
        RB([RB])
        GCA([GCA])
        DGS([DGS])
        CO([CO])
    end

    %% Champion-of relationships
    RCHM ===|champion-of| RC
    BCHM ===|champion-of| BC
    UGCH ===|champion-of| UG
    RBCH ===|champion-of| RB

    %% Cross-champion handoffs
    RCHM -->|unified research| BCHM
    BCHM -->|blueprints| UGCH
    BCHM -->|operational specs| RBCH

    %% Cross-champion feedback
    BCHM -.->|receives research| RCHM
    RBCH -.->|operational findings| BCHM
    UGCH -.->|usability findings| BCHM

    style RCHM fill:#4CAF50,color:#fff
    style BCHM fill:#2196F3,color:#fff
    style UGCH fill:#9C27B0,color:#fff
    style RBCH fill:#FF5722,color:#fff

Key observations:

• BCHM is the most connected champion, receiving from RCHM and handing off to both UGCH and RBCH
• Each champion orchestrates exactly 4 personas (including its base persona)
• The champion layer mirrors the FCC cycle: Find (RCHM) to Create (BCHM) to Critique/Publish (UGCH) + Operations (RBCH)

Network Analysis

Most Connected Personas (by Total Degree)

Rank	Persona	In-Degree	Out-Degree	Total	Role
1	GCA	7	4	11	Governance hub -- receives from all compliance sources
2	BC	6	5	11	Central Create node -- receives research, sends blueprints
3	DE	5	5	10	Critique bridge -- reviews and publishes
4	BCHM	3	7	10	Design champion -- orchestrates largest team
5	RC	4	5	9	Research origin -- feeds all downstream personas

Hub-and-Spoke Patterns

Three personas act as hubs connecting otherwise separate clusters:

1. GCA -- Connects the governance cluster (DGS, PTE, AMS) to the core workflow (DE, CO)
2. DE -- Connects the Create phase (BC, RB, UG) to the governance and publication pipelines
3. BCHM -- Connects the Research Champion (RCHM) to both the Publishing Champion (UGCH) and Operations Champion (RBCH)

Bottleneck Analysis

A bottleneck is a persona whose removal disconnects significant parts of the graph:

Persona	Consequence if Removed	Mitigation
GCA	Governance personas lose their reporting target	Designate DE as backup governance receiver
DE	Create phase outputs cannot reach publication	Direct BC to SCP handoff as bypass
BCHM	Find phase cannot hand off to Create phase	Enable direct RCHM to BC handoff

Related Resources

• Cross-Reference Matrix -- Full data reference
• Interaction Patterns -- Pattern descriptions with sequence diagrams
• Archetype Analysis -- How archetypes shape interactions
• Interaction Cookbook -- Recipes for working with the matrix