Technical Design Documents
Purpose
Index of ShipSolid platform Technical Design Documents. TDDs live in the canonical
technical-designs/ surface. Cohesive sets use a subdir (e.g., technical-designs/grafana-tf/).
Platform TDDs
[stub: platform-tdd-index]— fill this in. Greppable doc-debt marker.
Related
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.