01 — Platform Architecture
How the platform is built — views, planes, signals, and the decision record indexes.
Contents
- Architecture Overview
- Platform Overview (C4 L1-L2)
- Data Plane Architecture
- Control Plane Architecture
- Signal Catalog
- Dependency Map
- Faro / RUM Technical Design
- RFCs
- Technical Design Documents
- Architecture Decision Records (ADRs)
- ADR-001: Adopt Eight-Pillar Monorepo Structure
- ADR-002: Adopt Grafana Cloud for Unified Observability
- ADR-005: Adopt AIOps Pillar for Intelligent Operations
- ADR-006: Pin OpenTelemetry Semantic Conventions to v1.26
- ADR-007: Adopt Two-Tier Grafana Alloy Collector Topology
- ADR-008: Adopt Grafana Cloud + OpenTelemetry + Alloy as the ShipSolid Observability Standard
Conventions
- kebab-case filenames; human-readable name in each page’s
title:/ H1. scope: platform— ShipSolid platform content.- Stubs are greppable:
[stub: <name>].
Local graph
Linked from 1 note
Related notes
Signal Forge ADR-005: Separate collector configmaps per deployment mode
Keeps cloud and local Alloy collector configs in separate files rather than one conditional configmap, so each mode's exporters stay explicit and uncoupled.
Signal Forge ADR-003: Span metrics generated before tail sampling
Places the spanmetrics connector ahead of tail_sampling so RED metrics reflect all traffic instead of only the ~25% of traces that survive sampling.
Signal Forge ADR-002: SpanLink for async RabbitMQ propagation (not parent-child)
Uses a SpanLink, not a parent-child span relationship, to connect RabbitMQ consumer spans back to the producer span across async, retry-prone delivery.
Architecture Overview
Signal Forge's topology, service communication, trace propagation, and per-signal pipeline flow across local and Grafana Cloud deployment modes.