Lenss to audit rfcs

Audit an RFC against the goal it claims to meet.

System design and architecture reviews that start from the success criterion, not the diagram.

Works on: RFCs and design docs · Architecture decision records · Capacity and migration plans

How the audit runs

  1. 01

    Pin the objective

    The success criterion the design must meet, stated as a measurable target, separated from the solution it proposes.

  2. 02

    Quote what it takes for granted

    Each assumption the design rests on, tied to the exact sentence that carries it.

  3. 03

    Find the operational limit

    The capacity, latency or cost ceiling that binds first, and whether the design accounts for it.

  4. 04

    Compute the breaking point

    From the RFC's own figures, the value at which the design stops meeting its criterion.

Typical findings

Average vs tail

Caches, queues and retries that improve the mean while the SLO is a percentile.

Hidden ceilings

Throughput, connection or budget limits stated once and ignored in the plan.

Coupling

Behaviour the design needs from other services or teams, never agreed.

Worked example

Stakes$9,400 / mo · read path for every catalog pageAdversarial Review · 1/4

Source draft

591 chars

RFC: Redis cluster in front of the catalog database

Platform team · status: proposed

Problem. Catalog reads peak at 18,000 requests per second and our p99 read latency is 420 ms. The SLO is a p99 under 150 ms. Every catalog query against Postgres takes between 380 and 450 ms at peak. Proposal. Put a six-node Redis cluster in front of the catalog read path. A cache hit returns in 4 ms. A miss falls through to Postgres and populates the key. We expect a 90% hit rate based on the 80/20 access pattern we see in logs. Cost. $9,400 per month for the cluster. Two engineers for three weeks. Success. p99 catalog read latency under 150 ms at peak within one sprint of launch.

Adversarial review

pinned · quoted · computed
01

Pinned objective

p99 catalog read latency under 150 ms at 18,000 req/s.

Underneath: The success metric is a tail percentile; the proposal reasons about the average request.

02

Hidden assumption

A 90% hit rate moves the p99. It does not: p99 is set by the slowest 1% of reads, and with 10% of reads missing, that slowest 1% is all misses.

“We expect a 90% hit rate based on the 80/20 access pattern we see in logs.”
verbatim · highlighted in source

If it’s wrong: The cluster ships, average latency falls, and the SLO still fails at the same 380–450 ms tail.

03

Flip threshold

Cache hit rate at which p99 can fall under 150 ms

≥ 99.0%RFC expects 90%
Figures behind the threshold
Miss path: Postgres + cache lookup384–454 ms
Every miss vs the 150 ms SLOover, always
p99 ≤ 150 ms needs misses ≤1.0% of reads
p99 at the expected 90% hit rate≥ 384 ms

At 90% the SLO fails. The decision turns on hit rate above 99%, not on the cluster.

Cheapest test: Replay one peak hour of read logs against an LRU of the planned size and measure the miss rate before provisioning.

Used most by Engineers

Audit your own draft now.

Paste up to 24,000 characters. You get the objective, every quoted assumption, the tensions, the flip threshold and a hardened rewrite.

Audit your draft