Skip to content

Interaction Patterns

This specification documents the five multi-persona interaction patterns that govern how personas communicate within the FCC framework. Each pattern is defined by a relationship type in the cross-reference matrix and has distinct semantics for message flow, ownership transfer, and workflow control.

Pattern 1: Handoff

A handoff transfers a completed deliverable from one persona to another. Ownership changes at the handoff boundary -- the source persona has finished its contribution, and the target persona takes responsibility.

Sequence Diagram

sequenceDiagram
    participant RC as Research Crafter
    participant BC as Blueprint Crafter
    participant DE as Documentation Evangelist

    RC->>RC: Compile research inventory
    RC->>BC: Handoff: Research inventory with annotated references
    Note right of BC: Ownership transfers to BC
    BC->>BC: Create blueprint from research
    BC->>DE: Handoff: Blueprint for review
    Note right of DE: Ownership transfers to DE

Semantics

Property Value
Direction Unidirectional (source to target)
Ownership Transfers from source to target
Trigger Source completes its deliverable
Blocking Target cannot proceed without the handoff
Cross-reference count 48 entries across all 24 personas

When to Use

Use handoff when one persona produces an artifact that another persona needs to do its work. The Research Crafter hands off the research inventory to the Blueprint Crafter because the Blueprint Crafter cannot design a blueprint without the research.

Pattern 2: Feedback

A feedback relationship sends evaluation, corrections, or observations back toward the producing persona. Feedback does not transfer ownership -- it informs the source so it can improve.

Sequence Diagram

sequenceDiagram
    participant BC as Blueprint Crafter
    participant DE as Documentation Evangelist
    participant BC2 as Blueprint Crafter (Revision)

    BC->>DE: Handoff: Blueprint for review
    DE->>DE: Evaluate against quality standards
    DE->>BC2: Feedback: Standards gaps and edit suggestions
    Note left of BC2: Ownership remains with BC
    BC2->>BC2: Revise blueprint
    BC2->>DE: Handoff: Revised blueprint

Semantics

Property Value
Direction Reverse flow (target back to source)
Ownership Remains with original producer
Trigger Reviewer identifies issues or improvements
Blocking Optional (severity-dependent)
Cross-reference count 24 entries across all 24 personas

Feedback Loop Termination

Feedback loops must terminate to prevent infinite cycles. FCC uses three termination strategies:

  1. Iteration cap -- Maximum number of revision cycles (typically 2-3)
  2. Quality threshold -- Loop exits when quality gate score exceeds a defined threshold
  3. Severity filter -- Only error-severity findings trigger another revision; warning and info are noted but do not block
sequenceDiagram
    participant BC as Blueprint Crafter
    participant DE as Doc Evangelist

    loop Max 3 iterations
        BC->>DE: Submit blueprint
        DE->>DE: Evaluate quality
        alt Quality score >= threshold
            DE->>BC: Approved
        else Quality score < threshold
            DE->>BC: Feedback with findings
            BC->>BC: Revise
        end
    end

Pattern 3: Coordination

A coordination relationship describes two personas that share information bidirectionally. Neither owns the other's deliverable. They align on standards, resolve conflicts, or cross-link artifacts.

Sequence Diagram

sequenceDiagram
    participant RB as Runbook Crafter
    participant UG as User Guide Crafter

    RB->>UG: Share operational step references
    UG->>RB: Share user-facing quick-fix procedures
    Note over RB,UG: Bidirectional synchronization
    RB->>RB: Update runbook with UG cross-links
    UG->>UG: Update guide with RB cross-links

Semantics

Property Value
Direction Bidirectional
Ownership Shared or separate (each owns their deliverable)
Trigger Either persona updates their deliverable
Blocking Non-blocking (coordination is advisory)
Cross-reference count 16 entries across all 24 personas

Common Coordination Pairs

Pair What They Coordinate
RB + UG Operational procedures and user quick-fixes
CIA + STE Index schemas and taxonomy definitions
DGS + STE Data schemas and semantic taxonomy
CO + RS Timelines and scheduling
PTE + STE Privacy classification and semantic taxonomy

Pattern 4: Governance

A governance relationship represents oversight. The source persona reports compliance status to the target. Unlike feedback, governance relationships carry authority -- they can block downstream progress.

Sequence Diagram

