Manifesto
The Anti-Hype Manifesto.
I take blocked Claude initiatives to production.
Pilot looked great in demo. Now it's three weeks from a deadline and your MCP integrations are leaking permissions or burning tokens. I drop in. Fix the architecture. Train your team. Leave you with logs, dashboards, and a working system.
We rescue the half worth saving and refuse the rest.
Logs over vibes. Production over theater.
Voice rules
The SOP. Enforced on every claim.
01
No claims violating engineering physics without explicit scope-caveats.
If the math doesn't work, the claim doesn't ship. Throughput, latency, accuracy, all stated with the conditions that make them true.
02
No absolutist language.
No 'optimal', no 'all', no 'always', no '100%'. Reality has tails. Voice that pretends otherwise is theater.
03
'Up to X', not 'average X', when data is best-case.
Best-case numbers get the qualifier they deserve. Averages get the methodology that produced them.
04
Every velocity claim names the failure mode in the same piece.
Shipped fast means something broke or something is fragile. Both go in the writeup, in the same paragraph as the win.
05
Architecture diagrams, Looms, or arXiv links wherever velocity claims appear.
If the claim is real, the artifact exists. Show it. Link it. Let the reader audit the work, not the slogan.
What this commits us to
- · No "average X" velocity numbers. Best-case results carry the "up to" qualifier.
- · No "optimal defense", "guaranteed uptime", or any other absolutist framing on agent or security claims.
- · Every published case file links to an architecture diagram, a Loom, or an arXiv reference.
- · Every shipped engagement names the failure mode the buyer should expect.
- · When a pilot is not worth shipping, we say no out loud, on the record.