FibreTrace business logic
Built 2026-10-21. The business logic as it runs on BETA FibreTrace (commit 205b76b4), the Lovable project where every Dashboard and business-logic change is now made. English is canonical; the Vietnamese page follows it.
Business logic
How FibreTrace works, as it runs on BETA FibreTrace: tiers and personas, vocabulary, Claim Units, programme capacity, the purchase-order to Fibre Verification Record flow, sharing and masking, sign-in and roles.
- Business logic VI: The one document to read. English is canonical.
What changed
- 2026-10-21 (v14) — Business logic re-checked against BETA commit
205b76b4, covering four weeks of Malcolm’s changes. Access: data is now separated per company in the database; staff have three roles (Superuser, Admin, Customer Support) with Customer Support limited in the database and every admin change logged; sign-in uses an emailed code with 30-day trusted devices; a Superuser alone changes a Company Code. Claims: a scan counts as claimed only once it sits in a confirmed claim, and only then can its IDs show; a brand opens a received scan’s details only after its own claim is confirmed; rejecting a claim now removes only that proposal and frees its scans; every PO screen follows the database status (“Ready to claim”, “Claimed”); a new Claim Unit ledger books every reservation, claim and reversal. Sharing: non-exclusive is preselected, PO-linked scans cannot be shared, outbound scans are shared automatically with the receiving company, and confirmed records get public links again. New: webhook feeds (off by default), active and inactive product categories with an Excel PO template, producers set inactive instead of deleted, facility registrations that FibreTrace approves against free licences, a stricter sign-up review that grants the first licence, facility details locked after the first scan, SDU escalation contacts (alerts not sent yet), and one notifications inbox. Section 12 now lists what was fixed (both 2026-10-05 blockers among them) apart from what is still open, plus seven new gaps, including webhook feeds exposing hidden IDs, public records that can be listed, and sign-up rejections that are never emailed.