Skip to content

Specification Hub

This section contains the formal definitions and reference material for the FCC Agent Team Framework. Every component described here is implemented in code under src/fcc/ and backed by data files under data/.

Core Specifications

  • R.I.S.C.E.A.R. Specification -- The 10-component persona definition format. Covers Role, Input, Style, Constraints, Expected Output, Archetype, Responsibilities, Role Skills, Role Collaborators, and Role Adoption Checklist.

  • Dimension System -- The 56-dimension persona profiling system organized into 9 categories, including 14 consumer-to-agent reinterpretations.

  • Discernment Matrix -- Six traits (Humility, Professional Background, Curiosity, Taste, Inclusivity, Responsibility) evaluated across 7 rating dimensions for multi-perspective persona assessment.

  • Design Target Factors -- Six factors (Optimism, Social Connectivity, Influence, Appreciation for Diversity, Curiosity, Leadership) that define the "Super Connector" profile using the same 7-dimension rating model.

Structural Specifications

  • Cross-Reference Matrix -- The 100+ entry interaction map covering all 24 personas across 5 relationship types (handoff, feedback, coordination, governance, champion-of). Includes data model reference, category diagrams, and source architecture.

  • Cross-Reference Quick Reference -- Compact single-page reference card with relationship types, persona IDs, query patterns, and quality gate checklist.

  • Workflow Graphs -- Three workflow graph definitions (5-node base, 20-node extended, 24-node complete with champions) with edge types, BFS traversal, and topological ordering.

  • Quality Gates -- 28 quality gates organized by persona category, each with defined thresholds, check lists, and severity levels. Includes 3 cross-reference integrity gates (QG-XREF-001/002/003).

  • Capability Tags -- 30 capability tags using a three-level structure (capability / category / supercategory) for governance scoring and artifact classification.

How to Read This Section

Each specification page follows a consistent structure:

  1. Purpose -- why the specification exists and what problem it solves
  2. Format -- the data structures and fields involved
  3. Reference -- complete enumeration of all values
  4. Extension Guide -- how to add custom entries

All specifications are defined declaratively in YAML or JSON files under data/ and loaded by Python dataclass models in src/fcc/. Changes to specifications should be made in the data files first, then validated with fcc validate.