Florentin Purcea

InternalInternal operations

A control plane for a 51-project portfolio

Scaling operationsManual work

  1. Issue detected

    Fifty-one projects, sixty-five workers, nine Cloudflare accounts — and no single place that knew what was deployed, broken, stale or ready to launch.

  2. Verification

    Discovery across GitHub and Cloudflare registered every project; daily audits from the edge — performance, accessibility, screenshots — replaced memory with measurements.

  3. Root cause

    Knowledge lived in people's heads and in nine separate dashboards, and "unknown" was silently read as "fine".

  4. Fix

    Health and readiness scores where UNKNOWN is never zero, launch gates with waivers, regression sweeps, 36 MCP tools, and recommendations whose impact is measured after they ship — read-only toward every child repository, by rule.

  5. Measured Attributed

    19 recommendations validated with before/after numbers

    Window: daily audits across 51 projectsCaveat: Before/after measured per recommendation; other changes shipped in the same window were not isolated.

Before / after

What changed, in numbers.

Before0projects with one source of truth
System changeDiscovery across GitHub and Cloudflare, daily edge audits, health and readiness scores, launch gates.
After Delivered51projects registered, audited daily
Measurement window: internal, running daily

What was built

The system, in buyer words.

Discovery across GitHub and Cloudflare, daily audits (performance, accessibility, screenshots) from the edge, health and readiness scores where UNKNOWN is never zero, launch gates with waivers, regression sweeps, and recommendations whose impact is measured after they ship.

Built on
Cloudflare WorkersD1Browser RenderingGitHub APIGoogle SheetsMCP
Analyse my businessWhatsApp