Explanation¶

Background and reasoning. Read these when you want to know why something behaves the way it does, or when a design decision is getting in your way and you want to know whether it is load-bearing.

The design¶

• How the application is assembled: four crates, link-time registration, hand-rolled typestate, and why clap lives in exactly one place.
• How arguments reach a command: passthrough subtrees, what the framework captures, and why the global --output flag is inconsistent.
• What a self-update trusts, and why: compiled-in keys, prehashed signatures only, and why the swap happens last.

The boundaries¶

• What this family does not do: every limitation, unsupported combination and deliberate absence in one place.

The components¶

• rtb-cli: the entry point and its extension points.
• rtb-docs: documentation inside the binary.
• rtb-update: the self-update flow.
• rtb-mcp: commands as Model Context Protocol tools.