i3 · Count Session

SC-2026-0729-MCC-001 BLIND CYCLE MCC STOCKDISPLAY_GOOD 47 of 88 · 53% Variances 4 Not found 2 09:15 · elapsed 4h 36m

Sled live · scan then qty then Enter

1Planned28-07 17:02 2In progresssince 09:15 3Adjudicating2 lines queued 4Submittedcounter signs 5Under review1 of 2 signed 6Approvedledger posts here 7Completedread-only TVoidnever posts

Blind mode is enforced by the server, not by CSS. While count_sessions.is_blind is true, GET /api/counts/sessions/<id>/next omits expected_qty, balance_at_freeze and unit_cost_fils from the response body entirely. There is nothing in the page for a counter to reveal with a developer console. Expected quantities appear only after the line is observed.

Scope

frozen · immutable

Location: MCC Mirdif City Centre
Stock types: STOCK 61 keys · DISPLAY_GOOD 27 keys
Narrow by: ABC class A and B, plus 6 drift-linked keys
Sample rule: 8% of the location's keys, weighted by value and by days since last verification
Zones: SHOPFLOOR · DISPLAY · WINDOW · BACKROOM
Frozen at: 29-07-2026 09:14:22 GST
Ledger watermark: entry #4,182,996
Thresholds: 5u or 2.0% of expected or AED 500, copied from policy and now immutable
Photo minimum: 2 on any breaching line, enforced at submit
Second-pass rate: 8% randomised plus every breach · 6 lines drawn so far
Excluded: 14 non-taggable keys are out of the sled's reach and are counted by hand in this same session, marked method=manual

Freezing the scope stops the SKU set changing. It does not stop trading, and it does not block a single Shopify webhook.

Progress by zone

Walk order, not the count grain. A SKU found in two zones is one line with two observations.

2 zones open

ZoneProgressDoneVarNFSaturation

SHOPFLOOR34/3420pass 2 · 0.28%

DISPLAY13/2722pass 1 running

WINDOW0/800queued

BACKROOM0/1900queued

Counters

FAFatima A.lead counter · pass 141 lines · 62 lines/hr

ZRZainab R.second pass only · never counts a line she will approve6 lines · 48 lines/hr

SHSara H.supervisor · adjudicator · approver 20 lines counted

R-10.6: an approver may not appear as a counter on the line they approve. Sara has counted nothing in this session precisely so that she can sign every line in it.

Cross-body Messenger 42 · Black

MST-CRM-42-BLK DISPLAY_GOOD DISPLAY zone · fixture D3 Line 48 of 88 pass 1

System quantity withheld served 13:47:08 · watermark #4,183,204 · 2 ledger events at this key since freeze

Counted quantityInteger · units · zero is a valid answer

2 photos required if this breaches

Four outcomes, not one nullable number. Not found means the counter looked and saw nothing but is not certain the key belongs here, and it never becomes a zero without adjudication. Counted 0 means the counter looked and there were none, and it is the only observation that can legitimately drive a balance to zero. INV1's CHECK (quantity > 0) made that second sentence unstorable.

Passes and adjudication

Two disagreeing passes are never averaged. A third person decides, and the decision is stored with its own actor and reason.

2 adjudicating

SKU	Stock type	Zone	Pass 1	Qty 1	Pass 2	Qty 2	Agree	Adjudicated	By	Reason
MSR31-07	STOCK	SHOPFLOOR	Fatima A.	18	Zainab R.	18	exact	18	auto	no decision needed
MSR31-12	STOCK	SHOPFLOOR	Fatima A.	7	Zainab R.	7	exact	7	auto	no decision needed
MST-CRM-42-BLK	DISPLAY_GOOD	DISPLAY	Fatima A.	6	queued	-	breach · pass 2 forced	-	pending	variance -6 crossed the 5u arm
LTC04-03	STOCK	SHOPFLOOR	Fatima A.	11	Zainab R.	13	disagree by 2	13	Sara H.	pass 2 re-walked the back fixture and found 2 more
MIN-CNDL-007	STOCK	SHOPFLOOR	Fatima A.	22	Zainab R.	22	exact	22	auto	no decision needed
LTC01-01	DISPLAY_GOOD	DISPLAY	Fatima A.	3	Zainab R.	3	exact	3	auto	no decision needed
JB_PEARL_03	DISPLAY_GOOD	DISPLAY	Fatima A.	0	Zainab R.	2	disagree by 2	-	queued	a counted zero against a counted two is the case that must never be averaged to one

Second passes are drawn from every threshold breach plus a randomised 8% of clean lines, so a counter cannot know which of their lines will be checked. That randomisation is what makes recount agreement a usable measure of a counter rather than a measure of the system.

