Brief
Elite Metal Welding Solutions is a family-run mobile welding contractor in the Cragin neighborhood of Chicago, founded 2013, operating a six-service taxonomy against a 15-client commercial roster. The engagement entered with no production website, a NAP triangle that needed reconciling across three sources, and no brand system. The deliverable was a launch — copy-locked content, ten pages live, performance verified, Cloudflare in front, and a monthly operating cadence that would not require a rebuild in six months.
Constraints
Zero production pages at engagement open. NAP inconsistencies across three sources (resolved in Discovery to 918 Grace St., (847) 340-2115). No brand system — no color palette, no typography lock, no voice contract. Mid-build, an incident designated V12 deployed a greedy regex that stripped nine pages from a working build state — a recoverable mistake that produced both a recovery trace and a permanent guardrail (V11 mbe-certified ALLOW regex).
Approach
The engagement ran under the EMS 360 Mark-Ops master plan — seven workstreams on a pause-resilient monthly cadence from M0 through M8 and beyond. Discovery first (NAP + taxonomy + roster). Brand next (33-swatch OKLCH Forge Premium palette, Oswald + Inter typography lock, blend-voice contract). Then a D4 content pack that copy-locked all ten launch pages before any block-builder script touched WordPress. D5 and D7 shipped paste-ready Kadence execution kits with bootstrap, helpers, and per-page section assemblies. D8 ran publish-flip; D10 closed Cloudflare onboarding; D11 hardened cache with the H4 rule.
Implementation
The publish-flip on D8 registered ten of ten pages at HTTP 200, caught a maintenance-plugin gate before it bricked the launch, and codified the REST nonce-rotation workaround as a permanent guardrail (Rule AJ). D9 deployed capability strips and cross-service grids, attached four-type Schema JSON-LD, and ran Lighthouse mobile against the six service pages — LCP landed at 786 ms.
D10 closed Cloudflare onboarding through §6 — DNS lift, Cache Rule with wp-admin bypass, scoped `cfut_` API token, WP Rocket bridged via the official Cloudflare plugin v4.14.2, and a `cf-ray` header verifying delivery from the ORD point of presence. D11 layered the H4 cache hardening rule and observed HIT on five paths with LCP at 226 ms post-cache.
Reflection
The engagement compressed because the discipline preceded the build. Discovery resolved the NAP triangle before any page was scaffolded. The D4 content pack locked copy before any execution kit was paste-ready. By the time D8 fired publish-flip, the failure modes had been narrowed to two — a maintenance-plugin gate and a REST nonce-rotation quirk — both of which were caught at the gate, neutralized, and converted into permanent rules. Trades work on Kadence does not require throwing out WordPress; it requires running the build the way a welder runs a seam.
The engagement compressed because the discipline preceded the build. Discovery resolved the NAP triangle before any page was scaffolded. The D4 content pack locked copy before any execution kit was paste-ready. By the time D8 fired publish-flip, the failure modes had been narrowed to two — a maintenance-plugin gate and a REST nonce-rotation quirk — both of which were caught at the gate, neutralized, and converted into permanent rules. Trades work on Kadence does not require throwing out WordPress; it requires running the build the way a welder runs a seam.
