Skip to content

Enterprise Adoption Guide

This guide covers deploying the FCC Agent Team Framework in enterprise environments. It addresses CI/CD integration, governance for regulated industries, quality gate customization for compliance, team onboarding, and scaling from a pilot project to organization-wide adoption.

CI/CD Pipeline Integration

FCC is a Python package with a CLI interface and programmatic API. Both integrate cleanly into standard CI/CD pipelines.

GitHub Actions Example

name: FCC Validation
on:
  pull_request:
    paths:
      - 'docs/**'
      - 'data/personas/**'
      - 'data/governance/**'

jobs:
  validate:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-python@v5
        with:
          python-version: '3.11'

      - name: Install FCC
        run: pip install fcc-agent-team-ext

      - name: Validate personas
        run: fcc validate --personas data/personas/

      - name: Validate cross-references
        run: fcc validate --cross-references data/personas/cross_reference.yaml

      - name: Run quality gates
        run: fcc validate --quality-gates data/governance/quality_gates.yaml

      - name: Validate generated docs
        run: fcc validate-docs --output-dir docs/generated/

      - name: Run deterministic simulation
        run: |
          fcc simulate --scenario GEN-001 --mode deterministic --output trace.json
          fcc validate --trace trace.json

GitLab CI Example

fcc-validation:
  image: python:3.11
  stage: test
  script:
    - pip install fcc-agent-team-ext
    - fcc validate --personas data/personas/
    - fcc validate --cross-references data/personas/cross_reference.yaml
    - fcc validate --quality-gates data/governance/quality_gates.yaml
  rules:
    - changes:
        - docs/**
        - data/**

Pre-Commit Hook

Add FCC validation as a pre-commit hook to catch issues before they reach CI:

# .pre-commit-config.yaml
repos:
  - repo: local
    hooks:
      - id: fcc-validate
        name: FCC Schema Validation
        entry: fcc validate --personas data/personas/
        language: python
        additional_dependencies: ['fcc-agent-team-ext']
        files: '^data/personas/.*\.yaml$'

Governance for Regulated Industries

FCC's governance layer provides built-in support for compliance requirements common in regulated industries (financial services, healthcare, government).

The Governance Stack

FCC provides three governance mechanisms:

  1. Quality Gates -- 28 automated validation checkpoints with severity levels (error, warning, info). Gates can block downstream progress when they fail.
  2. Governance Personas -- Three dedicated personas (DGS, PTE, AMS) that evaluate documentation for data governance, privacy, and factual accuracy.
  3. Capability Tags -- 30 tags in a three-level hierarchy for artifact classification and audit trails.

Compliance Mapping

Map FCC governance components to industry compliance frameworks:

FCC Component SOC 2 HIPAA ISO 27001 FedRAMP
Quality Gates CC7.1 (monitoring) 164.312(c) (integrity) A.12.1 (procedures) CA-7 (monitoring)
Data Governance Specialist CC6.1 (access) 164.312(a) (access) A.8.1 (asset mgmt) AC-1 (access policy)
Privacy Taxonomy Engineer P1.1 (privacy) 164.530 (notices) A.18.1 (compliance) AP-1 (purpose)
Anti-fact Mitigation CC3.1 (risk) 164.312(c) (integrity) A.12.2 (protection) SI-4 (monitoring)
Capability Tags CC2.1 (communication) 164.530 (documentation) A.5.1 (policies) PL-2 (planning)
Trace Logging CC7.2 (detection) 164.312(b) (audit) A.12.4 (logging) AU-2 (auditing)

Customizing Quality Gates for Compliance

Create industry-specific quality gates by extending the base gate definitions:

# data/governance/quality_gates_hipaa.yaml
quality_gates:
  - id: QG-HIPAA-001
    name: PHI Data Classification
    description: All documentation references to patient data must include PHI classification tags
    severity: error
    category: compliance
    check: tag_presence
    required_tags: ["phi-classification", "data-sensitivity"]

  - id: QG-HIPAA-002
    name: Access Control Documentation
    description: Documents describing data access must reference the access control matrix
    severity: error
    category: compliance
    check: cross_reference_presence
    required_references: ["access-control-matrix"]

  - id: QG-HIPAA-003
    name: Audit Trail Completeness
    description: All documentation changes must have traceable audit entries
    severity: warning
    category: compliance
    check: trace_completeness

Governance Workflow Pattern

In regulated environments, route all documentation through the governance pipeline before publication:

graph LR
    RC[Research Crafter] --> BC[Blueprint Crafter]
    BC --> DE[Documentation Evangelist]
    DE --> DGS[Data Governance Specialist]
    DGS --> PTE[Privacy Taxonomy Engineer]
    PTE --> AMS[Anti-fact Mitigation Specialist]
    AMS --> GCA[Governance Compliance Auditor]
    GCA -->|Approved| SCP[Stakeholder Content Publisher]
    GCA -->|Rejected| DE

Team Onboarding Strategies

Phased Rollout

Deploy FCC in three phases, expanding both the persona count and the team's familiarity.

Phase 1: Core Only (Weeks 1-2)

  • Deploy the 5-node base workflow (RC, BC, DE, RB, UG)
  • Train the team on R.I.S.C.E.A.R. specification structure
  • Run deterministic simulations to build familiarity
  • Assign each team member a primary persona to study

Phase 2: Extended Workflow (Weeks 3-4)

  • Add integration personas (CIA, UMC, STE, TS, BV, RIC, GCA)
  • Introduce the cross-reference matrix for interaction understanding
  • Run the 20-node extended workflow
  • Begin customizing quality gates for project-specific needs

Phase 3: Full Deployment (Weeks 5-6)

  • Add governance personas (DGS, PTE, AMS) and stakeholder personas (CO, SMC, EC, RS, SCP)
  • Activate champion personas (RCHM, BCHM, UGCH, RBCH) for orchestration
  • Run the complete 24-node workflow
  • Integrate with CI/CD pipeline

Role Assignment Matrix

Map team members to FCC personas based on their existing skills:

Team Role Primary FCC Persona Secondary Persona Rationale
Tech Lead Blueprint Crafter (BC) Blueprint Validator (BV) Architecture and design ownership
Tech Writer Documentation Evangelist (DE) User Guide Crafter (UG) Documentation standards and user content
SRE / DevOps Runbook Crafter (RB) Collaboration Orchestrator (CO) Operational procedures and coordination
QA Engineer Anti-fact Mitigation (AMS) Traceability Specialist (TS) Quality assurance and traceability
Product Manager Executive Communicator (EC) Roadmap Synchronizer (RS) Stakeholder communication and planning
Security Engineer Data Governance (DGS) Privacy Taxonomy Engineer (PTE) Data governance and privacy

Training Curriculum

Session Duration Content Audience
FCC Overview 1 hour What is FCC, the three phases, value proposition All team members
R.I.S.C.E.A.R. Deep Dive 2 hours 10-component spec, reading YAML, loading registry Practitioners
Simulation Workshop 2 hours Running simulations, reading traces, interpreting results Practitioners
Quality Gate Configuration 1 hour Gate YAML format, custom rules, CI integration Tech leads, QA
Governance Workshop 2 hours Compliance mapping, governance pipeline, audit trails Security, compliance

Scaling from Pilot to Organization-Wide

Pilot Phase (1-2 Teams)

  • Select a bounded documentation project as the pilot
  • Assign one FCC champion (team member, not the persona type) to drive adoption
  • Use the core 5-persona workflow to minimize complexity
  • Measure: time to first documentation delivery, quality gate pass rates, team satisfaction

Expansion Phase (3-5 Teams)

  • Publish a shared persona registry as an internal Python package
  • Create team-specific quality gate overlays for different compliance contexts
  • Establish a cross-team governance review using the GCA persona workflow
  • Measure: cross-team consistency, documentation coverage, reuse rates

Organization-Wide Phase

  • Deploy a centralized FCC service with shared persona registry and quality gates
  • Integrate with the enterprise documentation platform (Confluence, SharePoint, etc.)
  • Establish an FCC Center of Excellence to maintain persona definitions and quality gates
  • Measure: documentation debt reduction, compliance audit pass rates, onboarding time

Governance Model for Multi-Team Deployment

graph TD
    COE[FCC Center of Excellence] --> REG[Shared Persona Registry]
    COE --> GATES[Quality Gate Library]
    COE --> TEMPLATES[Template Library]

    TEAM_A[Team A] --> REG
    TEAM_A --> GATES_A[Team A Gate Overlay]
    GATES_A --> GATES

    TEAM_B[Team B] --> REG
    TEAM_B --> GATES_B[Team B Gate Overlay]
    GATES_B --> GATES

    TEAM_C[Team C] --> REG
    TEAM_C --> GATES_C[Team C Gate Overlay]
    GATES_C --> GATES

Cost Considerations

Component Cost Driver Optimization
Deterministic simulation Compute only Minimal; runs in CI/CD at no LLM cost
AI-powered simulation LLM API calls Use deterministic mode for validation; reserve AI mode for production content
Quality gates Compute only Run in CI/CD pipeline; parallelize gate evaluation
Documentation generation Compute only Generate once, cache results, regenerate on persona changes