RTerm Systems Thinking — Problem Solving & Breaking Down Complex Systems

This skill is the operating manual for attacking hard, ambiguous systems problems with RTerm. Most system-design frameworks stop at the whiteboard. RTerm goes further: the same agent that helps you decompose the problem, estimate the load, and pick the trade-offs can then build, measure, and operate the real thing — across SSH/WinRM/Serial fleets, with playbooks, MOP approvals, SRE telemetry, governance, and a tamper-evident audit trail.

Use it when the request sounds like:

• "Design / break down / reason about system X" (a payment switch, a URL shortener, a data platform, an observability stack, a fraud engine, a multi-region deployment).
• "How much capacity do we need?" (users → QPS → storage → bandwidth → node count).
• "What's the right trade-off here?" (consistency vs availability, push vs pull, sync vs async, SQL vs NoSQL, monolith vs services).
• "Take this ambiguous blob and turn it into bounded sub-systems we can build."
• "Prove the design works on real infrastructure" — then deploy it, measure it, and operate it.

1. The RTerm systems-thinking loop