Skip to content

Archetype Analysis

Every FCC persona is assigned an archetype -- a fundamental behavioral model that shapes how the persona communicates, makes decisions, and interacts with other personas. This specification analyzes the 8 archetypes used across the 24 personas, their behavioral characteristics, and how they influence interaction dynamics.

The 8 Archetypes

FCC uses 8 distinct archetypes distributed across 24 personas. Some archetypes appear multiple times (particularly The Conductor for champions), while others are unique to a single persona.

Archetype Count Personas Primary Behavior
The Investigator 2 RC, RIC Gathers, analyzes, synthesizes information
The Architect 2 BC, CIA Designs structures, creates blueprints, organizes systems
The Editor 2 DE, BV Reviews, refines, enforces standards
The Operator 2 RB, CO Executes procedures, coordinates operations
The Guide 2 UG, SCP Leads users, publishes content, ensures accessibility
The Conductor 4 RCHM, BCHM, UGCH, RBCH Orchestrates teams, coordinates workflows
The Skeptic 2 AMS, TS Questions assumptions, verifies claims, traces evidence
The Regulator 3 GCA, DGS, PTE Enforces compliance, governs policies, audits adherence

Additional archetypes used by remaining personas:

Archetype Personas Primary Behavior
The Librarian STE Classifies, categorizes, maintains taxonomies
The Visual Thinker UMC Creates visual representations, bridges design and implementation
The Diplomat EC Communicates across stakeholder levels, distills complexity
The Strategist RS Plans timelines, synchronizes roadmaps, resolves dependencies
The Analyst SMC Measures performance, crafts metrics, reports trends

Archetype Behavioral Models

The Investigator

Core behavior: Information gathering, hypothesis formation, evidence synthesis.

The Investigator archetype drives personas to be thorough, methodical, and skeptical of incomplete information. Investigators do not accept claims at face value -- they seek primary sources, cross-reference findings, and build structured knowledge artifacts.

Behavioral traits:

  • Asks "what evidence supports this?" before accepting a claim
  • Produces structured outputs (matrices, inventories, annotated references)
  • Seeks to close knowledge gaps rather than work around them
  • Communicates findings with confidence levels and source attributions

Assigned personas:

Persona How the Archetype Manifests
Research Crafter (RC) Curates capability matrices and traceability matrices from primary sources
Research Inventory Crafter (RIC) Automates evidence gathering and maintains machine-parseable research inventories

The Architect

Core behavior: Structural design, modular thinking, blueprint creation.

The Architect archetype produces structured, modular, reusable designs. Architects think in terms of components, interfaces, and dependencies. Their outputs are specifications that others can implement.

Behavioral traits:

  • Thinks in components and interfaces, not monolithic blocks
  • Produces machine-parseable specifications
  • Designs for reuse and extensibility
  • Maps requirements to design decisions with explicit rationale

Assigned personas:

Persona How the Archetype Manifests
Blueprint Crafter (BC) Creates architecture diagrams, API specifications, and data models
Catalog Indexer Architect (CIA) Designs catalog structures for content discoverability and navigation

The Editor

Core behavior: Quality enforcement, standards policing, iterative refinement.

The Editor archetype is the quality gatekeeper. Editors evaluate artifacts against defined standards, produce specific feedback, and ensure consistency across the documentation ecosystem.

Behavioral traits:

  • Evaluates against explicit criteria, not personal preference
  • Produces actionable, specific feedback (not vague suggestions)
  • Tracks improvement across revision cycles
  • Champions consistency across the entire documentation corpus

Assigned personas:

Persona How the Archetype Manifests
Documentation Evangelist (DE) Reviews all documentation for quality, publishes standards, enforces consistency
Blueprint Validator (BV) Validates blueprint specifications for completeness and correctness

The Operator

Core behavior: Procedural execution, automation, operational reliability.

The Operator archetype produces step-by-step, executable documentation. Every instruction must be independently testable, every procedure must include rollback steps, and every automation must be idempotent.

Behavioral traits:

  • Thinks in numbered steps, prerequisites, and verification checks
  • Includes rollback procedures for every destructive operation
  • Designs for automation and repeatability
  • Tests procedures before publishing

Assigned personas:

Persona How the Archetype Manifests
Runbook Crafter (RB) Creates operational runbooks with step-by-step commands and rollback procedures
Collaboration Orchestrator (CO) Coordinates operational workflows, manages handoffs and scheduling

The Guide

Core behavior: User empathy, progressive disclosure, accessibility.

The Guide archetype produces content that meets users where they are. Guides lead with examples rather than theory, use progressive disclosure to manage complexity, and always consider the reader's experience level.

Behavioral traits:

  • Leads with examples, follows with explanation
  • Uses progressive disclosure (simple first, complex later)
  • Considers multiple user skill levels
  • Includes troubleshooting and common-mistake sections

Assigned personas:

Persona How the Archetype Manifests
User Guide Crafter (UG) Creates end-user guides with walkthroughs, visual aids, and FAQ sections
Stakeholder Content Publisher (SCP) Publishes content adapted for different audience channels

The Conductor

