Request for Comments (RFCs)¶
Optional pre-ADR design documents for Kollect. RFCs hold exploration, option comparisons, and review feedback before a decision is locked in a numbered Architecture Decision Record.
Process guide: ADR and RFC process
When to add an RFC here¶
| Situation | Prefer |
|---|---|
| Comparing multiple architectures with long trade-off tables | RFC in docs/rfc/ |
| Decision ready to merge with the codebase | ADR in docs/adr/0Txx-….md |
| Small extension of an existing decision | Update the existing ADR |
Many Kollect records skip this directory and land directly as ADRs with status Exploring — that
is fine. Use docs/rfc/ when the write-up would clutter the ADR index or needs iteration before a
number is assigned.
Naming and lifecycle¶
- Filename:
docs/rfc/<kebab-case-topic>.md— no numeric prefix. - Status:
Draft→Review→Accepted|Withdrawn|Superseded. - Promotion: when accepted, add ADR-0Txx in the appropriate theme, link from the RFC header, and set RFC status to Superseded.
Active RFCs¶
| RFC | Topic | Status |
|---|---|---|
| Prometheus attribute metrics | Scalar gauge/counter export from collected numeric attributes (Tier C′) | Proposed (Exploring) |
Exploring ADRs that began as RFC-style work:
| ADR | Title |
|---|---|
| ADR-0304 | Custom-resource metrics and richer aggregation |
| ADR-0501 | Multi-cluster sync topology |
Superseded RFCs¶
| RFC | Topic | Status |
|---|---|---|
| Sink family CRDs | Option C — three family CRDs instead of unified KollectSink |
Superseded → ADR-0414 |
Backlog without RFCs yet¶
Items tracked on Planned features until a draft opens here or in
docs/adr/:
- BigQuery sink (spec needed)
- Azure Blob Storage sink (spec needed)
Recently promoted to Exploring ADRs (formerly backlog):
| ADR | Topic |
|---|---|
| ADR-0604 | Target- and inventory-scoped Prometheus metrics |
| ADR-0605 | OpenTelemetry tracing |