HTML3
Start demo →
Hacppify · html3 prototype · rebuilt around the 2026-07 audit

How the HACCP platform should work —
records first, assurance second.

A clickable prototype of the Hacppify redesign for Georgian restaurants and cafés. It replaces the v3 direction, which was built on a false premise: that a specialist must approve a HACCP plan before anyone can record anything. Georgian law (Food/Feed Safety Code Art. 17¹ · Government Decree №173/2010) requires a working system — daily records, real critical limits, corrective actions. No state certificate exists. This prototype makes the working system the product.

Demo cast: კაფე „მარგო" — a Tbilisi café, 8 staff, full track 🧑‍💼 ლევანი (owner) 🔍 დავითი (specialist, „CleanFood") 🧑‍🍳 ნინო · გიორგი · თამარი (staff) 📅 “today" = 11 July, Friday 🌐 UI language: Georgian (this guide is the only English page)

The five rules everything follows

Each rule exists to kill a specific audit finding — the rationale is on the card.

1

Records start on day one. The gate is inverted.

No specialist approval ever blocks a journal. Onboarding generates sensible defaults, and staff can log fridge temperatures ten minutes after signup. The specialist is an assurance layer — they review, leave findings with deadlines, refine limits. A quality badge, never a lock.

⌀ Kills audit finding B1 — v3's approval gate stalled every new business at zero records.
2

Two tracks, decided by a 3-question triage.

A small low-risk café gets the simplified track (Decree №173: ~4 daily checks, no binder). A full kitchen gets the full HACCP track — with true CCPs only. PRPs (basic hygiene) dominate both, because that is the real 80–90% of the work.

⌀ Kills B2 + B3 — v3 forced one-size-fits-all full HACCP and ignored the legal simplified path.
3

The plan is a living set of “safe method" cards.

Modeled on the UK's SFBB: each card states the hazard in plain words → what we do → how we check (linked to a journal) → what to do when it goes wrong. Formal documents are derived on demand by the inspection pack — never maintained by hand.

⌀ Kills B4 — v3 generated a 24-document binder nobody could read, use, or keep current.
4

Idiot-proof kitchen UX.

Staff pages assume a shared wall tablet, wet hands, zero computer skills, Georgian only. Concretely: PIN user-switching (no emails or passwords), nothing tappable under 56px, no free-text typing on any staff path (chips, steppers, presets, photo), emoji as iconography, instant green/red feedback, values pre-filled from yesterday, and an offline indicator (“your record is saved on the device").

⌀ Kills the audit's adoption risk — v3's email logins and typed forms were unusable at the kitchen counter, so records simply wouldn't happen.
5

Legal honesty is the brand.

Cite the real legal basis everywhere; tag every task კანონით (required by law) vs რეკომენდებული (best practice). The headline metric is honest journal completeness (“დღეს 5/6 ჟურნალი"), never an invented compliance percentage. The anti-scam line, verbatim in-product: „კანონი მოითხოვს მოქმედ სისტემას — სერტიფიკატი კანონით არ არსებობს."

⌀ Kills A5 — v3's fake “96.3% compliant" score put us on the same shelf as the ₾3,000 certificate-scam consultants.

What changed vs v3

Same product idea, opposite architecture. Every row traces to an audit finding.

v3 (the old direction) html3 (this prototype)
🔒 Specialist approval gate — journals locked until a plan is approved 🔓 Gate inverted — records from day one; specialist review is a quality badge, never a lock
📚 24-document binder generated up front, maintained forever 🗂️ Living plan of 9 safe-method cards + documents derived on demand by the inspection pack
🎭 Invented “96.3% compliance" score 📊 Honest completeness — “დღეს 5/6 ჟურნალი", with the missing one named
📧 Email + password logins for kitchen staff 🔢 PIN kiosk on a shared tablet — tap your face, type 4 digits
❄️ 6 fake CCPs — thawing, raw washing, sifting treated as critical points 🍳 True CCPs only (cooking, cooling, reheating, hot-holding, frying oil) — the rest are PRPs, labeled as such
🚫 No export — nothing to hand an NFA inspector 🖨️ Inspection pack — printable ledgers in the format inspectors already know
🪦 Write-once staff — no way to offboard an employee who left 👥 Team CRUD with offboarding — the PIN dies instantly, the records stay (the law requires the trail)

Page map & demo walkthrough

17 pages across 4 actors. The numbered badges are the recommended walkthrough order — it follows one business, კაფე „მარგო", from signup to specialist visit. Click any card to open the page.

Footnotes

⚖️
Legal basis, cited honestly. Georgian Law on Food/Feed Safety, Veterinary and Plant Protection Code — Article 17¹ (HACCP-based self-control), and Government Decree №173 of 2010 (hygiene rules; simplified regime for small businesses). The obligation is implementation, phased in for catering from 2023. There is no state-issued HACCP certificate — anyone selling one for ₾3,000 is selling paper. The product says this out loud; the legal banner appears on the triage, done, plan, and inspection-pack pages.
🌡️
Demo limit values are defaults, not doctrine. Fridges 0…+4°C, freezer ≤ −18°C, cooking core ≥ 75°C, hot-holding ≥ 63°C, cooling 60°→8°C within ≤ 4h, reheating ≥ 75°C, frying oil TPM ≤ 24%, receiving chilled ≤ 8°C / frozen ≤ −15°C. Onboarding generates these as sensible starting points; the specialist refines them per business during review (see specialist/review.html, where დავითი tightens the cooling window). Journals run on the defaults in the meantime.
🧪
Prototype notes. Any 4-digit PIN works. Data is not persisted between pages — each page is a self-contained demo of its flow. The journal codes (F01 fridges, F02 cooking, F03 cleaning, F04 open/close, F09 receiving, F10 oil) deliberately match the numbering Georgian consultants and inspectors already use, so the printed pack looks familiar on first contact.