A-00 · ShipStack · a Claude Code framework by ViaVia
In 2026 the hard part isn't getting AI to ship — it's trusting what it shipped without asking.
An AI production line for Flutter apps — a human gate on every call.
Seven AI departments take an app from market research to the App Store as a five-stage line. Agents advise and execute; you sign the GO/NO-GO at every consequential step. And they're held to a written engineering standard — by hooks that pass or fail automatically, not a style guide they might ignore.
Discipline that's enforced, not hoped.
- Stage
- A-01
- Scale
- 1:1
- Drawn
- R&D dept
- Signed
- Human
A-01 — A-05 · The line
Five stages. A gate between each.
Clone ShipStack for an app, describe the idea, and the line runs: seven AI departments execute five stages, each writing deliverables the next reads — and stopping at a human yes before every consequential call.
- A-01 Gate
Idea → Validation
R&D maps the market — GO/NO-GO before code.
- A-02 Gate
Validation → Design
Model, pricing, UI direction — gated on you.
- A-03 Gate
Design → Build
Architecture and app — built to one standard.
- A-04 Gate
Build → Ship
Store assets, legal, submission — staged for sign-off.
- A-05 Gate
Post-Launch
Maintenance and iteration — advised, then approved.
A-06 · The departments
Seven desks the dossier passes through.
Each department is a markdown role with its own tool allow-list. They advise and draft; the consequential calls wait for you.
- 01 Product Owner Holds scope — every brief traces here.
- 02 R&D Market evidence — no build on a hunch.
- 03 Financial Unit economics — pricing you sign off.
- 04 Business Model and positioning — one page, gated.
- 05 UI/UX One design direction — approved before pixels.
- 06 Marketing Store listing and launch — drafted for review.
- 07 Technical Flutter build — production standard, golden-tested.
A-07 · The standard
The agents work to a code, not a vibe.
Left alone, an agent takes the shortest path and amplifies whatever it finds — each feature quietly degrading the next. So ShipStack's agents are held to a written agentic-engineering playbook, and the non-negotiables are enforced by hooks that pass or fail on their own. The gate decides direction; the standard keeps the output production-grade.
- STD-01 Enforced
Design first
Refactor before adding — agents amplify what they find.
- STD-02 Enforced
No dead code
Stop hook flags any uncalled export.
- STD-03 Enforced
No useless tests
Behaviour through the public surface, not internals.
- STD-04 Enforced
Complexity < 10
Analyzer gates each method before done.
- STD-05 Enforced
Respect layers
Domain imports no HTTP, DB or filesystem.
- STD-06 Enforced
Tested for real
Mutation runs flip the code; weak tests fail.
From the ViaVia agentic-engineering playbook · hooks run at edit, at done, and at commit.
A-08 · The technical standard
What the Technical desk builds against.
On top of the playbook, the Technical department builds to one deep Flutter production standard — Riverpod, feature-first architecture, golden tests, RLS, EU accessibility, and GDPR legal templates tied to the exact stack. The point isn't raw code generation; it's an opinionated, repeatable line with a human inspector at every gate.
A-09 · Status
Internal · waitlistHumans decide. The standard holds.
ShipStack is the opposite of a fire-and-forget "AI employee". Every pricing call, brand choice, architecture decision and store submission stops for a human yes — and between those gates the playbook's hooks hold the line. Today it's an internal framework ViaVia uses to build and maintain its own Flutter apps — not a self-serve product you can sign up for yet. Even the name is provisional.
A-10 · Waitlist
Run the line for your apps.
We're planning to open ShipStack to a few teams beyond ViaVia. Tell us what you're building and we'll be in touch as we open it up. No signup, no billing — just an email to the waitlist.
Pitch us your apphello@viavia.solutions · Internal · waitlist