DS·2026·04·20 PUBLIC ADVISORY
DEPARTMENT OF SHIPPING · OFFICE OF THE DEVELOPER GENERAL
ISSUE №07 ROUTING: PUBLIC
APPROVED FOR
PUBLIC
DISSEMINATION

§ 404.1(b)
VIBECODE
DEVELOPER
GENERAL HAS
READ IT

§ 404.2(a)
SO SHOULD YOU
Form DS·001 · Public Health Advisory · 20 April 2026

You Shipped
It & Now
It's Alive.

A cheerful advisory for anyone shipping code they didn't quite read. No rules. Just vibes — the responsible kind.

14 min read · or 6 if you skim Agency: Dept. of Shipping Clearance: UNCLASSIFIED
▸ File copy · DS-2026-07
Notice to developer.
If you built it in an afternoon and don't remember what it does, this document is directed at you.
Take the 2-min assessment → or skip to the playbook — $19 →
§ 01 · Notice
Form DS·002

The Developer General's Warning

Read aloud.
Preferably
to yourself.
Before
merging.

Vibecoding has been found to cause unreasonable confidence in first-time and experienced developers alike, leading to the deployment of unreviewed software to unsuspecting humans.

Side effects may include: mass credential exposure, invoices sent to the wrong continent, payment flows that double-charge, AI agents that declare inbox zero by deleting everything, and the mass psychological event known as "it works on my machine." Consult your staff engineer if symptoms persist beyond the weekend.

§ 02 · Classification
Form DS·003

The Responsibility Spectrum

Every shipped artifact carries a blast radius.

The spectrum below is non-negotiable. Find where your project sits. Act accordingly.

Do not lie to yourself at level 4.

Lv. 01 · LOW
01
A script that renames your vacation photos.
Ship it
Lv. 02 · CAUTION
02
A Chrome extension your team "kind of" relies on.
Skim before merge
Lv. 03 · ELEVATED
03
An internal tool that touches customer data.
Stop vibing
Lv. 04 · HIGH
04
A payments flow you described as "pretty solid."
Dear god, no
Lv. 05 · CRITICAL
05
Medical software you built over a long weekend.
Call a lawyer
Not sure where you land? Take the 2-min assessment →
§ 03 · Self-Cert
Form DS·005

Are You Shipping
Under the Influence?

§ 04 · Casefile
Form DS·011

Field Reports
filed by anonymous shippers

§ 05 · The Responsible Shipper's Oath

I swear to read my own code before I deploy it. Never to call a payments integration "vibes-based." And to remember users are real people who did not consent to being beta testers.

Pledge yours — take the oath below.Signed ✓
Share on X →
§ 06 · Field Manual
Form DS·019

The Playbook

$19USD
PDF · ePub · Templates · ~90 pages

You know your score.
Now fix it.

Not another ebook. A field manual for the vibecoding era — outcomes you can ship tomorrow, not theory you'll forget by Friday.

Built for: solo devs · AI-first builders · indie hackers · anyone shipping code they didn't read line-by-line.
90-day money-back guarantee. If the Playbook doesn't save you one weekend, email us and we'll refund it. No forms, no questions.
Get the playbook → $19 Free sample chapter →
  • 01
    Never commit a secret againThe 10-minute audit that catches keys, tokens, and .env files before git does.
  • 02
    Stop shipping Friday at 5pmThe decision tree that answers "should I deploy this?" in 60 seconds. Print it. Tape it to your monitor.
  • 03
    Audit any project in 10 minutesThe graduation checklist — from "works on my machine" to "safe for other humans." Copy-paste ready.
  • 04
    Make the AI build it safely30 battle-tested prompts that bake bcrypt, rate limits, and CSRF into the first draft. Works in Claude, Cursor, Codex.
  • 05
    Keep your agents on a leashHow to scope permissions, delegate safely, and revoke access before things go sideways.
  • +
    Learn from other people's disasters12 real postmortems. What broke, the decision point, the principle violated, the fix.