Architecture Decision Records¶
This directory contains Architecture Decision Records (ADRs) for the FCC framework. ADRs document significant technical decisions, their context, and their consequences.
ADR Index¶
| ADR | Title | Status | Date |
|---|---|---|---|
| ADR-001 | Book Series Structure | Accepted | 2026-03-29 |
| ADR-002 | Docs from Code via AST | Accepted | 2026-03-29 |
| ADR-003 | Knowledge Graph Export | Accepted | 2026-03-29 |
| ADR-004 | Embedding Provider Protocol | Accepted | 2026-03-29 |
| ADR-005 | Federated KG Namespace | Accepted | 2026-03-29 |
| ADR-006 | Dual-Bus Event Architecture (PAOMBus + UXBus + LaneRouter) | Accepted | 2026-04-22 |
| ADR-007 | SAFe Alignment Skeleton | Accepted | 2026-04-22 |
| ADR-008 | POLARIS (ice_ext) Absorption + Stable Bridge Promotion | Accepted | 2026-04-22 |
| ADR-009 | Universal Services Coordination Pattern (Superset-First) | Accepted | 2026-04-22 |
| ADR-010 | Six Pillars Architecture for v1.5.0 | Accepted | 2026-04-22 |
| ADR-011 | GraphRAG with Zachman-Cell Filtering | Accepted | 2026-04-22 |
| ADR-012 | CRDT-Backed Real-Time Multi-User Collaboration | Accepted | 2026-04-22 |
| ADR-013 | Bidirectional Federation with Per-Namespace Conflict Policy | Accepted | 2026-04-22 |
| ADR-014 | Chromium sandbox + puppeteer-config for mermaid rendering | Accepted | 2026-04-24 |
ADR Process¶
- Propose. Create a new ADR file with status "Proposed."
- Discuss. Review the ADR with stakeholders.
- Accept or Reject. Update the status based on the decision.
- Supersede (optional). If a later decision replaces this one, update the status to "Superseded by ADR-NNN."
Template¶
# ADR-NNN: Title
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Rejected | Superseded
## Context
What is the issue that we are seeing that motivates this decision?
## Decision
What is the change that we are proposing and/or doing?
## Consequences
What becomes easier or more difficult to do because of this change?