Skip to content

Chapter 6: Ecosystem Overview

Learning Objectives

By the end of this chapter you will be able to:

  1. Name the 11 projects in the FCC ecosystem and describe each project's role.
  2. Explain the FCC tier system and how it classifies projects by maturity.
  3. Describe the dependency relationships between ecosystem projects.
  4. Articulate how cross-project orchestration works at a high level.
  5. Identify which projects are most relevant to your use case.

The figure below lays out the eleven-project FCC ecosystem as three tiers, with the FCC framework at the centre, the four Tier 2 extensions depending on it, and six Tier 3 consumers built on top.

flowchart TB
    subgraph T1["Tier 1: Core"]
        FCC[l2_fcc_agent_team_ext<br/>FCC Framework]
    end
    subgraph T2["Tier 2: Extensions"]
        AOME[AOME<br/>Privacy-Aware Objects]
        CONSTEL[CONSTEL<br/>Metadata & Knowledge]
        SKY[Sky-Parlour<br/>NL Interface]
        CTO[CTO<br/>Object Model Bridge]
    end
    subgraph T3["Tier 3: Consumers"]
        PAOM[PAOM]
        DATA[L2 Data]
        ANA[L2 Analytics]
        GOV[L2 Governance]
        DEP[L2 Deployment]
        DOCS[L2 Docs]
    end

    FCC --> AOME
    FCC --> CONSTEL
    FCC --> SKY
    FCC --> CTO
    AOME --> PAOM
    CONSTEL --> DATA
    CTO --> ANA

    style FCC fill:#2196F3,color:#fff
    style T1 fill:#e3f2fd
    style T2 fill:#f3e5f5
    style T3 fill:#e8f5e9

No Tier 3 project depends on FCC without going through a Tier 2 extension, which is how the ecosystem keeps FCC focused on framework concerns while domain-specific code accrues elsewhere.

The Ecosystem at a Glance

FCC is not a single project. It is the orchestration engine at the center of an ecosystem of 11 projects, each addressing a different aspect of AI-agent collaboration, governance, and deployment. Understanding the ecosystem is essential because most production use cases involve at least 2--3 projects working together.

Here is the full ecosystem:

Project Role FCC Tier
l2_fcc_agent_team_ext Core FCC framework (this project) Tier 1
AOME AI Object Model Engine -- privacy-aware object modeling Tier 2
CONSTEL Constellation metadata and cross-project knowledge sharing Tier 2
Sky-Parlour Natural-language interface for ecosystem exploration Tier 2
CTO Chief Technology Object -- canonical object model bridge Tier 2
PAOM Persona-Aware Object Model -- consumer of FCC personas Tier 3
L2 Data Shared datasets and data pipeline infrastructure Tier 3
L2 Analytics Analytics dashboards and reporting Tier 3
L2 Governance Enterprise governance policy management Tier 3
L2 Deployment Deployment automation and infrastructure Tier 3
L2 Docs Cross-project documentation and style guides Tier 3

Tier System

The tier system reflects each project's relationship to the core FCC framework:

  • Tier 1: The FCC framework itself. Everything depends on this.
  • Tier 2: Direct extensions that add major capabilities. These projects integrate deeply with FCC's persona, workflow, and governance systems.
  • Tier 3: Consumers and support projects that use FCC but do not extend its core. They depend on Tier 1 or Tier 2 projects.

Key Projects in Depth

AOME (AI Object Model Engine)

AOME provides privacy-aware object modeling. When FCC personas process data, AOME ensures that personal information is handled according to privacy regulations (GDPR, CCPA, HIPAA). AOME integrates with FCC through the plugin system: it contributes privacy-related personas, validators, and governance rules.

In a typical integration, AOME's privacy personas run as part of the Critique phase, checking that Create-phase outputs do not contain unauthorized personal data. AOME also provides data classification capabilities that tag artifacts with sensitivity levels, feeding into FCC's governance system.

CONSTEL (Constellation Metadata)

CONSTEL manages metadata across the ecosystem. When multiple projects collaborate on a shared initiative, CONSTEL provides the metadata layer that tracks which artifacts came from which project, how they relate to each other, and what versions are in play.