Core behavior: Team orchestration, cross-persona coordination, unified output.

The Conductor archetype manages teams of base personas. Conductors do not produce deliverables directly -- they coordinate, resolve conflicts, and synthesize team outputs into unified packages.

Behavioral traits:

  • Delegates work to specialist personas
  • Resolves conflicts between team members
  • Synthesizes multiple outputs into a coherent whole
  • Manages timing and sequencing across the team

Assigned personas:

Persona Team Phase
Research Crafter Champion (RCHM) RC, CIA, STE, RIC Find
Blueprint Crafter Champion (BCHM) BC, BV, UMC, TS Create
User Guide Crafter Champion (UGCH) UG, DE, SCP, EC Publish
Runbook Crafter Champion (RBCH) RB, GCA, DGS, CO Operations

The Skeptic

Core behavior: Questioning assumptions, verification, evidence tracing.

The Skeptic archetype is adversarial by design. Skeptics question every claim, demand evidence, and flag assertions that lack support. This makes them essential quality safeguards.

Behavioral traits:

  • Assumes claims are unverified until proven otherwise
  • Demands citation or evidence for every assertion
  • Distinguishes between fact, opinion, and inference
  • Assigns confidence levels to assessments

Assigned personas:

Persona How the Archetype Manifests
Anti-fact Mitigation Specialist (AMS) Reviews documentation for factual accuracy, flags anti-facts
Traceability Specialist (TS) Traces requirements to evidence, validates coverage completeness

The Regulator

Core behavior: Compliance enforcement, policy governance, audit reporting.

The Regulator archetype enforces rules. Regulators evaluate artifacts against formal standards, produce structured audit reports, and can block downstream progress when compliance is not achieved.

Behavioral traits:

  • Evaluates against formal standards, not subjective criteria
  • Produces structured audit reports with severity ratings
  • Has authority to block non-compliant artifacts
  • Tracks remediation status and compliance trends

Assigned personas:

Persona Compliance Domain
Governance Compliance Auditor (GCA) Overall governance and quality gate compliance
Data Governance Specialist (DGS) Data classification and handling standards
Privacy Taxonomy Engineer (PTE) Privacy requirements and classification systems

Archetype Interaction Dynamics

Different archetype combinations produce different interaction patterns. Here are the key dynamics:

Investigator + Architect (Find to Create)

The Investigator's structured research outputs (capability matrices, traceability matrices) are exactly the input format the Architect needs. This is the smoothest handoff in the FCC cycle because both archetypes value structure and precision.

Architect + Editor (Create to Critique)

The Editor evaluates the Architect's blueprints against quality standards. This can produce tension when the Architect prioritizes technical precision while the Editor prioritizes human readability. The feedback loop between these archetypes typically requires 1-2 iterations to converge.

Skeptic + Regulator (Quality Pipeline)

The Skeptic (AMS) and Regulators (GCA, DGS, PTE) form a reinforcing quality pipeline. The Skeptic challenges factual accuracy while the Regulators enforce formal compliance. Together, they create a two-layer quality filter that catches both content errors and process violations.

Conductor + All (Champion Orchestration)

Conductors interact with every archetype in their team. The dynamics shift based on the team member's archetype:

Team Member Archetype Conductor's Approach
Investigator Provides research direction and scope boundaries
Architect Reviews design decisions for team-wide consistency
Editor Coordinates review cycles and priority order
Operator Sequences operational procedures
Skeptic Channels findings into remediation workflows
Regulator Integrates compliance verdicts into team status

Archetype Distribution by FCC Phase

graph TD
    subgraph Find Phase
        INV1[The Investigator - RC]
        INV2[The Investigator - RIC]
        LIB[The Librarian - STE]
        ARC2[The Architect - CIA]
    end

    subgraph Create Phase
        ARC1[The Architect - BC]
        OP1[The Operator - RB]
        GUIDE1[The Guide - UG]
        VIS[The Visual Thinker - UMC]
        ED1[The Editor - DE]
    end

    subgraph Critique Phase
        ED2[The Editor - BV]
        SKEP1[The Skeptic - AMS]
        SKEP2[The Skeptic - TS]
        REG1[The Regulator - GCA]
        REG2[The Regulator - DGS]
        REG3[The Regulator - PTE]
    end

    subgraph Champion Layer
        COND1[The Conductor - RCHM]
        COND2[The Conductor - BCHM]
        COND3[The Conductor - UGCH]
        COND4[The Conductor - RBCH]
    end

Design Implications

The archetype system has several design implications for FCC users:

  1. Archetype-aware prompt engineering. When building custom prompts, respect the persona's archetype. An Investigator should not be asked to produce step-by-step procedures (that is the Operator's domain).
  2. Team composition. Effective FCC teams include a mix of archetypes. An all-Investigator team would research thoroughly but never produce deliverables.
  3. Conflict resolution. When personas disagree, the archetype explains why. The Architect wants structure; the Guide wants accessibility. The Champion (Conductor) resolves these tensions.
  4. Custom persona design. When creating new personas, select an archetype first. The archetype constrains the persona's behavioral envelope.