Line variance with the count window

The window column is R-10.1 made visible. Every intervening ledger event between the line's freeze watermark and its observation is listed on the line, so a counter who was "wrong by 2" because two units sold while they walked the aisle is shown as correct with two sales attached.

1 real variance

#	SKU	Title	Stock type	Zone	Counted	Frozen	Window	Expected	Variance	Value AED	Reason	Photos	Approval
9	MSR31-07	Signature Tote 31 · Sand	STOCK	SHOPFLOOR	18	20	-2	18	0	0	count_window_movement	not required	auto
14	MIN-CNDL-007	Oud Noir candle · 180g	STOCK	SHOPFLOOR	22	23	-1	22	0	0	count_window_movement	not required	auto
21	LTC01-01	Leather card holder · Tan	DISPLAY_GOOD	DISPLAY	3	2	+1	3	0	0	count_window_movement	not required	auto
27	LTC04-03	Leather wallet bifold · Stone	STOCK	SHOPFLOOR	13	13	0	13	0	0	confirmed after adjudication	not required	auto
48	MST-CRM-42-BLK	Cross-body Messenger 42 · Black	DISPLAY_GOOD	DISPLAY	6	14	-2	12	-6	-1,830	theft	1 of 2	dual required
31	MSK05-BRN	Strap · Brown 20mm	STOCK	SHOPFLOOR	9	7	0	7	+2	+280	missed_receipt	not required	drift opened
33	JB_PEARL_03	Pearl bracelet set · 3pc	DISPLAY_GOOD	DISPLAY	-	2	0	2	pending	pending	adjudicating	not required	blocked
36	GIFTBOX_LUX_02	Luxe gift box · composite	STOCK	BACKROOM	n/a	0	0	0	0	0	composite · never holds stock	n/a	out of scope
39	LTC07-02	Passport holder · Navy	DISPLAY_GOOD	DISPLAY	not found	1	0	1	held	held	not_found	not required	needs adjudication
41	MIN-DIF-004	Reed diffuser · Amber	STOCK	SHOPFLOOR	0	0	0	0	0	0	counted zero · confirmed empty	not required	auto
44	MSR31-12	Signature Tote 31 · Noir	STOCK	SHOPFLOOR	7	7	0	7	0	0	confirmed	not required	auto
45	MST-CRM-38-TAN	Cross-body Messenger 38 · Tan	STOCK	SHOPFLOOR	4	4	0	4	0	0	confirmed	not required	auto
46	BX-MSR31	Tote 31 gift box · composite	STOCK	BACKROOM	n/a	0	0	0	0	0	composite · never holds stock	n/a	out of scope
47	STRAP-MSK05	Strap · Black 20mm	STOCK	SHOPFLOOR	15	15	0	15	0	0	confirmed	not required	auto

Three of the four apparent variances are the count window and net to zero once the intervening sales are attached. Under v2's arithmetic they would have been shrinkage of 4 units and would have been approved as such. The one real variance is MST-CRM-42-BLK, minus 6 units at AED 1,830, and it needs two signatures and two photos.

Ledger preview

The exact rows this session will post on approval, generated by the same function the commit uses. If this preview and the committed rows ever differ, acceptance criterion AC-10.17 has failed.

not yet posted

Lines observed

43 counted · 2 not found · 2 skipped

Will write a ledger row

the only two with a non-zero variance

Verification only, no ledger row

clean counts and window-reconciled lines

#	Table	source_type	SKU	Location	Stock type	quantity_delta	balance_after	idempotency_key	occurred_at
1	ledger_entries	stock_count_adjust	MST-CRM-42-BLK	MCC	DISPLAY_GOOD	-6	6	count:SC-2026-0729-MCC-001:48	29-07 13:47:22
2	ledger_entries	stock_count_adjust	MSK05-BRN	MCC	STOCK	+2	9	count:SC-2026-0729-MCC-001:31	29-07 11:02:41
3	balance_verifications	blind_count	MST-CRM-42-BLK	MCC	DISPLAY_GOOD	n/a	6	bv:count:...:48	29-07 13:47:22
4	balance_verifications	blind_count	MSR31-07	MCC	STOCK	n/a	18	bv:count:...:9	29-07 09:41:08
5	balance_verifications	blind_count	MSR31-12	MCC	STOCK	n/a	7	bv:count:...:44	29-07 13:12:55
6	balance_verifications	blind_count	MIN-CNDL-007	MCC	STOCK	n/a	22	bv:count:...:14	29-07 10:04:19
7	balance_verifications	blind_count	MIN-DIF-004	MCC	STOCK	n/a	0	bv:count:...:41	29-07 12:58:03
8	balance_verifications	blind_count	LTC01-01	MCC	DISPLAY_GOOD	n/a	3	bv:count:...:21	29-07 10:47:31
9	balance_verifications	blind_count	LTC04-03	MCC	STOCK	n/a	13	bv:count:...:27	29-07 11:38:44
10	balance_verifications	blind_count	STRAP-MSK05	MCC	STOCK	n/a	15	bv:count:...:47	29-07 13:41:02
11	balance_verifications	blind_count	MST-CRM-38-TAN	MCC	STOCK	n/a	4	bv:count:...:45	29-07 13:22:17
12	count_variances	drift.open	MSK05-BRN	MCC	STOCK	n/a	n/a	drift:count:...:31	on approval
13	events	stock_count.approved	session-level, consumed by module 02		flips provenance	n/a	n/a	count:SC-2026-0729-MCC-001	on approval
14	events	alert.raise	theft reason at a retail location		module 01 owns delivery	n/a	n/a	alert:count:...:48	on approval

