VERIFICATION-PHASE1.md — Phase 1 · Database complete · Verification Sheet
Owner contract per PLANNING §97 + PHASES-GUIDE.md §Phase 1: you check the three layers (automated proof, this sheet, your own spot-check) and sign. (You intended this phase when saying "phase 2" — the sequencing correction is PLANNING §109; the engine sheet docs/VERIFICATION-PHASE2.md remains open for your sign alongside.)
What changed (2026-09-06)
- Full field audit against your paperwork (FIELDMAP): Party, Yarn, Loom and Flange masters are complete (KEEP — the form lets you enter everything the paper has: party address/GST/PAN, yarn count+type+ticket, flange no+beam size, loom class/shifts). Design master had gaps — fixed: the warping-rate field was never saved (the quote's warping leg was always ₹0 — same class as a bug we caught in the engine), plus GLM, design GST% and warp-shrinkage% are now enterable, and multi-yarn rows can carry per-row rate + GST + incl/excl (your costing app's model).
- Status/dropdown value sets formalized — one documented table (docs/VALUE-SETS.md): every enum column's formal set + live range; the app writes only the formal set; new values must go through the doc.
- Tenancy + migrations verified — all 27 tables carry the tenant/setup seams; migration series 0000–0008 is valid and the live database has zero drift from the schema snapshots.
- Migration 0009 applied — the Phase-1 gap columns landed: design GST%/shrinkage, beam weight, booking gross, partner-GP pairing, transfer-year tags, dispatch delivery/bill/tag fields, and the unique dedupe index on events. 609 design records preserved in the rebuild.
- Your imported data — untouched. (See the counts below.)
Why
Every screen reads these tables; the filing cabinet being complete and true to your paperwork is what makes "fields in each form correct" (your words) — this phase was the thing you meant.
How it is proven (automated)
- 141 unit tests green — incl. the new masters pins (warping/GLM/GST/ shrink authorable, rows with rate/GST quints, category Transport) and all prior engine/ops/capture pins.
- Journey suite 53/53 against the live deployed site on the migrated database.
- Every change committed + pushed (4724e0d); decisions in PLANNING §109–§110, BUILD-LOG 57–59, the §Phase-1 ledger in COMPLETION.md.
Your 5-minute spot-check (per PHASES-GUIDE §Phase 1)
| # | Check | What you should see |
|---|---|---|
| 1 | Masters → Party: open a few party records (https://trading.tynolabs.com/masters → Party) | every paper field present: name, category (incl. Transport), address/city/taluka/district/PIN/state, mobile, phone, email, due days, broker, opening balance, PAN, GST No |
| 2 | Masters → Yarn: open Yarn records | count + type (Cotton/OE/Denier/Lycra) + ticket, count system Ne/D/Tex |
| 3 | Masters → Design: open an existing design AND open the Add/edit form | reed/pick/reed-space, warp+weft counts, weave, width, UTL, HSN, lasa/L2L, size add-on, weft waste, other expense, all rates (warp/weft/sizing/job/WARPING), GLM, GSM, GST%, warp-shrinkage%, multi-row yarn grid |
| 4 | Create one of each (a party, a yarn, a design) with a real example of yours | values save exactly as typed; the design's kg/m recompute appears |
| 5 | Imported data intact | counts match: 909 contracts · 6,688 beams · 2,048 lots · 468 parties (open a few; nothing changed) |
Any field you expected and didn't find → it goes in as a gap (say the field and the screen). Anything from your data missing → reopen.
Owner calls that gate the sheet (both pre-listed)
- GSTIN (decision ①) — the empty GSTIN in src/lib/company.ts renders a blank on the six print templates. Give the registered number and every external print (gatepass/hishob/dispatch/beam card) fills it.
- Bale/lump entity (decision ③) — no lump item class and no bale table
exist; the SO
deliveryForm: lumppath is a dead end today. Call: build the lump→bale tables now, or defer to the checking stage.
Deferred (recorded, not blocking)
beam.statushosts two lifecycles (tippan draft/intimated/issued + floor/ getting/onLoom/…) — owner/Phase-4 mapping decision.- Sizing-receipt grid (beam kg + cuts/cut-mark/S.GP.No screen), weft-issue loom/shift/type, winding empties/ring-wt receipt, contract per-beam lines, fabric-inward — the coverage audit's F1–F12 — land with their Phase-4 spines (ledger).
- Journey-residue cleanup in the live DB (§83 cleaner — counts exceed the documented clean state by today's QA runs; e2e fixtures excluded).
Unlocks next
Phase 3 — the shared platform layer — on verified tables, statuses and services; Phase 2's engine (already verified) feeding it.
Signature: ____________________ (owner, after the 5-minute check) Date: ____________________