sequenceDiagram
    participant DGS as Data Governance Specialist
    participant PTE as Privacy Taxonomy Engineer
    participant AMS as Anti-fact Mitigation Specialist
    participant GCA as Governance Compliance Auditor

    DGS->>GCA: Governance: Data governance compliance status
    PTE->>GCA: Governance: Privacy compliance status
    AMS->>GCA: Governance: Content validation results
    GCA->>GCA: Aggregate compliance verdicts
    alt All compliant
        GCA->>SCP: Approved for publication
    else Non-compliant
        GCA->>DE: Remediation required
    end

Semantics

Property Value
Direction Source to governance authority
Ownership Source retains artifact ownership
Trigger Compliance checkpoint in the workflow
Blocking Yes -- governance failures block publication
Cross-reference count 6 entries (DGS, PTE, AMS each report to GCA)

The Governance Pipeline

Governance personas operate in a pipeline where each specialist evaluates a different aspect, and the Governance Compliance Auditor (GCA) aggregates the results:

graph TD
    DGS[Data Governance Specialist] -->|Data compliance| GCA[Governance Compliance Auditor]
    PTE[Privacy Taxonomy Engineer] -->|Privacy compliance| GCA
    AMS[Anti-fact Mitigation Specialist] -->|Factual accuracy| GCA
    GCA -->|Compliance verdict| DE[Documentation Evangelist]
    GCA -->|Audit report| CO[Collaboration Orchestrator]

Pattern 5: Champion-Of

A champion-of relationship represents the elevation of a base persona. The champion coordinates and amplifies the base persona's work by orchestrating a team of related personas.

Sequence Diagram

sequenceDiagram
    participant RCHM as Research Crafter Champion
    participant RC as Research Crafter
    participant CIA as Catalog Indexer Architect
    participant STE as Semantic Taxonomy Engineer
    participant RIC as Research Inventory Crafter

    RCHM->>RC: Orchestrate core research
    RCHM->>CIA: Orchestrate catalog indexing
    RCHM->>STE: Orchestrate taxonomy engineering
    RCHM->>RIC: Orchestrate research automation
    RC-->>RCHM: Research findings
    CIA-->>RCHM: Indexed catalog
    STE-->>RCHM: Taxonomy definitions
    RIC-->>RCHM: Automated inventory
    RCHM->>RCHM: Unify research package
    RCHM->>BCHM: Handoff: Unified research package

Semantics

Property Value
Direction Champion to base persona (one-to-one elevation)
Ownership Champion coordinates; base persona executes
Trigger Workflow enters the champion's domain
Blocking Team members wait for champion orchestration
Cross-reference count 4 entries (one per champion)

Champion Teams

Champion Base Persona Orchestrates Domain
RCHM RC RC, CIA, STE, RIC Research (Find phase)
BCHM BC BC, BV, UMC, TS Design (Create phase)
UGCH UG UG, DE, SCP, EC Publishing (Critique/Publish)
RBCH RB RB, GCA, DGS, CO Operations (Governance)

Combined Pattern: Cross-Champion Workflow

In the complete 24-persona workflow, champions hand off to each other, creating a high-level orchestration layer above the individual persona interactions:

sequenceDiagram
    participant RCHM as Research Champion
    participant BCHM as Blueprint Champion
    participant UGCH as User Guide Champion
    participant RBCH as Runbook Champion

    RCHM->>RCHM: Orchestrate Find phase
    RCHM->>BCHM: Handoff: Unified research package
    BCHM->>BCHM: Orchestrate Create phase
    BCHM->>UGCH: Handoff: Validated blueprints
    BCHM->>RBCH: Handoff: Operational blueprints
    par Publishing Track
        UGCH->>UGCH: Orchestrate user documentation
    and Operations Track
        RBCH->>RBCH: Orchestrate operational procedures
    end
    RBCH->>BCHM: Feedback: Operational findings
    UGCH->>BCHM: Feedback: Usability findings

Relationship Type Distribution

Across the 106 cross-reference entries, the relationship types are distributed as follows:

Relationship Type Count Percentage Primary Use
handoff 48 45% Deliverable transfer between phases
feedback 24 23% Quality improvement loops
coordination 16 15% Bidirectional synchronization
governance 6 6% Compliance oversight
champion-of 4 4% Persona elevation
orchestration handoffs 8 7% Champion-to-team coordination