Site Map¶
This page maps the entire FCC documentation tree to the underlying
subsystems and persona packs. It exists so a new contributor can answer
"where does X live?" without scrolling the navigation tree. Source for the
persona counts and pack names is the persona registry under
src/fcc/data/personas/; source for the section structure is mkdocs.yml.
The diagram below shows the documentation tree on the left, the source modules they describe in the middle, and the persona packs on the right.
graph LR
subgraph DOCS["docs/ tree"]
D_GS[Getting Started]
D_GB[Guidebook<br/>26 chapters]
D_BK[Books<br/>Book 1-3]
D_AR[Architecture<br/>this tree]
D_SP[Specification]
D_TU[Tutorials]
D_PE[Personas]
D_DM[Decision Makers]
D_FB[For Beginners]
D_FE[For Educators]
D_FS[For Scientists]
D_FP[For Professionals]
D_FT[For Teams]
D_DV[Developer]
D_DC[Decisions<br/>5 ADRs]
D_RM[Roadmap]
end
subgraph SRC["src/fcc/ subsystems"]
S_PE[personas/<br/>RISCEAR + registry]
S_WF[workflow/<br/>graphs + actions]
S_SI[simulation/<br/>engine + traces]
S_SC[scenarios/]
S_PR[protocols/<br/>A2A + MCP + WS]
S_MS[messaging/<br/>event bus]
S_OB[observability/]
S_CO[collaboration/]
S_PL[plugins/<br/>11 types]
S_GO[governance/]
S_OM[objectmodel/]
S_SE[search/]
S_KN[knowledge/<br/>+ federation]
S_RG[rag/]
S_FE[federation/]
S_DE[demos/]
S_TU[tutorials/]
S_EV[evaluation/]
S_CM[compliance/]
S_SF[scaffold/<br/>CLI]
end
subgraph PERSONAS["147 personas across 26 packs"]
P_CORE[Core<br/>5]
P_INT[Integration<br/>8]
P_GOV[Governance<br/>4]
P_STK[Stakeholder<br/>5]
P_CHM[Champion<br/>4]
P_OS[Open Science]
P_RAI[Responsible AI]
P_JV[JV Collab + Gov]
P_DOC[Docs as Code]
P_PRV[Privacy]
P_KG[Knowledge Graph]
P_LFA[Local-First AI]
P_DE[Data Eng<br/>6]
P_ML[ML Lifecycle<br/>9]
P_MM[ML Models<br/>11]
P_DV[DevOps<br/>3]
P_AD[App Dev<br/>2]
P_UX[UX/Viz<br/>6]
P_PR[Protocol Eng<br/>6]
P_HC[Healthcare<br/>11]
P_FN[Finance<br/>11]
P_LG[Legal<br/>5]
P_IN[Insurance<br/>6]
P_EN[Energy<br/>6]
P_GV[Government<br/>6]
P_PLG[Plugin packs<br/>23]
end
D_GS --> S_PE
D_GB --> S_PE
D_GB --> S_WF
D_BK --> S_PE
D_BK --> S_WF
D_AR --> S_PL
D_AR --> S_OM
D_AR --> S_KN
D_AR --> S_FE
D_SP --> S_PE
D_SP --> S_WF
D_TU --> S_DE
D_PE --> S_PE
D_DM --> S_GO
D_FB --> S_PE
D_FB --> S_SI
D_FE --> S_CO
D_FS --> S_RG
D_FS --> S_KN
D_FP --> S_CM
D_FP --> S_FE
D_FT --> S_CO
D_DV --> S_PL
D_DC --> S_OM
D_RM --> S_GO
S_PE --> P_CORE
S_PE --> P_INT
S_PE --> P_GOV
S_PE --> P_STK
S_PE --> P_CHM
S_PE --> P_OS
S_PE --> P_RAI
S_PE --> P_JV
S_PE --> P_DOC
S_PE --> P_PRV
S_PE --> P_KG
S_PE --> P_LFA
S_PE --> P_DE
S_PE --> P_ML
S_PE --> P_MM
S_PE --> P_DV
S_PE --> P_AD
S_PE --> P_UX
S_PE --> P_PR
S_PE --> P_HC
S_PE --> P_FN
S_PE --> P_LG
S_PE --> P_IN
S_PE --> P_EN
S_PE --> P_GV
S_PE --> P_PLG
The takeaway is that every documentation surface has a single load-bearing
source module (often two), which makes search-and-replace refactors safe:
when you rename a class in src/fcc/<module>/, the matching docs/ page
is straightforward to find.
Navigation cheatsheet¶
| If you want to … | Start here |
|---|---|
| Run the framework | Getting Started |
| Understand the FCC pattern | Guidebook ch. 1 |
| Read about a specific persona | Personas overview |
| Add a new plugin | Plugin boundaries |
| Wire FCC into another project | API boundaries |
| Set up cross-project federation | Federated vs individual |
| Teach a course | For Educators |
| Run reproducible research | For Scientists |
| Deploy to enterprise | For Professionals |
| Read the design decisions | ADR index |
See also¶
- Source:
mkdocs.yml(nav definition) - Source:
src/fcc/data/personas/(persona pack files) - Architecture index