SMP-2026-0726-011 SAMPLE_QC · +76h

One sample end to end · origin, purpose, custody chain, the classification decision and who made it, and the final disposition

Leather belt sample run ★

First shipment of LLW-NEW-099 · a new SKU, no production history, no cost history except the invoice

Supplier: ORO Leather · UAE · 21d lead
SKU: LLW-NEW-099 new
Quantity: 5 units
Counted at: 23-07-2026 10:30
Deadline: 26-07-2026 10:30
Location: HQ_319
Requesting team: marketing
Purpose: shoot
Cost basis: invoice

Value held

AED 2,100

5 × AED 420 · basis: supplier invoice INV-ORO-2026-0408

Not sellable · not written off · owned · counted in on_hand and owned_qty

PO / PI raised

Shipped

Customs cleared

GRN counted

SAMPLE_QC · 148h

Classified

POOL / STOCK / RTS / write-off

72h SLA

Clock started at counted_at, 23-07 10:30 · nothing on this rail changes a balance

breached +76hgate-blocking

safe 48h

warn 24h

breached +76h

0h · 23-07 10:3048h warn · 25-07 10:3072h deadline · 26-07 10:30now · 148h

When	Event	Actor	Detail	Ledger effect
25-07 10:30	warn_24h	system:sample_sla	24h remaining, notified marketing	none, by design
26-07 10:30	breached	system:sample_sla	first_breached_at set, never cleared	none, by design
26-07 10:31	escalated	system:sample_sla	Slack to marketing lead · alert ALT-71204	none, by design
27-07 09:00	escalated	system:sample_sla	Second escalation · Ahmad CC	none, by design
29-07 06:00	gate_blocked	system:sample_sla	GATE 7 will not go green while this row is open	none, by design

Five automatic events, zero ledger rows. v2 would have written +5 STOCK at 168h and closed this record. i3 will not, because a unit nobody has inspected must not become sellable by the passage of time.

Origin

PI · not a production run

Artefact	Reference	Detail	State
Purchase intent	PI-2026-LC-044	signed 10-07 by a.yousuf	signed
Purchase order	PO-2026-118	line 4 · 5 units flagged sample at order time	received
Production run	-	not applicable, this came off a PO not a run	-
Supplier invoice	INV-ORO-2026-0408	AED 2,100.00 · 5 × AED 420	matched
Customs	DHL 4548827193	cleared 23-07 08:00	cleared
GRN receipt	GRN-2026-0723-003	counted by r.kumar at 10:30 · blind count 1 of 1	posted
Sample batch flag	is_sample_batch = true	declared by the supplier at dispatch	honoured
Ledger posting	LE-4468812	+5 SAMPLE_QC @ HQ_319 · not RNI, not STOCK	posted
Cost layer	CL-0090118	AED 420 per unit at landed cost, frozen	costed

Module 06 owns everything above the ledger posting. Rule R-06.20: a sample receipt posts to SAMPLE_QC, and its 72h clock starts at counted_at.

Custody chain

4 hops · 3 people

When	Held by	Where	Qty	Handover
23-07 10:30	r.kumar · WH	HQ_319 · receiving	5	counted in from GRN
23-07 14:10	r.kumar · WH	HQ_319 · QC bench	5	staged for inspection
24-07 09:40	f.marketing	HQ_319 · marketing cupboard	5	signed out for shoot review
26-07 16:00	j.photo · studio	HQ_319 · studio	3	3 taken for test shots, 2 left in cupboard
27-07 11:20	f.marketing	HQ_319 · marketing cupboard	5	all 5 back together, 2 show colour variance
29-07 -	f.marketing	HQ_319 · marketing cupboard	5	awaiting the classification decision

Every hop is a program_holding_events row with a named actor. v2's timeline recorded the SLA but not who physically had the units, which is exactly the question asked when a sample goes missing.

QC evaluation

6 checks · the suggested outcome recomputes live

4 pass · 1 fail · 1 n/a

✓Matches PI specificationsDimensions, material and colour against PI-2026-LC-044PASS ✓Stitching and finish qualityNo loose threads, clean edges, uniform stitch densityPASS ✓Hardware and functional componentsBuckle operates without friction across all 5 unitsPASS ✓Labelling and packagingSKU tag, country of origin and barcode present and readablePASS ✕Batch consistency across all units2 of 5 units show colour variance beyond Pantone toleranceFAIL Transit damageOptional. Flag only if visible on the item, not the outer cartonN/A

Suggested: STOCK (partial) · 3 units pass every check, 2 fail batch consistency. The suggestion is advice; decided_by is still a person.

Decision tree

The highlighted branch matches the current QC result

Is the item sellable as is?

Yes, all units → STOCK

Yes, some units only → STOCK (partial) ← current path

No. Is the defect repairable or cosmetic?

Usable for marketing or shoot only → SAMPLE_POOL

Supplier at fault, credit expected → RTS

Beyond use → WRITE-OFF (photo required)

A sample whose cost_basis is unknown cannot reach the STOCK branch at all. This one has an invoice, so it can.

Pick a classification

Splittable · the parts must sum to 5, the unclassified remainder

required · 76h overdue

Accept all to SAMPLE_POOL shoot use

Tracked as a marketing asset in the PHOTOGRAPHY sub-pool. Not sellable. Returns to the pool after each shoot.

+5 SAMPLE_POOL0 STOCKno cost line

Reclassify all to STOCK sellable

