Geaux Digital Media
Proof

Real problems, and how they were actually solved

Seven engagements, written up honestly — including the diagnosis that turned out to be wrong, the fix we recommended against, and the time our own tooling set off our own alarm.

What these are, and what they are not

Client names, industries, vendors, dollar figures, and order references are removed. The engineering is intact, because the engineering is the point — and because a write-up you cannot check the reasoning of is a brochure.

These show capability, not outcomes. There is no named client here and no before/after business metric, because publishing those requires a client’s consent and a baseline measured before the work started. We would rather tell you that plainly than dress seven diagnoses up as case studies.

If you want the version with a name and a number attached, ask — that conversation is a consent conversation, and it is one we are actively having.

Integration risk · API access · log forensics

A third-party integration was cancelling paid orders

Orders were cancelled seconds after the card was charged. Everything inside the application said the application was not doing it.

IntegrationTechnical support
Read
Plugin conflict · display vs. data

A free item that appeared to be a charge

Customers said they were being billed for a free gift. Nobody was being charged — and the obvious fix would have missed the defect entirely.

IntegrationTechnical support
Read
Infrastructure · proxy chains

A CDN header broke a payment gateway

An authentication error several layers away from its cause. The obvious fix was editing a credential by hand — which would not have held.

ArchitectureIntegration
Read
Infrastructure · irreversible-change method

Reclaiming storage when there is no room to back up

36 GB against a much smaller plan, and no space to take a backup first. One reframe made most of the problem reversible.

ArchitectureTechnical support
Read
Judgment · second-order effects

The fix we recommended against

A single toggle would have stopped the attack. It would also have broken fulfillment, inventory, and product data — and nobody would have connected the two.

ArchitectureTechnical support
Read
Verification · trusted-set blind spots

Our own scanner flagged our own code

Two checks, two answers, and no way from the outside to tell which was wrong. The uncomfortable half is the useful half.

ArchitectureTechnical support
Read
AI-native operating model

How we run our own operations

We sell business systems and automation. The most direct evidence that we mean it is how we run ourselves — the one case here with no client in it.

AutomationAI
Read
Get started

Have one of these already?

Most of what is on this page started as somebody saying “something is wrong and we can’t work out what.” If that is where you are, that is a good place to start from.