CONSTEL integrates with FCC through the event bus. As FCC workflows produce artifacts, events are emitted to CONSTEL, which indexes the metadata and makes it queryable across projects. This is the foundation for the federated knowledge capabilities covered in Book 3.

Sky-Parlour

Sky-Parlour provides a natural-language interface for exploring the ecosystem. Instead of writing queries against CONSTEL's metadata API, you can ask: "Which personas were involved in last week's data quality review?" Sky-Parlour translates the question into the appropriate API calls and returns a human-readable answer.

Sky-Parlour is particularly useful for stakeholders who need visibility into FCC workflows but do not want to interact with the CLI or API directly.

CTO (Chief Technology Object)

CTO provides a canonical object model that bridges FCC's internal models with external systems. FCC's objectmodel package (src/fcc/objectmodel/) includes a CTOFacadeAdapter and CTORepositoryAdapter that translate between FCC's dataclass-based models and CTO's object model.

This bridge is optional -- FCC works without CTO -- but it is valuable when you need to integrate FCC with enterprise systems that already use CTO as their canonical model.

PAOM (Persona-Aware Object Model)

PAOM is a consumer of FCC personas, not a producer. It imports persona definitions from FCC and uses them to drive its own object modeling workflows. The important architectural point is that FCC owns the persona definitions; PAOM consumes them. This ensures that there is a single source of truth for persona specifications across the ecosystem.

Dependency Map

The dependency relationships between projects form a directed acyclic graph:

                  l2_fcc_agent_team_ext (Tier 1)
                   /    |    |    \
                  /     |    |     \
               AOME  CONSTEL CTO  Sky-Parlour (Tier 2)
              / | \    |     |      |
             /  |  \   |     |      |
          PAOM Data Analytics Governance Deployment Docs (Tier 3)

All Tier 2 projects depend on the core FCC framework. Tier 3 projects may depend on Tier 1, Tier 2, or both. No circular dependencies exist -- the graph is strictly acyclic.

Cross-Project Orchestration

When a task spans multiple projects, FCC's solution-level EAIFC workflow graphs coordinate the work:

  1. FCC dispatches sub-tasks to Tier 2 projects via protocol integration (A2A, MCP).
  2. Tier 2 projects execute their local workflows and report results back to FCC.
  3. FCC aggregates results and routes them through its governance system.
  4. CONSTEL indexes metadata from all participating projects, enabling cross-project queries.
  5. Sky-Parlour provides visibility to stakeholders who need a high-level view.

This orchestration model is covered in depth in Book 3, Chapters 5 and 6. For now, the key insight is that FCC acts as the orchestration hub -- it does not do everything itself, but it coordinates the projects that do.

Choosing Your Starting Point

Not every use case requires the full ecosystem. Here is a decision tree:

  • Single-project AI orchestration: FCC alone is sufficient. Use the core personas, a standard workflow graph, and the built-in governance system.
  • Multi-project coordination: Add CONSTEL for metadata sharing and CTO for model bridging.
  • Privacy-sensitive workloads: Add AOME for privacy-aware object modeling and governance.
  • Stakeholder visibility: Add Sky-Parlour for natural-language exploration.
  • Enterprise integration: Add PAOM for object model consumption and L2 Deployment for infrastructure automation.

Start with the smallest set of projects that meets your requirements. You can add more as your needs grow -- the plugin system and protocol integration make it straightforward to incorporate new projects into an existing FCC deployment.

Key Takeaways

  • The FCC ecosystem comprises 11 projects organized into 3 tiers by their relationship to the core framework.
  • Tier 1 is FCC itself; Tier 2 projects (AOME, CONSTEL, CTO, Sky-Parlour) extend the core; Tier 3 projects consume the framework.
  • Cross-project orchestration uses EAIFC workflow graphs with A2A/MCP protocol integration.
  • CONSTEL provides cross-project metadata; AOME provides privacy governance; CTO bridges object models.
  • Start with the minimum set of projects for your use case and expand as needed.

Cross-References

← Chapter 5: The Collaboration Model | Next: Chapter 7 -- Getting Started →