Two independent reviewers examined the complete Kuberan HTML suite and both source documents. These are review annotations—not silently added requirements. Each note identifies the reviewer, priority, exact target and expected coverage so decisions can be accepted, changed or deferred deliberately.
Add a visible maturity label for every application—concept, partly interactive, or workflow complete—and list the important workflows still awaiting design.
Should cover: honest prototype maturity, known omissions, and clear boundaries for pharmacy, fuel, full payroll/GL, e-commerce fulfilment and regulated modules.
Add release phases, dependencies, acceptance gates and named sources of truth. Link every application to measurable functional and non-functional acceptance criteria.
Should cover: MVP versus later scope, document precedence, workflow owners, dependency map and go/no-go evidence.
The working cashier application needs receipt lookup, returns/exchanges, no-receipt returns, hold/retrieve, reprint, cashier sign-in/lock, opening float, pickup, no-sale, blind till count, shift close, lane alerts, price check and item-not-found escalation. Show approvals and device-failure responses.
Should cover: the full register lifecycle from cashier sign-in through blind till close, including printer, scale, terminal and server exceptions.
Define the cashier workflow as testable states covering authentication, till acceptance, sale building, promotions, loyalty, restricted-item prompts, suspend/retrieve, void/cancel, returns, terminal recovery, receipts and visible sync status.
Should cover: acceptance scenarios for every state and transition; the current page represents only a small part of documented checkout scope.
Add opening, shift-change and closing checklists with owner, due time, evidence, escalation and sign-off for tills/safe, temperatures, sanitation, recalls, staffing, deliveries, labels, alarms, batches, deposits and backup. Safety and money tasks must roll over until closed.
Should cover: daily store control, responsibility, proof and escalation.
Add restricted loss-prevention cases that link transactions, notes, witnesses and optional camera references; record outcomes and prohibit AI accusation or discipline.
Should cover: fair, evidence-based investigation and access control.
Specify task states, ownership, SLA/escalation, role permissions, evidence retention, data-freshness display and the rule that AI suggestions cannot complete controlled work.
Should cover: deterministic task lifecycle and auditable manager actions.
Capture appointment, driver/seal, temperatures, accepted/rejected quantities, substitutions, catch weight, case/unit conversion, lot/expiry, photos, source documents and sign-off. Rejected or short goods must create a claim without increasing stock.
Should cover: cold chain, traceability, discrepancies and vendor credits.
Add recall/quarantine with UPC/lot/date search, stop-sale at every lane, hold locations, sold/on-hand tracing, disposition, notifications, evidence and manager close. Add configurable fresh-production recipes, yield, labels, allergens, markdown, donation and waste.
Should cover: recall safety plus deli, bakery, meat, seafood and prepared-food transformation.
Define valuation and costing, quantity precision, UOM conversion, negative stock, count-freeze versus live movement, concurrent sale/receipt reconciliation, lot traceability, vendor credits and production implications.
Should cover: trustworthy on-hand, COGS, shrink, recall and month-end valuation invariants.
Add acknowledgement, confirmed quantity/cost, substitutions, backorders, cutoff, missed delivery, claims, invoice disputes, debit memos, vendor credits and ageing with retained correspondence and photos.
Should cover: PO transmission through delivery, dispute and recovered value.
Show calendars, cutoff, packs/minimums, cash/budget, promotions, seasons, allocations, shortages and override reasons; distinguish recommended, committed, in transit and unavailable.
Should cover: real constraints that determine whether a forecast can become an order.
Define PO versioning and state transitions, authorization thresholds, landed-cost changes, receiving/invoice links, reopen/cancel rules, supplier transport adapters and idempotent send/acknowledge behaviour.
Should cover: one auditable lifecycle across suggested order, approval, transmission, receipt, invoice and credit.
Add employee availability, leave, open shifts, swaps, call-outs, missed-punch corrections, break acknowledgement and final-hour visibility, with coverage impact and notification history.
Should cover: the changes and exceptions that occur after a schedule is published.
Freeze the period, total regular/overtime/holiday/adjustments, map earning codes, export with control totals, record acceptance/rejection, correct failures and require final sign-off without unnecessary banking data.
Should cover: auditable completion at the payroll provider.
Make jurisdiction rules configurable and effective-dated; define clock trust/offline punches, approvals, period locks/reopen, payroll adapter contract, sensitive-data boundaries and retention.
Should cover: consistent time calculation, privacy and failed-export recovery.
Include every register/terminal batch, over-short, deposits in transit, chargebacks, stored-value liability, vendor credits, accruals, payroll control, negative stock, valuation, prior-period corrections and accountant-export acceptance. Give each exception an owner and due date.
Should cover: accountable close across sales, cash, inventory, payables, payroll and tax.
Show dispute and vendor-credit ageing, duplicate-payment prevention and the boundary between bill approval, accounting export, payment authorization and payment status.
Should cover: AP responsibility and segregation of duties.
Specify opening/closing continuity, duplicate and overlapping statements, split/combined matches, fees, chargebacks, settlement timing, reversals, stale items, permissions, period locks/reopen, subledger mapping and immutable approval evidence.
Should cover: auditable reconciliation rather than confidence-only matching.
Add cases for complaints, quality, injury/property, returns, points, gift cards and privacy, with owner, deadline, evidence, resolution, approval and follow-up. Implement identity verification, access/correction, consent, anonymization, required retention, marketing stop and breach response.
Should cover: service recovery and operational privacy, with limited cashier exposure.
Treat gift cards, points and store credit as controlled value: activation, reload, redemption, replacement, transfer, offline limits, manual adjustments, fraud holds and liability reports.
Should cover: complete stored-value lifecycle and high-value approval.
Define customer deduplication/merge, consent versions and purposes, loyalty/stored-value ledger invariants, offline balance reservation, conflict recovery, audit retention and deletion/anonymization boundaries.
Should cover: privacy-safe identity plus exactly-once value movement.
Add Food Safety, Recalls & Compliance for temperatures, sanitation, pests, allergens, certificates, notices, quarantine, corrective action and inspection evidence. Add Equipment, Maintenance & Incidents for refrigeration, scales, printers, doors, alarms, HVAC and vehicles.
Should cover: ongoing food-safety records, preventive maintenance and breakdown response.
Prototype import/entry, margin/tax impact, overlap detection, effective time, shelf/scale label batches, installation confirmation, shelf-versus-register scan check and rollback.
Should cover: execution from price decision to correctly installed label.
Define deterministic precedence/stacking, coupon funding and limits, price zones, Ontario scanning-price policy configuration, signed device snapshots, rollback, tax provenance, representative-item tests and dual approval for high-risk changes.
Should cover: safe, versioned, fully distributed configuration.
Add amount at risk, due date, recommendation, source, responsible manager and delay consequence, plus a 13-week cash view, commitments, borrowing headroom, payroll/HST dates, vendor-credit ageing, maintenance, food safety and unresolved loss cases.
Should cover: forward-looking cash and risk decisions, not only current KPIs.
Add trends and drill-down for department margin, waste, labour productivity, out-of-stocks, vendor service, promotions and maintenance; show period, freshness, definition and source.
Should cover: comparable, source-backed management information.
Define every KPI formula, source ledger, time zone/business-day rule, freshness SLA, correction behaviour, permissions and multi-store aggregation boundary.
Should cover: explainable numbers that reconcile to operational detail.
Explain supported OS distribution, minimums, licensing, updates and drivers. Add UPS shutdown testing, replacement-box recovery, key custody, support SLA, signed update/rollback, spare plan, restore drill, network check and a printable failure card.
Should cover: realistic installation, ownership and recovery for non-technical stores.
Do not declare readiness until power-loss recovery, storage/SMART health, local discovery/certificates, isolation/firewall, time sync, update rollback, recovery code, restore, disconnected-server checkout and escalation tests pass.
Should cover: verifiable appliance acceptance rather than a successful pairing alone.
Define initiated, presented, authorized, captured, declined, timed-out, unknown, reversed, refunded, partially approved and reconciled states; require stable attempt IDs, status inquiry before retry, callback idempotency and explicit sale/payment recovery.
Should cover: prevention of duplicate charges, unpaid completed sales and wrong tender status.
Specify causal ordering, dependency rules, partial-batch transaction semantics, same-ID/different-payload rejection, poison-event authority, queue retention, log compaction, snapshot cutover and reconciliation after device/server restoration.
Should cover: implementable sync without silent loss, reordering or inconsistent ledgers.
Add owner controls for Disabled, Local, OpenAI, Anthropic or Hybrid execution; encrypted store-supplied API keys; permitted data movement; provider/model selection; cost and rate limits; model/key testing and rotation; retention; confidence thresholds and one-click disable. Core workflows must work with AI off.
Should cover: provider choice, credential custody, AI cost, consent, health, disablement and no silent cloud fallback.
Add plain-language food safety, recall and emergency playbooks for refrigeration/power/server failure, fire, flood, robbery, injury, contamination, boil-water notice and evacuation, including authority, stop-sale, offline evidence, contacts and resume sign-off.
Should cover: safe action during an incident, not only technical recovery after it.
Expand safe opening, till/float issue, pickups/drops, change orders, blind counts, over-short, batches, stored value, bag numbers, two-person check, bank/armoured-car handoff and deposit-in-transit, including one-person exceptions.
Should cover: every physical and system handoff from opening cash to bank confirmation.
Add role-based practice, competency sign-off, quick cards, accessibility/language, refresher and first-week support. Extend inventory guidance to labels, fresh production, temperatures, recalls, claims, DSD and donation.
Should cover: adoption by non-technical staff and complete grocery-floor procedure.
Add RPO/RTO, retention/rotation, key escrow, replacement provisioning, restore epoch, client replay, disaster reconciliation and scheduled restore-drill evidence.
Should cover: replacement of a failed/stolen box without loss or duplicate sales.
Define $10–20M-store capacity: registers/devices, SKUs, daily lines/events, peak scans/writes, latency, offline duration, storage/attachments, recovery time, availability and benchmark gates for SQLite’s single-writer design.
Should cover: measurable proof that Java/Spring Boot plus SQLite meets the promise.
Add PCI scope reduction, EMV/P2PE expectations, encryption/key recovery, certificate revocation, signed updates, vulnerability/breach response and Canadian privacy/accessibility/marketing boundaries. Add cutover for opening stock/cost, prices, balances, POs, bills, employees, tills and history with control totals and rollback.
Should cover: production security and adoption by an operating store, not product-only import.
Update the family to Staff/Time, Finance/HST, Customers/Loyalty, Owner, Store Box, cash office, food safety/recalls, maintenance, emergencies, training and AI governance. Add fresh yield/allergens, cold chain, claims/credits, price-label confirmation, cash custody, LP, maintenance and optional regulated modules.
Should cover: present scope and explicit document precedence.
Incorporate outbox/inbox/ordered pull, data ownership, payment recovery, security/backup targets, AI permission boundaries, schema compatibility, observability, migration, testing and rollout gates; identify the legacy prototype correctly.
Should cover: a current architecture summary that cannot misdirect implementation.
Mark this as the legacy detailed checkout prototype and reconcile its returns, shift, alerts, cash movements, lock and help workflows into the current Checkout definition. Add payment recovery for unknown results, reversals, partial approval, retry and batch reconciliation.
Should cover: prototype status and preservation of operational controls.
Treat this file as an exploratory interaction reference, not a source of truth. Map retained scenarios to current requirements and acceptance tests, including accessibility, permissions, hardware failure and safe split-tender recovery.
Should cover: traceability from useful legacy ideas to the build backlog.
Review date: August 7, 2026. Review notes describe gaps and decision points; they do not claim that every item belongs in the first release.