Proof-first presentation

deet caught on because the story was testable.

Every surface ships a runnable proof: the command, the receipt, and the artifact. That consistency is why the presentation stuck.

Open playgroundRead the playbook

Proof in minutes

A two-minute loop that ends with a green check and real output files.

Receipts, not rhetoric

Commands, diffs, and artifacts stand in for claims and slides.

Portable outputs

SQL and contracts run anywhere, so adoption never feels like lock-in.

Shareable context

Templates and the .deet context file make every demo repeatable.

The receipts stack

deet never asks for belief. It ships artifacts you can open, run, and review in Git.

Typecheck receipt

Typed errors with file + line + hint.

SQL receipt

Compiled SQL per model, ready for your warehouse.

Contract receipt

TypeScript contracts for app integration.

Context receipt

.deet snapshot for LLMs and onboarding.

Proof loop
$ deet check
✓ 12 models type-checked
$ deet compile --target duckdb --out dist
✓ Wrote dist/sql/user_metrics.sql
$ deet contract --out contracts
✓ Wrote contracts/user_metrics.d.ts

The loop is the pitch

We lead with commands because they make the promise measurable. If the loop is fast, the product is fast. If the artifacts exist, the promise is real.

Run the quickstartSee the playbook
$deet check
$deet compile --target duckdb --out dist
$deet contract --out contracts

Build with receipts from day one

The method is simple: ship the loop, ship the artifacts, and let the product speak.

Install the CLIExplore the .deet file