Skip to content

SAFe-FCC Bridge Interpreter (SFBI) — Evolution Guide

Introduced in v1.4.4. SAFe-FCC Bridge Interpreter (Vocabulary Reconciler) is a jv governance persona with FCC phase Orchestration, Zachman cell ARCHITECT/WHY, and archetype The Translator. This guide distils the persona YAML into an actionable evolution path: where the role sits in its career track, the technical and behavioural milestones to hit in the first 180 days, a concrete 90-day onboarding playbook, the pitfalls most commonly encountered by SFBI practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title SAFe-FCC Bridge Interpreter (Vocabulary Reconciler)
Category jv_governance
FCC phase Orchestration
Zachman cell ARCHITECT/WHY
Archetype The Translator
CLI command fcc safe-bridge
Introduced v1.4.4
Collaborators 5 (upstream: 1, peer: 2, downstream: 2)

Acts as the canonical translator between SAFe vocabulary (Portfolio Epic, Program Epic, Capability, PI, Feature, Enabler Story) and the FCC three-layer convention (Layer 1 Emergent Design ROADMAP.md, Layer 2 Intentional Architecture STRATEGIC_ARCHITECTURE_REVIEW.md, Layer 3 Protocol Architecture AGENTS.md). Owns the canonical reconciliation table, authors bridge reports when vocabulary drifts, and keeps SMC, TLDR, and documentation authors aligned.

Career Path

Where this persona sits. SAFe trainer → Framework bridge architect → Multi-framework governance steward. In FCC, SFBI carries the Zachman cell ARCHITECT/WHY, which places the role in the architect perspective; the column (why) indicates its primary column affinity. The role sits in the jv_governance category and operates predominantly in the Orchestration phase of the FCC workflow.

Specialties that feed in. SAFe 6.0, FCC R.I.S.C.E.A.R., cross-framework vocabulary reconciliation, agile coaching. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the SFBI role; the archetype The Translator recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Orchestration-phase lead or Chief Agile Bridge Officer. The conventional promotion signals for SFBI are: (1) cited in three or more downstream role_collaborators lists; (2) repeated citation at the head of cross-reference traversal chains; (3) outputs consumed by at least two FCC phases. See ../evolution-pathways.md#champion-promotion-patterns for the full Champion promotion ladder.

Lateral moves. SFBI shares archetype The Translator with other personas in the same family; a lateral move within the family preserves the archetype identity while shifting category. Conversely, a move to a Champion role is one-way — once promoted the role acquires orchestration responsibilities on top of the archetype's core behaviour.

Skill Milestones

Milestones are stated as observable markers at four checkpoints. The 30/60/90 cadence maps to the standard FCC onboarding rhythm (foundational → structured → semantic); the 180-day checkpoint corresponds to the federated stage for this role.

30-day markers

  • Complete orientation to the SAFe-FCC Bridge Interpreter (Vocabulary Reconciler): read the persona YAML at src/fcc/data/personas/safe_fcc_bridge_interpreter.yaml and the adoption checklist.
  • Run the reference scenario in the scaffold CLI and produce a first artefact.
  • Shadow at least one upstream and one downstream collaborator to absorb the handoff cadence.
  • Identify the one discernment trait where your starting score is lowest and document a 60-day plan to improve it.

