Glossary

Every term a newcomer trips on. Confidence markers and citation shorthand as defined in README.md (L: = Lovable clone at origin/main ffab85ca; QC: = QC script line; BL: = .local/business-logic/).

Core commercial objects

Scanning and verification

Units and pricing-like objects

People, companies, access

Terminology collisions — handled explicitly

C1. Claim Unit (CU) vs credit unit. Code says Claim Unit (claimUnits.ts, CuStat.tsx, fmtCu()); the Owner dashboard copy says “credit units”; the QC script uses both (“1 CU (Claim Unit / credit unit)” QC:6, “Claim Unit (CU) / credit units” QC:276) and therefore canonises the pair, not a winner. Lovable ran a 4-pass copy sweep spelling CU out as “Credit Units” (Aug 17-19) that is itself incomplete at HEAD. Newest source: the QC script — uses both. Status: OPEN (tracked since 2026-08-18; port-plan unit 9 blocked on it). VERIFIED

C2. Purchase Order vs Nomination. The table, routes and hooks are purchase_orders / /purchase-orders / usePurchaseOrders; the UI copy direction is Nominations — QC X-02 mandates “Nominations (not Purchase Order)” (QC:276) while the same script still writes “Create a nomination (PO)” and routes through /purchase-orders. Newest source: QC script — settles display wording only. Whether the domain/table renames is OPEN. VERIFIED

C3. Verification Records vs Scan History vs Claims. Three surfaces share vocabulary: /verifications is called Scan History (manufacturer view of sessions), /claims is called Verification Records (retailer view of claims), and “verification-record” is also the primary evidence-pack type. QC X-02 mandates “Verification Records (not Claims)” for the /claims page and “Scan History” for /verifications. Newest source: QC script — settled as display wording; the route names still say otherwise. STATED, consistent with L route naming |

C4. programme vs program. The codebase mixes both: tables are fibre_programmes/programme_*, admin route renamed to /admin/programs with /admin/programmes redirecting (L:src/App.tsx:215-216), functions say programme. Newest source: the Aug-19 window’s rename commits — “program” is winning in URLs, “programme” persists in data names. No stated ruling on prose spelling. Status: OPEN as a style rule, cosmetic. VERIFIED

C5. Claim vs Activate. Older UI used “Activate” for confirming a claim (walkthrough era buttons “Activate · N MT”); QC X-02 mandates “‘Claim’ (never ‘Activate’)” (QC:276). Separately “Activated” remains the capacity-funnel stage name for produced volume — same word, different concept, both still live. Newest source: QC script. Status: display rule settled; funnel stage name unchanged. STATED

C6. Audit vs verification vs session vs scan. SAT posts audits (one audit = one verification event with multiple scans); the dashboard groups scans into sessions (verification sessions) and calls them verifications; canvas has no session resource at all and monet fakes session_id from the audit’s own id (“a load-bearing coincidence, not a correct mapping” — memory reference_verification_id_obfuscation). Status: real vocabulary alignment is blocked on BE shipping a sessions resource. VERIFIED

C7. Orders vs Purchase Orders. The real Fibretrace /orders API is the Collections domain, unrelated to purchase orders/nominations; purchase_order appears in the real API only as a free-text reference field on audits/invoices. Do not map one onto the other. VERIFIED (port-plan.md:121; integration-audit/README.md:110,216)

C8. Tier labels. Malcolm’s definitions (Tier 3 = spinner, Tier 4 = raw fibre producer/gin) vs the signup wizard’s labels (“Tier 3 — Fibre producer”, “Tier 4 — Raw material”). Newest code source is the signup wizard, but the walkthrough definitions drive the whole persona narrative. Status: OPEN, needs a naming ruling. VERIFIED (L:src/lib/signup.ts:5-19 vs BL:demo:32-35)