Rows 3 to 11 are the case ruling L14 creates. Those lines were counted, they were correct, and they moved nothing, so quantity_delta = 0 is forbidden and no ledger row exists. They post a balance_verifications row instead, and that row is the only thing that turns their provenance to counted. Module 02's v_balance_provenance must read v_last_verification for this to work, which is conflict C1 in the module 10 spec.

Approval chain

One real variance breached the threshold, so this session needs two signatures. Neither signer may have counted the line they sign.

1 of 2 signatures

Counter FAFatima A. · MCC lead Fatima A. Signed 29-07-2026 · 14:02:11 GST
TOTP verified · ip 10.0.14.221
covered hash a7f4b2c1 · 47 lines · 43 counted

Supervisor · approver 1 SHSara H. · Ops Manager Awaiting signature Notified 14:02:40 · expires in 23h 41m
counted 0 lines in this session, so eligible for every line

Finance · approver 2 MFMahmoud F. · Finance Blocked until approver 1 signs Required because the reason code is theft, which forces dual approval at any size
value AED 1,830 also crosses the AED 500 arm

Integrity hash · SHA-256 a7f4b2c18e6d9f33c5a1b072e8d4f19b3e2a9c7d4f8b6e1a0d9c5b2e7f3a8d1c

Inputs: session code, the frozen scope key list, every observation with its pass number and counter, every adjudication, every evidence sha256, and every signature collected so far. It chains to the previous session at MCC through prev_session_hash = 3f81c04a, so deleting a session breaks the location's chain rather than leaving a gap nobody notices. Adding an observation after a signature invalidates that signature and the page says who must re-sign.

Line queue

88 keys · walk order

53%

MSR31-07Signature Tote 31 · Sand18

MSR31-12Signature Tote 31 · Noir7

MST-CRM-38-TANMessenger 38 · Tan4

LTC01-01Card holder · Tan3

LTC04-03Wallet bifold · Stone13

LTC07-02Passport holder · Navynot found

MIN-CNDL-007Oud Noir candle · 180g22

MIN-DIF-004Reed diffuser · Amber0

MSK05-BRNStrap · Brown 20mm9 · +2

STRAP-MSK05Strap · Black 20mm15

JB_PEARL_03Pearl bracelet set · 3pcadjudicate

MST-CRM-42-BLKMessenger 42 · Blacknow

MST-CRM-42-TANMessenger 42 · Tan

MSR31-04Signature Tote 31 · Olive

LTC02-05Coin pouch · Sand

LTC09-01Laptop sleeve 14 inch

MIN-VAS-005Ceramic vase · Tall

MIN-SPRY-008Room spray · Citrus

JB_PEARL_07Pearl drop earrings

LP_MONO_11Monogram patch · personalised

Row badges show the counted number only after observation. Before that there is nothing to see, because the server never sent it.

RFID handheld feed

MCC-SLED-02 · RFD40

live

TimeEPCSKURSSIResult

13:47:19E280 6894 0000 4021 8F3CMST-CRM-42-BLK-52match

13:47:18E280 6894 0000 4021 8F2AMST-CRM-42-BLK-49match

13:47:18E280 6894 0000 4021 8F2AMST-CRM-42-BLK-51dup

13:47:16E280 6894 0000 4019 C107MST-CRM-42-BLK-58match

13:47:14E280 6894 0000 4019 C0F1MST-CRM-42-BLK-61match

13:47:11E280 6894 0000 3987 44B2MST-CRM-42-BLK-55match

13:47:09E280 6894 0000 3987 4491MST-CRM-42-BLK-64match

13:46:52E280 6894 0000 4102 71DDLTC07-02-71wrong zone