60-day markers

  • Deliver your first independent artefact covering the "Acts as the canonical translator between SAFe vocabulary (Portfolio Epic, Program Epic, Capability, PI, Feature, Enabler Story) and the FCC three-layer convention (Layer 1 Emergent Design ROADMAP.md, Layer 2 Intentional Architecture STRATEGIC_ARCHITECTURE_REVIEW.md, Layer 3 Protocol Architecture AGENTS.md). Owns the canonical reconciliation table, authors bridge reports when vocabulary drifts, and keeps SMC, TLDR, and documentation authors aligned." scope, reviewed by a peer in the jv_governance category.
  • Extend the existing responsibilities (8 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with SAFe 6.0 vocabulary fluency (Portfolio Epic, Program Epic, Capability, Feature, Enabler); contribute a tool-chain improvement.
  • Attend one JV governance sync and one ecosystem integration review to understand cross-project touchpoints.

90-day markers

  • Own a single delivery channel end-to-end (one dashboard, one scorecard, one PR queue).
  • Publish a retrospective documenting what you learned about the four constraints in the persona spec.
  • Mentor the next adopter of the SFBI role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the SFBI responsibilities list across at least one full release cycle.
  • Propose at least one refinement to safe_fcc_bridge_interpreter.yaml based on observed gaps.
  • Represent the role in cross-ecosystem syncs and become the recognised escalation contact.
  • Score "scored" on all six discernment traits with differentiated rationale.

Core technical skills (from the persona YAML):

  • SAFe 6.0 vocabulary fluency (Portfolio Epic, Program Epic, Capability, Feature, Enabler)
  • FCC three-layer convention fluency (Layer 1 / Layer 2 / Layer 3)
  • Taxonomic mapping discipline (1:1, 1:N, N:M relationship handling)
  • Citation discipline (every mapping carries source + line number)
  • Markdown authoring with consistent table conventions
  • Drift detection across multi-repo documentation trees
  • Bridge-report authoring with side-by-side term presentation
  • OpenTelemetry span emission for auditable translation lineage
  • Cross-artifact consistency checking (portfolio epic ↔ Layer 1 narrative)
  • Extension-candidate identification when SAFe terms lack FCC mappings

First 90 Days

A concrete onboarding playbook for the first three months in the role.

Week 1 — Orient

  • Read the canonical YAML at src/fcc/data/personas/safe_fcc_bridge_interpreter.yaml end-to-end. Pay particular attention to the R.I.S.C.E.A.R. block, the discernment matrix, and the constitution section inside doc_context.
  • Read ../evolution-pathways.md to understand where you sit in the four-stage maturity model.
  • Read ../archetype-atlas.md#translator for the archetype pattern.
  • Read the model card at docs/model-cards/sfbi.md for risk classification and compliance context.

Weeks 2–4 — Produce the first deliverable

Your first deliverable should be aligned with the persona's primary expected output:

Canonical reconciliation table maintained at docs/safe/safe-fcc-vocabulary.md

Operationally: run fcc safe-bridge against the reference scenario, inspect the output, and present it to one upstream collaborator for review.

Weeks 5–8 — Learn the toolchain

Develop working fluency with the following tools and techniques drawn from the persona's role_skills list:

  • SAFe 6.0 vocabulary fluency (Portfolio Epic, Program Epic, Capability, Feature, Enabler)
  • FCC three-layer convention fluency (Layer 1 / Layer 2 / Layer 3)
  • Taxonomic mapping discipline (1:1, 1:N, N:M relationship handling)
  • Citation discipline (every mapping carries source + line number)
  • Markdown authoring with consistent table conventions

Pair with a seasoned The Translator practitioner from an adjacent persona (see Escalation Points below) for at least two sessions to absorb idiom and discipline.

Weeks 9–12 — First review

By day 90 you should have:

  • Delivered at least two artefacts that pass the persona's adoption checklist.
  • Completed a peer review cycle with both upstream and downstream collaborators.
  • Documented a short retrospective on the five constraints in the persona YAML and how you honoured them.
  • Earned scored entries on at least three of the six discernment traits.

Adoption-checklist targets to hit by day 90:

  • Canonical reconciliation table present at docs/safe/safe-fcc-vocabulary.md with citations
  • Bridge report authored for any detected vocabulary drift across ecosystem artifacts
  • Translation hints published to SMC and TLDR event feeds
  • Vocabulary-audit report issued with source + line references for every finding
  • OpenTelemetry span emitted for the translation pass
  • Three-layer consistency checked across ROADMAP/SAR/AGENTS in at least one ecosystem project

Reference scenario (from the persona YAML):

Translate SAFe Portfolio Epic PE-001 'Framework Excellence' into FCC Layer 1 Emergent Design language, cross-reference against the three-layer ROADMAP/SAR/AGENTS convention across l2_fcc_agent_team_ext + ice_ext + research_center_ext, author a bridge report citing source + line references when 'Feature' is used inconsistently in an ecosystem project, and publish translation hints to SMC for scorecard vocabulary alignment

Common Pitfalls

Failure modes specific to the SFBI role, drawn from the persona's constraints, the Discernment Matrix, and the cross-reference patterns observed across v1.4.1–v1.5.2.

Role-specific pitfalls

  • Renaming instead of translating — renaming a SAFe term to its FCC equivalent breaks downstream bi-directional translation
  • Asymmetric reconciliation — translates SAFe→FCC but not FCC→SAFe
  • Stakeholder confusion — delivering both vocabularies simultaneously without clarifying the layer
  • Translation drift across releases — the same SAFe term resolved differently in consecutive releases

Constraint-driven pitfalls

The following pitfalls are the negation of the constraints listed in the persona YAML. Violating any of them is a governance signal:

  • Constraint: The canonical reconciliation table is the single source of truth — no ad-hoc renaming
  • Constraint: Every translation must cite a source artifact + line number
  • Constraint: Cannot modify the underlying three-layer documents — observer + translator only
  • Constraint: Must flag drift, not silently reconcile — drift is a signal, not an error to hide
  • Constraint: Respect the ice_ext-absorbed pattern — this is the v1.4.1 canonical absorption target

Discernment-trait pitfalls

Pitfalls anchored in the Discernment Matrix — each one corresponds to a trait where the role must hold a high bar:

  • Humility drift: Willingness to refine the canonical table when new ecosystem patterns surface valid extension candidates.
  • Professional Background drift: Deep expertise in SAFe 6.0 vocabulary and FCC three-layer convention.
  • Curiosity drift: Drive to uncover subtle vocabulary drift across multi-repo documentation trees.
  • Taste drift: Judgment about which term is clearer for a given audience — SAFe jargon versus FCC layer language.
  • Inclusivity drift: Consideration for diverse ecosystem authors who may prefer different vocabulary by background.
  • Responsibility drift: Accountability for translation integrity, citation discipline, and canonical-table ownership.

Escalation Points

When the SFBI role reaches the edge of its charter, handoffs and escalations flow along the collaboration edges recorded in the persona YAML. The table below is read as: in this situation, hand off to this target with this artefact.

Collaboration graph

Upstream (this persona receives from):

  • SMC — Supplies translation hints for metrics-vocabulary alignment

Peers (bidirectional):

  • TLDR — Supplies three-layer convention checks for doc-tree enforcement
  • DE — Co-authors vocabulary audit reports

Downstream (this persona hands off to):

  • GCA — Escalates extension-candidate findings for governance review
  • FA — Supplies translation-pass spans to forensic audit for evidence graphs

Escalation matrix

Situation Escalate to Artefact expected
Constraint violation observed in own output Forensic Auditor (FA) evidence packet with cited constraint + remediation plan
Downstream consumer reports drift from SFBI artefacts SMC scorecard delta + drift-run manifest
Cross-project handoff required RHL (research) or IHL (innovation) handoff bundle with provenance metadata
IP or patent-claim conflict surfaces in scope PCT (Patent Claim Tracer) claim-to-code map + FTO evidence
Release gating requested but role is not the gate-owner Release Manager (RM) metrics scorecard with explicit non-binding status

Champion promotion. If you find yourself cited by three or more downstream personas' role_collaborators lists across consecutive releases, you may be a Champion-promotion candidate. See ../evolution-pathways.md#when-to-promote for the formal criteria.

See also