ExpiryMate — CRT Engine + Developer Interface

⏱

ExpiryMate

v2.2-final — CRT v2.0 FINAL (Beta)

SNM Holdings LLC — Project WS — ExpiryMate

Local profiles on this device. Not an online account — nothing here is sent anywhere.

Display Name

No password. No email required. This creates a local profile on this device only.

🔒 Active Governance Laws

L1 No inferred logic outside CRT

L2 Countdown begins on Trigger Event

L5 No manual expiry extension

L9 No Assumption Law — block if undefined

L11 Human override always wins

⚙️

SETTINGS

Application settings & customization.

This section is currently under development. Settings and personalization features will be introduced in a future ExpiryMate release.

🗂️

WHITE BOARD

The open brainstorming layer for ExpiryMate — ideas, comparisons, and exploration.

Nothing here is authoritative. Ideas ≠ decisions. This layer currently exists as a conversational working mode with the Chief Backend Engineer, not yet as a dedicated in-app screen.

For hands-on experimentation, see White Board Beta — the Developer Interface.

🔍

Product State

🔍

Sticker Preview

Product State

Align the sticker's black section with the top box and the white section with the bottom box. Sticker image crops are sent to Gemini through the ExpiryMate OCR Worker for reading; they are not processed only on this device. If a scan doesn't read well, enter it manually instead.

QUICK BOT CHECK

Complete the check before scanning.

📷 Open Camera

— OR —

🖼️ Choose Image File

🛠

DEVELOPER INTERFACE

WHITE BOARD BETA — experimental layer.
Isolated from the production User Interface.
Nothing here becomes authoritative without explicit promotion by Samuel (Chief Architect).

Developer Areas

📋 Database / CRT Manager→

Inspect all active CRT records, propose corrections

📊 CRT Data Quality / Work Queue→

COMPLETE / PARTIAL / REVIEW / UNUSABLE breakdown, readiness %

🛠 CRT Workbench→

Rapid completion view: current vs imported version per record

🔄 CRT Import / Export→

Export active CRT, edit externally, re-import, compare, approve

🗂 Change Review Queue→

Approve or reject proposed field-level corrections

📜 Audit Log→

Full history: field edits, imports, rollbacks

🕓 CRT Version History→

All versions preserved · rollback available

🧩 Feature Manager→

Beta capability status

💾 Local Data Layer→

Phase 2 / Milestone 1 · IndexedDB profiles, settings, metadata

🧪 Controlled Beta Test→

Automated import/compare/approve/rollback self-test

🚦 Promotion Controls→

Locked — requires explicit PROMOTE command

🔍

External Source Lineage (pre-Beta)

CRT v1.0

Initial 27 Base Rules across 8 categories. Superseded.

Main Editable CRT v2.0

Working copy. Several rows FLAGGED - DATA INCOMPLETE (Milk Fresh, Chicken cooked-states, Malva, Mud Cake, etc).

updated CRT.xlsx — v2.0

Prior authoritative baseline used in the last Beta session. Supersedes Main Editable CRT v2.0 wherever they conflict, per Samuel's standing instruction.

21_08_26 WORKING STRUCTURAL UPDATE.xlsx — v2.1-struct

Prior session baseline (179 rows / 82 products). Superseded by v2.2-final and preserved in the version chain for rollback.

EXPIRYMATE_CRT_v2_0_FINAL.xlsx — v2.2-final

Current active baseline. 180 rows / 82 products, confirmed by SNM. Adds the HOURS_TIMED method (24-hour non-hot-hold limits), 28 base rule definitions, 1.5-hour hot-hold values, Chicken Spatchcock frozen/fresh/hot-hold/defrost states and Kerrymaid Cream.

⚠ Known Data Integrity Issues

In-Session Version Chain (this Beta build)

🔍

Active Version

1. Export Current CRT

Downloads the active version. Edit in Excel/Sheets, keeping Override_ID stable for any row you modify — it's the key used to match records on re-import.

⬇ Export .xlsx

⬇ Export .csv

2. Import CRT

Re-import your edited file (.xlsx or .csv). It does not have to be complete (Section 10/31) — every record is validated and quality-classified independently, then compared against the active version. Nothing is applied until you explicitly approve.

⬆ Import CRT File (.xlsx or .csv)

Format Notes

Required columns: Override_ID, Base_Rule_ID, Product_Name, Product_Category, Product_State, Packaging_State, Storage_Condition, Shelf_Life_Method, Shelf_Life_Value, Shelf_Life_Unit, Trigger_Event, Max_Shelf_Life_Code, Handling_Constraints, Data_Status.

Shelf_Life_Method must be CALENDAR, HOT_HOLD_TIME or HOURS_TIMED. CALENDAR rows use DAYS; HOT_HOLD_TIME (hot holding 65-75C) and HOURS_TIMED (non-hot-hold timed limit) rows use HOURS, unless Shelf_Life_Value is SUPPLIER.

Runs Sections 18/26/27: generates a synthetic import covering 5 scenarios (A: complete new record, B: incomplete new record, C: valid modification, D: quality-degrading modification, E: removed record), verifies the Safe Replacement Rule's per-record decisions, walks Reject → Approve → Rollback, then runs the shelf-life-field regression check.

▶ Step 1 — Generate & Compare

Phase 2 / Milestone 1 — IndexedDB-backed local profile storage. Isolated from the CRT source of truth: this store never reads or writes CRT_BASE, versionStore, workingCRT, proposedQueue, auditLog or developmentData. White Board only — not promoted into the official dataset.

Checking status…

↻ Refresh Status

▶ Run Milestone 1 Tests (M1-T01 … M1-T09)

▶ Run Milestone 2 Profile Acceptance Tests

M1-T10 (existing product lookup, state selection, expiry calculation, Developer Interface, Rollback and OCR entry flow) is a manual regression pass — run the app normally and confirm nothing changed.

🔒 LOCKED

Completing Beta work does not authorize production adoption.

This control is intentionally non-functional. Promotion of any applied change to the real, official CRT / source-of-truth requires an explicit PROMOTE command issued by Samuel (Chief Architect) outside this interface, followed by manual review and application to the authoritative dataset.

Until then, the original working demo and controlled dataset remain authoritative. Law 11 — Human Override — applies.

Applied changes awaiting Samuel's review