50% Compliance, Not 0%: How a Logging Spike Almost Triggered the Wrong Architecture Rewrite

1 / 2

50% Compliance, Not 0%: How a Logging Spike Almost Triggered the Wrong Architecture Rewrite

DEV Community·FRANCISE LIANG·27 days ago

#71IJtay1

#ai #llm #webagent #playwright #spike #regex

Reading 0:00

15s threshold

TL;DR: I thought my prompt augmentation track was completely broken (compliance=0%) and almost spent 27 hours rewriting plan-and-execute. Turns out the 0% was a regex bug — real value was 50%.

7 chapters + 4 figures (hero / decision matrix quadrantChart / 7-version timeline / data delta tables).

Full version (with mermaid quadrantChart + reproducible spike commands):
https://github.com/franciseliang99-dot/web-agent/blob/main/docs/blog-drafts/2026-05-w5c2-spike-story-final-en.md

Project repo (MIT, ⭐ welcome):
https://github.com/franciseliang99-dot/web-agent

LLM engineering + spike decision methodology + Chrome GPU deadlock diagnosis + regex false-negative lessons. Might save you 27h.

Menu

50% Compliance, Not 0%: How a Logging Spike Almost Triggered the Wrong Architecture Rewrite