# Observability
All Observability notes →5 — Partial Results vs Fail-Fast
Three policies for partial failures in fan-out calls: fail-fast (abort if any dependency fails), best-effort (return what succeeded and surface what's missing), and minimum quorum (K-of-N replicas). Default to fail-fast unless correctness explicitly permits partial data.
1 — SLIs
Covers choosing a Service Level Indicator that actually reflects user-perceived reliability, not just what's easiest to measure.
3 — Error Budgets
Covers treating the error budget as a spendable risk resource that governs release velocity, not a compliance scorecard.
4 — Incident Detection
Covers the telemetry-to-detection path — how observability signals trigger the moment an incident is declared.
6 — Postmortems
Covers writing a blameless postmortem that traces the incident timeline back to instrumentation and observability gaps, not just the code fix.
7 — Chaos Engineering
Covers using deliberate fault injection to validate that observability signals actually fire the way an incident response plan assumes.
# Projects
All Projects notes →Error Budget Policy
How error budgets are calculated, consumed, and enforced.
Production Readiness Review (PRR)
The Production Readiness Review gate — what a service must satisfy before prod.
03 — Reliability Engineering
The SRE practice: charter, SLOs, error budgets, and the prod-readiness gate.
Reliability Review Archive
Archive of completed reliability / PRR reviews.
SLO Registry
Registry of all SLOs across ShipSolid platform services.
SRE Charter
The SRE practice charter — scope, principles, and how reliability work is prioritized.
KPIs, SLIs, SLOs & SLAs
Defines the **metrics hierarchy** used to align technical observability signals with business
Production Readiness Review Template
- **Service**: [FILL] - **Service Team TL**: [FILL]
SLO Document Template
- **Service**: [Full service name] - **Owner**: [Team name]
# Ci Cd
All Ci Cd notes →1 — High Availability
Covers designing the CI/CD control plane itself for high availability so pipeline outages don't become an organization-wide delivery outage.
2 — Scaling Pipeline Platforms
Covers horizontal and vertical scaling strategies for build farms, runners, and orchestration control planes as pipeline volume grows.
3 — Disaster Recovery
Covers backup, failover, and recovery procedures for CI/CD control planes, artifact stores, and pipeline state.
4 — Platform Capacity Planning
Covers forecasting build and deployment demand and provisioning runner and orchestration capacity ahead of it.
5 — Incident Response
Covers incident response specific to CI/CD platform outages — detection, triage, and communication when the delivery system itself is down.
# Infrastructure Platform Engineering
All Infrastructure Platform Engineering notes →1 — High Availability
Covers high availability design for infrastructure platform components and the workloads they provision.
2 — Disaster Recovery
Covers disaster recovery planning for infrastructure platforms — RTO/RPO targets and cross-region recovery.
3 — Infrastructure Scaling
Covers scaling strategy for infrastructure platform components under growing consumer and workload demand.
4 — Infrastructure Resilience
Covers resilience patterns for infrastructure platforms — graceful degradation and fault isolation.
5 — Infrastructure Incident Response
Covers incident response specific to infrastructure platform failures — provisioning outages, control-plane degradation, and recovery.
# Patterns
All Patterns notes →01 — Resilience Patterns
Graceful Degradation, Load Shedding, Fail Fast, and Self-Healing — the system-level resilience postures that sit above any single pattern like Circuit Breaker or Bulkhead.
02 — Availability Patterns
High Availability, Disaster Recovery, Backup/Restore, and Chaos Engineering — the practices that turn an availability target into something actually tested, not just assumed.
03 — Scalability Patterns
Horizontal vs. Vertical Scaling, Elasticity, and Partitioning — the levers for handling more load, and why horizontal scaling is usually the one worth designing for first.
Patterns
A book-shaped table of contents for reusable engineering patterns spanning object-oriented design, enterprise architecture, distributed systems, messaging, APIs, cloud infrastructure, observability, security, concurrency, AI/agentic systems, and organizational design — grounded in production experience at scale.
# System Design
All System Design notes →Chapter 1 — Reliability: SLI, SLO, SLA & Error Budgets
How SLIs roll up into SLOs, SLOs into error budgets, and error budgets into the release-velocity decisions a principal engineer actually gets asked to defend.
Chapter 2 — Resilience Patterns
Retry, timeout, circuit breaker, bulkhead, hedging, and adaptive concurrency as the patterns that contain a failure instead of letting it cascade.
Chapter 3 — Disaster Recovery
RTO and RPO as the two numbers that actually define a DR strategy, and the backup/restore and multi-region trade-offs behind hitting them.
Chapter 4 — Chaos Engineering & Game Days
Fault injection and game days as the practice of finding a system's failure modes on your own schedule instead of production's.