Hardware, platform and safety
Questions about the Reliability, Failsafes & Edge Pathways module of the catalog.
Status labels: Built in the repository (checked files or developer tooling, not an app feature) Designed in a document, no code yet Planned: listed in the catalog, not built Not decided Not in the catalog yet (a gap) No claim made
Planned C0402
Yes: FAIL-0003, Single-writer queue, is a core item under “Storage durability”. Its description reads: Serialize writes to avoid SQLITE_BUSY. This is a plan only.
Planned C0403
No: there is no released app. FAIL-0016 (Disk-full graceful handling), filed under “Storage durability”, is described as: Block new sales safely, never corrupt.
Planned C0404
No: there is no released app. FAIL-0023 (Unknown-outcome payment resolution), filed under “Crash & power loss”, is described as: Reconcile when app died during digital/card payment.
Planned C0405
Yes: FAIL-0047, KDS disconnect alert, is a core item under “Hardware faults”. Its description reads: Waiter notified, fallback to print. This is a plan only.
Planned C0406
Hub unreachable behavior (FAIL-0058) is assigned to both Lite and Pro. Section “Network”: Register continues independently. Tier names are catalog labels, and no prices are published.
Planned C0407
For Customer name/DNI typo post-issue (FAIL-0086) the catalog says: Within 10 business days NC exception. It is core priority within “Money & data edge cases” and sits in both Lite and Pro. It is not a feature yet.
Planned C0408
Self-diagnostic health screen depends on SQLite WAL mode with synchronous=FULL for money tables. By itself it covers: Check DB, disk, clock, printer, backup, SUNAT queue, license. These are catalog links between planned items in “Money & data edge cases”.
Planned C0409
Item price changed while ticket open (FAIL-0119) is assigned to both Lite and Pro. Section “Additional edge pathways”: Lock price at order time with manager-approved update. Tier names are catalog labels, and no prices are published.
Planned C0410
Document number consumed by crash before commit carries core priority in Reliability, Failsafes & Edge Pathways, section “Additional edge pathways”. Description: Gap-recovery by void/baja policy. Priority is only a planning label.
Planned C0411
Power cut for hours (apagón) in market is item FAIL-0138 in the “Additional edge pathways” section of Reliability, Failsafes & Edge Pathways. In the catalog it covers: Phone/battery-only mode, paper fallback book, later reconcile. Nothing is built.
Planned C0412
Dual-write journal (event log file) carries standard priority in Reliability, Failsafes & Edge Pathways, section “Storage durability”. Description: Secondary append-only transaction journal. Priority is only a planning label.
Planned C0413
Cashier gives wrong change discovered at close is item FAIL-0116 in the “Additional edge pathways” section of Reliability, Failsafes & Edge Pathways. In the catalog it covers: Variance attribution workflow. Nothing is built.
Planned C0414
Sale to non-domiciled buyer is item FAIL-0130 in the “Additional edge pathways” section of Reliability, Failsafes & Edge Pathways. In the catalog it covers: Document type 0/7 and exception handling. Nothing is built.
Planned C0415
The catalog marks it as always offline. For Shared phone used by multiple cashiers (FAIL-0141) the catalog text is: Fast PIN switch without losing cart. Under “Additional edge pathways”, and not built.
Planned C0416
Tip received via Yape to personal phone is item FAIL-0152 in the “Additional edge pathways” section of Reliability, Failsafes & Edge Pathways. In the catalog it covers: Record as tip without business revenue. Nothing is built.