Upload is live. Email and folder are designed. The gate is the same after ingest.

The demo at /demo is upload. Drop a PDF. See extraction. See validation. That is the live path. Five free runs. No signup. That is what you can test today.

The PRD also describes email-in and folder-drop. A clerk sends scans to an inbox. A folder on a shared drive is watched. The scans arrive without the clerk changing muscle memory. Those are designed ingest paths. After ingest, the same validators run. The gate is the same. Only the pipe is different.

Why ingest is not the product

Ingest is how scans arrive. The gate is what happens after. If a vendor demo shows a fancy WhatsApp integration but does not run GSTIN checksum, the integration is a feature and the product is missing. Ingest is not validation. Ingest is not export. Ingest is a pipe.

The product is the gate: GSTIN checksum, HSN format, arithmetic within plus/minus 1 rupee, regime consistency. Pass: export. Fail: review. That is the same whether the scan arrived by upload, email, or folder. Ingest does not change the gate.

What we will not do

We will not market WhatsApp as a product channel unless it ships. If the PRD says "email-in" and the product ships upload, do not put "WhatsApp integration" on the landing page. That is a roadmap item, not a feature.

We will not promise "bulk upload of 10,000 scans" if the demo handles five. The demo is the truth. Your workspace extends it. Bulk is a conversation.

The gate is the product, not the pipe

You upload scans. The gate runs. We measure straight-through. The ingest path is upload. If you want email-in or folder-drop, that is a later conversation. The gate runs on your paper. The pipe is a detail.