13:46:31E280 6894 0000 4471 0A19MSR31-04-48out of scope

13:45:58E280 6894 0000 3821 9C40LTC01-01-53match

13:45:56E280 6894 0000 3821 9C3ELTC01-01-57match

13:45:54E280 6894 0000 3821 9C22LTC01-01-60match

MCC-SLED-02RFD40 · 94% batterylast read 1s ago

MCC-IPAD-01host · iOS 18.4online

MCC-SLED-01RFD40 · offline 41mits pass is invalidated

A sled that silently stops transmitting mid-pass produces a zone that looks counted and empty, which is the most dangerous failure an RFID count can have. MCC-SLED-01 went offline at 13:06 and every line it touched after 13:06 has been reset to pending.

Session activity

Line 48 breached the threshold13:47

MST-CRM-42-BLK counted 6 against expected 12. Pass 2 forced, 2 photos required, dual approval flagged.

MCC-SLED-01 went offline13:06

4 lines touched after the last heartbeat were reset to pending. No count was accepted from an unheard device.

Adjudication queued11:44

JB_PEARL_03: Fatima counted 0, Zainab counted 2. No average taken. Sara H. assigned.

Window movement absorbed10:47

3 lines carried a non-zero window. Sales #MIN10482, #MIN10484 and a store transfer receipt landed during the walk. All three lines reconciled to variance 0.

Zone SHOPFLOOR saturated10:31

Pass 2 added 0.28% new distinct EPCs, below the 0.5% rule. Zone marked swept.

Scope frozen09:14

88 keys, 2 stock types, watermark #4,182,996. Thresholds copied from the MCC policy and now immutable for this session.

Lines counted through the session

With the zone boundaries and the sled outage marked. The flat stretch at 13:06 is not a slow counter, it is a dead device.

4h 36m elapsed

09:1510:0010:4511:3012:1513:0013:4514:30

Variance by zone

Split into the part that is real and the part that is the count window. Only the first column costs money.

AED 1,830 real

real variance count-window movement zone not counted yet 4 apparent variances · 1 real

What this session posts, and what it deliberately does not

43 lines were counted. Two of them moved stock. The other 41 moved nothing and must still be recorded, because "we looked and it was right" is the single most valuable thing a counting programme produces and it is the fact every incumbent system throws away.

-- the constraint that makes it impossible to get this wrong (R-10.2)
ALTER TABLE count_lines ADD CONSTRAINT ck_clean_posts_nothing
  CHECK (ledger_entry_id IS NULL OR variance IS DISTINCT FROM 0);

-- and the completeness identity the session must satisfy (AC-10.6)
SELECT count(*) FROM count_lines cl
WHERE cl.session_id = 'SC-2026-0729-MCC-001'
  AND cl.observation = 'counted'
  AND cl.verification_id IS NULL;
-- must be 0. A counted line without a verification row is a count that will be forgotten.

i2's count_lines had no stock type, no pass number, no evidence link and no route to the ledger, so no i2 count has ever moved a balance. ops2's IWMS count does move the carton and then swallows its own ledger write inside a bare except Exception: pass, which is strictly worse: it increases divergence at the exact moment it claims to correct it.

Four outcomes, not one nullable number

counted (a number, possibly zero) · not_found (looked, saw nothing, not certain the key belongs here) · skipped (in scope, deliberately not visited) · out_of_scope (encountered, not part of this session).

Only counted 0 may drive a balance to zero. A not_found is held until someone adjudicates it, because "I could not find it" and "there are none" are different facts and conflating them is how a stock system quietly loses a SKU.

One container, one line, one session

Module 04's defect D2: opening a carton credits the picking area at the carton's full quantity and never debits the carton. Both then read as stock at HQ_319.

The count-side guard is a unique constraint: count_evidence_sources (session_id, source_kind, source_ref). Reading the same carton twice fails at insert and blocks submit with the two candidate lines named. No discipline required.

Shortcuts ⌘⏎ submit and next Tab qty then note then submit N not found S skip F flag R recount P print sheet Esc pause ⌘⇧⏎ sign scan a barcode at any time to jump focus All shortcuts ↗

Count session SC-2026-0729-MCC-001

Scope

Progress by zone

Counters

Cross-body Messenger 42 · Black

Passes and adjudication

Line variance with the count window

Ledger preview

Approval chain

Lines counted through the session

Variance by zone

What this session posts, and what it deliberately does not

Four outcomes, not one nullable number

One container, one line, one session

This session has no keys in scope

No lines match the queue filter

The last observation did not reach the server

Read-only. You are not the assigned counter.

Evidence storage is in maintenance

This session will not post yet