Architect: FCC Adoption Decision¶

This file collects six prompts that step an architect's team through the FCC adoption decision, mapped to the twelve questions in For Architects — Decision Checklist. Each prompt pins the relevant FCC personas, states the R.I.S.C.E.A.R. slot it exercises, and names the expected deliverable shape. The prompts are designed to be run inside a 2-hour workshop with architecture, SRE, and compliance stakeholders in the room.

1. Classify the tier¶

When to use. First session of the workshop, before any implementation detail is discussed.

Personas/subsystems invoked. arch, pm. R.I.S.C.E.A.R. slot: Role + Constraints.

You are the Enterprise Architect (arch). Program Manager (pm)
reviews.

TASK: Classify the organisation's planned FCC adoption into one of
the three trust tiers: Strict (Tier 1), Active (Tier 2), or
Minimal (Tier 3).

Inputs to consider:
1. Our tolerance for FCC contract drift.
2. Headcount willing to own the FCC version pin.
3. The six Tier 2 consumers (PAOM, PHOENIX, AURORA, Distiller,
   Athenium, Mnemosyne) as reference points.

CONSTRAINTS:
- Cite at least two FCC v1.3.x references.
- Name the owner for each tier obligation.

Deliverable: a 1-page Markdown decision with the chosen tier, 3
supporting reasons, and an owner assignment for the pin.

Expected output notes. One tier chosen, 3 reasons, owner named, 2+ FCC references.

2. Pick the integration surfaces¶

Personas/subsystems invoked. arch, sre. R.I.S.C.E.A.R. slot: Input + Expected Output.

You are the Enterprise Architect (arch). Site Reliability
Engineer (sre) reviews.

TASK: Select the minimum viable set of FCC integration surfaces
for the adoption.

Candidate surfaces (pick 1 or more, justify exclusions):
1. Python SDK + CLI.
2. fcc.plugins entry points.
3. fcc.vocabulary_providers entry points.
4. MCP server (port 9001).
5. A2A server (port 9002).
6. WebSocket bridge (port 8765).
7. Vendored YAML registries.
8. ObjectModel bridge.

CONSTRAINTS:
- Justify every excluded surface with a 1-sentence reason.
- Call out any surface that requires a new network-zone rule.

Deliverable: a table (surface, include/exclude, reason) plus a
2-paragraph narrative on how the chosen subset will be deployed.

Expected output notes. 8 surfaces evaluated, exclusions justified, deployment narrative present.

3. Scope compliance¶

Personas/subsystems invoked. cmp, arch. R.I.S.C.E.A.R. slot: Constraints.

You are the Compliance Officer (cmp). Enterprise Architect
(arch) reviews.

TASK: Scope the FCC compliance pipeline for the adoption.

Decisions required:
1. Which regulatory regime applies (EU AI Act, NIST AI RMF,
   neither, or a new one).
2. Which risk category we accept for adopted personas (low,
   limited, high, unacceptable).
3. Whether evidence-graph output is mandatory per release.

CONSTRAINTS:
- Reference FCC's 256+ EU AI Act requirements count.
- Reference FCC's 29 NIST AI RMF subcategory mapping.
- Name the artifact that will be archived per release.

Deliverable: a 3-section Markdown compliance scope, total 300 to
500 words, ending with a single SHOULD/MUST/MAY statement per
decision.

Expected output notes. 3 decisions, archive artifact named, SHOULD/MUST/MAY present.

4. Assess risks and mitigations¶

Personas/subsystems invoked. ra, arch. R.I.S.C.E.A.R. slot: Responsibilities.

You are the Risk Analyst (ra). Enterprise Architect (arch)
reviews.

TASK: Walk the six risks from docs/for-architects/risk-and-mitigation.md
through our adoption and produce a risk register.

For each risk:
1. Likelihood (low / medium / high) given our tier.
2. Impact (low / medium / high) given our surfaces.
3. Primary FCC mitigation (name the module or surface).
4. Residual risk owner (name the role).

CONSTRAINTS:
- Use the full 6-risk list: version drift, plugin discovery,
  compliance drift, gate bypass, observability gaps, federation
  collision.
- Do not invent new risks in this pass; capture gaps as "open
  questions".

Deliverable: a 6-row risk-register table plus a 3-bullet list of
open questions.

Expected output notes. 6 risks covered, residual owners assigned, open questions logged.

5. Draft the operational contract¶

Personas/subsystems invoked. sre, cmp. R.I.S.C.E.A.R. slot: Role Collaborators.

You are the Site Reliability Engineer (sre). Compliance Officer
(cmp) reviews.

TASK: Produce a 1-page operational contract between our on-call
rotation and the FCC framework.

Contents:
1. Which of the 81 FCC event types we subscribe to.
2. Which metrics (from the 7 FccMetrics defaults) we scrape.
3. Which health check feeds our readiness probe
   (fcc.admin.readers.HealthReader.check() is the natural choice).
4. Runbook entry for "plugin discovery failure" incidents.
5. Runbook entry for "compliance audit failure" incidents.

CONSTRAINTS:
- Readiness probe budget: 500ms.
- No synthetic traffic against upstream FCC.

Deliverable: a 5-section Markdown contract, total 400 to 600
words.

Expected output notes. 5 sections, budget honoured, both runbook entries present.

6. Produce the adoption RFC¶

Personas/subsystems invoked. arch, pm, cw. R.I.S.C.E.A.R. slot: Expected Output + Role Adoption Checklist.

You are the Enterprise Architect (arch). Program Manager (pm)
reviews. Content Writer (cw) copy-edits.

TASK: Produce a single adoption RFC that ties together the outputs
of prompts 1 through 5.

Sections required:
1. Executive summary (200 words).
2. Tier + surfaces decision (from prompts 1 and 2).
3. Compliance scope (from prompt 3).
4. Risk register (from prompt 4).
5. Operational contract (from prompt 5).
6. Adoption timeline with 4 milestones (kickoff, first integration,
   staging soak, production cutover).

CONSTRAINTS:
- Cite docs/for-architects/decision-checklist.md by URL.
- Cite docs/architecture/context-diagram.md for the C4 map.
- Cite the FCC release series we are targeting.

Deliverable: a 6-section Markdown RFC, total 1500 to 2500 words,
ready to circulate to the architecture review board.

Expected output notes. 6 sections, 4 milestones, 3 citations present, word count in range.