Production equivalent. Writes +5 STOCK at HQ_319 and the SKU becomes sellable. Contradicted by the batch-consistency failure on 2 units.

+5 STOCK0 SAMPLE_POOL

Split · 3 STOCK, 2 SAMPLE_POOL suggested

The 3 units that passed every check become sellable. The 2 with colour variance go to the photography pool, where a Pantone half-step does not matter.

+3 STOCK+2 SAMPLE_POOLsums to 5 ✓

RTS the 2 off-colour units supplier at fault

Opens an RTS case in draft against ORO Leather with a return AWB. Credit expected: AED 840. Nothing ships from draft.

+3 STOCKRTS 2 unitscredit AED 840

Write off photo required

Units unsalvageable. Routes through program_writeoffs, needs a finance approver who is not the proposer, and needs photo evidence: ck_pw_photo refuses it otherwise.

+5 WRITTEN_OFFcost_ledger line4 photos attached ✓

Classification notes (required)

3 of 5 units match the PI reference exactly. Units 4 and 5 read two Pantone half-steps warm under daylight, visible side by side but not in isolation. Not a defect worth an RTS, and fine for the lookbook. Splitting.

Classifier

f.marketing (you) · role = manager · feature samples_classify

decided_by rejects system:*. A cron cannot classify, even at 148 hours.

Photos

4 uploaded 23-07 10:35 by r.kumar

Full item · front

Stitching detail

Colour variance · units 4-5

Buckle close-up

What "final disposition" means here

A split classification produces two sample_classifications rows against one receipt, each with its own outcome, quantity, destination and ledger entry. The receipt closes only when qty_classified = qty_received.

Partial classification is legal and common: classify the 3 good units today, argue with the supplier about the other 2 for a week. Over-classification is a constraint violation.

first_breached_at stays set after classification. A late decision does not erase the fact that the SLA was missed, which is what keeps the supplier scorecard honest.

ORO Leather · sample track record

18 samples year to date · this is the evidence that decides whether to keep taking samples from a supplier at all

Supplier detail ↗

Sample	SKU	Qty	Counted	Hours to decide	Breached	Outcome	Decided by	Later sell-through
SMP-2026-0726-011	LLW-NEW-099	5	23-07	148+	yes	pending	-	-
SMP-2026-0722-006	LLW-NEW-095	3	22-07	28	no	POOL	f.marketing	-
SMP-2026-0708-021	LLW-NEW-091	4	08-07	36	no	POOL	f.marketing	-
SMP-2026-0622-018	LLW-NEW-087	4	22-06	24	no	STOCK	a.yousuf	92%
SMP-2026-0601-012	LLW-BLT-012	4	01-06	26	no	STOCK	a.yousuf	92%
SMP-2026-0518-009	LLW-WAL-008	3	18-05	30	no	POOL	f.marketing	-
SMP-2026-0403-004	LLW-BAG-041	2	03-04	22	no	STOCK	a.yousuf	78%
SMP-2026-0305-002	LLW-BLT-003	6	05-03	40	no	STOCK	a.yousuf	64%
SMP-2026-0208-001	LLW-STR-001	2	08-02	68	no	RTS	f.marketing	credit OK
SMP-2025-1204-044	LLW-BAG-038	3	04-12	31	no	STOCK	a.yousuf	81%
SMP-2025-1118-039	LLW-WAL-004	2	18-11	27	no	STOCK	a.yousuf	88%
SMP-2025-1002-031	LLW-BLT-001	5	02-10	33	no	STOCK	a.yousuf	94%

12 of 18 shown · 12 STOCK (67%), 5 POOL (28%), 1 RTS (5%) · average 28h to classify against a 72h SLA · this sample is the first ORO Leather breach in 18, which is why it escalated to Ahmad rather than to a supplier claim.

Incoming samples from this supplier

3 in the next 30 days

SKU	Description	Qty	PI	ETA	State
LLW-NEW-101	Belt · black	5	PI-2026-LC-048	03-08	shipped
LLW-NEW-103	Wallet · brown	3	PI-2026-LC-049	06-08	dispatched
LLW-NEW-105	Keychain set	8	PI-2026-LC-050	12-08	prep

16 more sample units land in the next two weeks. If this one is still unclassified when they arrive, the breach queue triples and GATE 7 moves further away, which is the argument for deciding today rather than waiting for a perfect answer.

Why this page refuses to auto-classify

v2's version of this page carried a button reading "Classify now (required)" above a line that read "Auto-fallback to STOCK in 12h if not manually classified. INV2 will write +5 STOCK and close this record automatically." Both statements were on screen at once. The second makes the first optional.

It also disagreed with i2's own schema, where samples.state allows auto_pool and not auto-stock. Two specifications, two destinations, one timer, and whichever one shipped would have been a surprise to somebody.

At 148 hours this sample has 3 units that pass every check and 2 that do not. An automatic promotion would have made all 5 sellable at hour 168, including the 2 that fail batch consistency, and the only trace would have been a system-authored row.

Ruling L19 says a carrier status string may never credit stock. The same principle, applied to a clock, is ck_phe_no_robot_writeoff: a system actor may chase, warn, escalate and gate-block, and may never promote, consume, gift, write off or declare lost.

Connected to Samples queue GRN + QC GRN events PI detail POs + PI Production Supplier detail Return to supplier Write-off approvals SKU detail Live inventory Audit log Influencer