Pick a typeface pairing and scale that actually matches how the brand talks, instead of two fonts that just look nice together

Help me choose a typography system — not just "a nice font pairing," but a full decision covering typeface pairing, a type scale, and usage rules, reasoned from how this brand actually communicates.

BRAND VOICE
Confident and no-nonsense — we're a data infrastructure company that talks to engineers directly, not a consumer brand trying to be warm.

REAL CONTENT SAMPLE
'Your pipeline drops packets under load. We show you exactly which node, at exactly which second, with a one-command rollback.' — from the homepage hero.

CONSTRAINTS
Must be free for commercial web use (Google Fonts or equivalent) and must render well at small sizes in a data-dense dashboard UI.

WHAT NEEDS TO SUPPORT THIS DECISION
Marketing website, product dashboard UI, and PDF export of usage reports.

First, extract from the real content sample what the brand voice actually does on the page — is it terse and declarative, does it lean on long explanatory sentences, does it use a lot of numbers and data callouts — and connect specific typeface characteristics (x-height, contrast between thick/thin strokes, geometric versus humanist letterforms) to that observed voice, rather than describing fonts in isolation with adjectives like "modern" or "friendly" that don't connect back to anything concrete about this brand. Propose exactly one heading typeface and one body typeface (not a shortlist to choose from later), and justify the pairing specifically in terms of contrast that serves a purpose — different enough that headings are instantly distinguishable from body text at a glance, similar enough in mood that they don't read as two unrelated brands sharing a page. State whether both fonts are freely licensed for the listed platforms or whether a licensing check is needed before this becomes final — do not assume licensing is fine. Propose a type scale (the actual size/weight/line-height steps from H1 down to caption text) using a stated ratio or rationale, not arbitrary numbers. Write explicit rules for where the heading font is and is not allowed to appear — a common failure is a heading typeface creeping into body copy or UI buttons where it hurts readability at small sizes.

WHAT NOT TO DO
Do not recommend a currently-trendy pairing purely because it's popular in the design community right now — every recommendation must trace back to the voice analysis or the stated constraints. Do not propose more than one option per role; a shortlist defers the actual decision rather than making it.

OUTPUT FORMAT
1. Voice-to-letterform reasoning (short paragraph).
2. The chosen pairing (heading + body) with the specific justification.
3. Licensing status for the listed platforms, flagged if unconfirmed.
4. The type scale as a table (level, size, weight, line-height).
5. Usage rules: where the heading font is and isn't allowed to appear.