Shiproom OS

Comment

Who it is for

Shiproom OS is for solo builders, hackathon teams, and small AI product teams who can generate ideas quickly but still need a clear launch packet that a judge, teammate, or next AI agent can trust.

The problem

AI can produce a lot of text, but submissions still fail when the target user is vague, the first-version scope is unclear, the proof checklist is missing, and no one can tell what is real versus planned.

How AI is used

AI turns a rough product idea into a structured launch packet: target user, problem, first-version scope, proof checklist, launch copy, evidence ledger, learning loop, next-agent handoff, and safe Novus/Pendo activation-event map. The app keeps claims bounded with deterministic sections, local storage, verifier scripts, and explicit proof gates.

Inspiration

AI has made starting a product easier than ever. The hard part is still the last mile: naming a real user, narrowing the scope, proving that the product works, writing launch copy, and leaving enough evidence that another person or AI agent can continue responsibly. Shiproom OS was built for that gap.

What it does

Shiproom OS turns one rough idea into a launch packet with target user, problem, first-version scope, proof checklist, launch copy, shipping timeline, evidence ledger, learning loop, next-agent handoff, JSON export, Markdown submission brief, saved local snapshots, and a safe Novus/Pendo activation-event map.

How it was built

The MVP is a static web app with deterministic generation logic, local browser storage, Playwright verification, GitHub Pages deployment, no-secrets checks, README review-hub checks, claim-boundary checks, and a guarded Novus/Pendo install helper. A real Novus/Pendo Public App ID is installed, and the public repository includes the dashboard proof screenshot plus a verifier for the installed snippet and proof file.

What is proven

Challenges

The main challenge was keeping the project honest. It would have been easy to make a polished generator and overclaim the rest. Instead, the app and README separate what is proven, what is only a draft, and what still needs human approval.

What I am proud of

The product does not stop at generating copy. It creates a reviewable launch packet: who the product is for, what version one includes, what proof is still missing, how launch should be explained, what should be measured, and what the next human or AI agent needs to know.

What's next

Next, Shiproom OS should connect saved launch packets to real activation data, compare different launch attempts, and help teams decide whether to keep shipping, narrow scope, or stop.

2026-06-11 Novus resubmission proof

After the organizer note, I reconnected Novus through GitHub and rechecked the deployed Shiproom OS app again. Novus shows Scan ✓, the public App ID, Shiproom install targets, and visitor metadata detection. I also added a public verifier that opens the deployed GitHub Pages app, triggers a launch-packet interaction, and confirms pendo, pendo.track, pendo.initialize, cdn.pendo.io, and data.pendo.io requests.

Resubmission proof: https://raw.githubusercontent.com/daideguchi/shiproom-os/main/submission/novus-resubmission-proof-2026-06-11.md Public live screenshot: https://raw.githubusercontent.com/daideguchi/shiproom-os/main/media/shiproom-public-novus-live-2026-06-11.png Verification commit: https://github.com/daideguchi/shiproom-os/commit/abb04b7

Built With

Share this project:

Updates