Dinar POS · reference

How the work runs

Since 9 September the current milestone is built by several assistants working in parallel, each on one task, with one of them managing. This page says what each task goes through before it counts as done, so a progress report can be read against it.

Milestone 1
a sale and a ticket on one desktop
3 of 9 tasks done, 3 in progress

Who does what

Role	Does	Never
Manager	Writes the task briefs, starts the workers, runs the whole test suite on the combined result, runs the reviews, merges, keeps the log, updates this site.	Writes feature code while workers run.
Worker	One task in its own copy of the code: writes the failing test first, then the code, runs every check, pushes its branch, reports with numbers.	Merges, touches another worker's copy, opens a pull request.
Reviewer	Reads a finished branch with one question in mind (money exact to the centime, who can reach what, whether the tests would notice a broken rule) and lists what it found, with proof.	Edits anything.
Samir	Opens and merges the checkpoint pull requests, tests the printer, answers the questions the log raises.

What every task passes, in order

The worker's own checks: formatting, the strictest compiler warnings as errors, the generated types in sync with the Rust structs, every unit and API test, both builds, and the browser test suite when a screen changed.
The same checks again on the combined code, after the branch is brought up to date with everything merged since it started.
A review. Money and stock tasks get the full review, where each finding is proven by running it, not by reading; the others get one reviewer. Findings go back to the same worker, and the fix is reviewed again.
The merge, the task marked done, one entry in the log with the names of the log files.
After two merges in a row, the whole suite once more on the combined result: two branches can each be green and red together.
At the checkpoints (the till, the backup), a pull request to the main branch that Samir opens; the automated build on GitHub runs there, a sweep for out-of-date pages follows, and a progress report is published here.

Which assistant for which job

The stronger, slower model takes anything where a wrong centime or a lost number costs more than the time: totals, tax, the ticket numbering, stock, backups, the reviews of those. The faster model takes the bounded work: translations and right-to-left layout, screenshots, documentation sweeps, this site. The smallest model counts, lists and checks ports.

Where it is now

Wave	Tasks	State
1	The sale itself (document, numbering without gaps, stock going down, the fiscal rule that picks ticket or facture); the three languages with Arabic right to left on every screen; daily backup with restore from settings.	in progress since 15:25 on 9 September
2	The till screen; the 80 mm ticket in three languages as reference files.	after the sale lands
3	Out-of-date pages swept, progress report, checkpoint to the main branch.	closes the milestone, except the printer test, which needs Samir at the laptop

When it stops

A check that cannot be made green is never merged; the manager reads the log and decides. Two workers changing the same file in opposite ways is settled by the manager and written in the log. A finding that would change a fiscal rule stops the wave: the question is written for the accountant and the work continues on the stated assumption. Low disk or memory on the build machine holds new workers until a finished copy is removed.