Dinar POS · project status · 9 September 2026

Where the build stands

The first milestone, the money core and the first real screen, is built, reviewed and green, with pull request #14 open against main. Merging it opens the next one: a cash sale with a printed ticket on a real till.

PR #14 night/2026-09-08 → main
85 commits · 8 tracks · every track reviewed
github.com/Dinar-dz/dz-pos/pull/14

125

cargo tests, fmt and clippy clean

108

vitest tests across four packages

2 / 2

browser e2e against the real API and SQLite

tracks, each reviewed by two or three lenses before merge

Where the roadmap stands

Seven milestones to a first shop, sequence without dates. One is done, one is next, five are stubs that receive tasks when their turn comes.

M0 · done

Money core, first real screen

M1 · next

A sale and a ticket on one desktop

Facture, customers, credit

Stock in, expenses, reports

Team, roles, audit log

First release, v1.0

The phone in the shop

M0, item by item

Money(i64) centimes, Bps rates, pct half away from zerochecked arithmetic, clippy denies bare operators, proptests
TVA grouped per rate, global discount spreadproportional, floored, leftover to the largest HT; fixture shared with the mockup JS
Droit de timbre, 2025 tranchescash only, nothing at or under 300 DA, minimum 5 DA
Amount in words fr / en / ar with golden filesFrench and English round-trip; Arabic hand-written, no native review yet
First migrationSTRICT tables, CHECK on every money and rate column, per-shop counters, dated régime fiscal, seeded owner
crates/api: products, categories, healthnamed CORS origins, one JSON error envelope, core error codes as-is
packages/shared types generated from the DTOsgate fails on a stale, new or orphaned type
Products screen reading the APIadd form with category and rate, three languages, Playwright e2e and screenshot
Housekeeping: mockup stamp, CI clippy targets, dz-review sections, token rule
Trial of the Anthropic webapp-testing and frontend-design skills on the first screennot started; moves to M1
Fixture tva_rates_tablenamed in the spec, file not written; the rate list lives in the form and the migration CHECK
Fiscal rules confirmed by a comptableeight questions written, none answered yet

Reference

The parts that rarely change have their own pages: how it is built, the repository layout, the fiscal rules and the decisions taken or still open.

Not landed, on purpose or not

No agent-run review of the whole branch as one piece. A hand sweep checked fixture names against files, leftover markers and debug prints, and the prose.
The Tauri window was never driven on a display; the single-instance change is checked and clippy-clean only.
e2e/ sits outside the desktop tsc gate; no CI job runs the e2e.
No users, no auth: the origin list and the loopback socket are the whole boundary until M4.

What comes next

Merge PR #14; M0 closes and the six ladder steps are already ticked.
M1, first task to plan together: products CRUD complete on the real screen (list, drawer, barcode, category, unit, rate, low-stock).
Then the till and the cash sale, the document model with only ticket issued, the 80 mm ticket on a real printer.
Send the eight comptable questions; get a native speaker on the Arabic words.