WholeStack
Bring an existing app Sign in

Welcome to intent engineering.

Connect a repository
Intent Specification LayerIndependent verificationProduction runtime proofDesignDNA compilerManaged deployment

Evidence before confidence

Software should end in proof. not a promise.

WholeStack closes the gap between “the code exists” and “the business can trust it.” Every release has to survive executable requirements, adversarial checks, and runtime evidence.

/P0

29/29

Truth gates passed

Representative end-to-end proof pack

/P1

0

Successful no-ops

Commands either change reality or fail closed

/P2

382

Contract checks

Behavioral guarantees across the compiler spine

/P3

1,018

Compiler tests

Deterministic coverage for interface generation

One continuous evidence chain

ISLZetaDesignDNAShipGate

The WholeStack system

Intent, all the way down.

Four layers turn a business model into an application that can explain what it does, prove what it enforces, and stay operable after launch.

/L0Intent Specification Layer

Capture the business before generating the interface.

ISL turns records, roles, permissions, workflows, invariants, and exceptions into an executable contract. The source of truth is what the business means—not whichever component was generated first.

ProducesExecutable business contract

Independent release authority

No “trust us, we passed.”

ShipGate sits outside the generation loop. It attempts to disprove the application, records the evidence, and returns the only verdict that matters at release time.

01BUILDArtifacts resolve
02TESTBehavior executes
03PROVEClaims survive
04SHIPReceipt sealed
Run ShipGate on an existing repository ↗
ShipGate Independent release authority

Attestation№ SG-029

Artifact
summit-roofing
Command
verify --runtime
Issued
2026-04-11 00:23:14Z
Coverage
29 / 29 gates
  1. 00:00.041CONTRACTISL parsed · 143 clausesPASS
  2. 00:02.284BUILDWeb, API, data, authPASS
  3. 00:08.938EFFECTSNo successful no-opsPASS
  4. 00:14.327SECURITYRole boundaries enforcedPASS
  5. 00:21.702RUNTIMEProduction behavior replayedPASS
  6. 00:23.114ATTESTEvidence bundle sealedPASS
Final verdictSHIP
ShipGate
Sealed
sha256 · 8f2c…91aded25519 signedshipgate.dev

One compiler, many operating models

Start with what you do.
We’ll build how it works.

Choose a proven software shape, then let Zeta capture what makes your operation different. The category narrows the problem without trapping the result in a template.

/C01

CRM & Pipeline

Leads, accounts, follow-up, approvals, and revenue workflows.

12 operating patterns
/C02

Booking & Scheduling

Availability, resources, staff, reminders, payments, and exceptions.

9 operating patterns
/C03

Commerce

Catalogs, orders, subscriptions, fulfillment, and customer portals.

11 operating patterns
/C04

Marketplaces

Multi-party inventory, matching, fees, trust, and transaction states.

8 operating patterns
/C05

Field Service

Dispatch, crews, estimates, jobs, inspections, and proof of work.

10 operating patterns
/C06

Inventory & Resale

Acquisition, grading, storage, pricing, listing, and margin control.

7 operating patterns
/C07

Professional Services

Intake, engagements, documents, time, billing, and client access.

9 operating patterns
/C08

Your Operating Model

When the category ends, ISL captures the rules that become your advantage.

Define it with Zeta ↗

Position

Say what you mean, and mean what you say.

A new discipline

Intent engineering

in·tent en·gi·neer·ing (n.) — writing down what must be true about a business, so a machine can compile it, execute it, and prove it. Prompt engineering asks a model nicely. Intent engineering leaves a receipt.

Prompt engineering
Intent engineering
You write
A better sentence
A contract with proof obligations
The machine returns
Text that looks like code
A compiled system and its evidence
When something is wrong
Re-prompt and hope
Patch one clause, recompile, re-prove
What you can hand an auditor
A chat log
A signed attestation

Pricing law

Free to make.
Pay to ship.

You are not buying tokens, messages, or seats. You are buying one thing no other builder can sell: a signed proof that the software does what your business said. Prototypes cost us cents, so they cost you nothing.

  • 01No credits. No token meters. One paid action: ship.
  • 02Every ship is full proof. Rigor is never an add-on.
  • 03NO_SHIP costs nothing. You pay for proof, not for trying.
  • 04Same price at every door. Founder or agency, one law.
WholeStackReceipt · proof-carrying software
№ 0001
  1. /01

    Build

    Unlimited prototypes. Every open question listed. Labelled unverified. No card required.

    $0always
  2. /02

    Ship

    Build-it-right questions, full evidence chain, signed shipgate.json, deployment, source export. Charged only on SHIP.

    $299once, per app
  3. /03

    Live

    Hosting, re-verification on every change, live-assurance receipts, evidence archive. Change requests included.

    $79per month, per app
  4. /04

    White-label

    Your name on the contract and the attestation. Client workspaces, white-label receipts, volume pricing on ships. Same three items above—nothing forked.

    Talk to ussame law

Start with reality

Software that proves itself

Zeta captures the intent. WholeStack compiles the system. ShipGate decides whether it has earned the right to launch.

Build with WholeStack ↗Bring an existing app ↗