Plate № 47 · Operations · ops & verification
A pattern from the gf.cx specimen book
Encode once, read many
Give each physical thing a bulk-readable identity at intake, and one sweep reconciles a whole box, shelf, or room against its manifest — no unpacking, no per-item scan.
"Tag each item once with a bulk-readable identity, and inventory becomes a single sweep: a whole box, shelf, or room reconciles against its manifest in one read. Encode at intake; read many forever after; and fail loud when a sweep comes back empty."
The encode station → ZD621R RFID printer The identity → id.gf.cx registry
The problem
Counting physical things one at a time doesn't scale. A barcode or QR is a per-item, line-of-sight scan; an NFC tap-tag is one item at a centimetre. So a box of archived tapes, a carton of product, or a room of furnishings each demands handling every unit to know what's there. The count is O(items) of human effort — so it's done rarely, quietly drifts from the manifest, and "we think it's all there" replaces actually knowing. The expensive term isn't the data; it's picking each thing up.
The shape
- Pick a bulk-readable carrier. UHF RAIN RFID (EPC Gen2) does anti-collision — hundreds of tags/sec — and reads through cardboard. That's the one radio that turns "a box" into "one scan." QR and NFC are per-item by construction; UHF is per-set. The carrier choice is the pattern.
- Encode identity, not data. Write the tag's EPC = the opaque
id.gf.cx/<ref>; the chip's immutable factory TID is the backup key. The tag carries a pointer, the manifest carries the truth. MirrorEPC ↔ ref ↔ TIDin KV so any read resolves to a record — a rewritable pointer over a cheap tag beats baking data you can't correct. - Encode once, at intake. The same label pass that prints the human-readable QR + text also writes the EPC — one station, one pass (an RFID printer fronted by print.gf.cx). Tagging is a side-effect of labelling, not a separate chore that gets skipped.
- Reconcile, don't just read. A sweep yields a set of EPCs; diff it against that zone's manifest → present / missing / misplaced-foreign / unresolved. A pile of reads isn't an inventory until it's diffed against what was expected.
- Fail loud on an empty sweep.
present == 0where the manifest expects items means a reader/antenna failure or the wrong aisle — never "everything's missing." A zero-read that stamps a clean count is the stale-green lie in physical form.
Why it works
The cost function is human-handling × item-count. A bulk-readable identity collapses the count term to a single sweep regardless of set size — you stop paying per item, so the count that was too expensive to run often becomes cheap enough to run every time something moves. Storing a pointer (not data) keeps the manifest authoritative and the tag cheap and rewritable, with the TID backstopping a rewritten EPC. And reconciliation turns a raw read into a decision — present, missing, misplaced — instead of a number you still have to interpret.
When it breaks
- Metal detunes UHF. Bare drives, aluminium enclosures, and the reflective layer of an optical disc read poorly or not at all. Use on-metal tags (thicker, standoff antenna) or tag the plastic case — never the disc itself.
- Reading without a manifest. A heap of EPCs is not an inventory. With nothing to diff against, a sweep tells you what's there but never what's missing — which is the question inventory exists to answer.
- Trusting an empty read. A zero-count sweep reported as "all missing" instead of "reader failed" is the same quietly-stopped-job failure the Operations playbook is built to refuse.
- Over-reading adjacent zones. High TX power bleeds into the next shelf, so a "shelf count" silently swallows its neighbour. Scope the read zone / dial power down during a stocktake.
Where it applies
- Use — archive media (vault / library): a box of LTO tapes → one read logs the whole box on its way to the shelf.
- Use — product inventory (Audrey): a sealed carton bulk-reads on intake, no unboxing.
- Use — a room of things (Dogwood House): walk through once and capture beds, leads, and contents in a single pass.
- Skip — a handful of items, or anywhere a per-item line-of-sight scan is already trivial; the tag + reader rig only earns out at set-scale.
Reusable elements
- The identity model — EPC = opaque
id.gf.cx/<ref>, TID as backup key,EPC↔ref↔TIDmirrored in KV (a UHF sibling ofnfc_kv_mirror.py). A tag is a pointer to a manifest record, not a data store — portable to any bulk-readable carrier. - Reconcile-against-manifest — the present / missing / misplaced / unresolved diff. The read is data; the manifest is truth; the diff is the product.
- Fail-loud-on-empty — a zero-read is a probe failure, never an inventory of absence. The ops-baseline "a no-op must never stamp green" applied to the physical world (see Plate № 26).
- Encode-at-print — the label pass that prints the human QR also writes the machine EPC, so tagging can't be forgotten because it isn't a separate step.
Reference
- Encode station
- vault.gf.cx/hardware/zebra/zd621r/ — the desktop UHF RFID printer, and its industrial sibling the ZT610R, that print-and-encode in one pass.
- Identity
- id.gf.cx — the opaque-ref registry the EPC points at; the same identity face the NFC layer uses.
- Front-end
- print.gf.cx — the single label / print cockpit that emits the tag.
- Origin
- The 2026-09-14 "desktop / RFID" session — the realisation that one UHF sweep captures a whole box, generalised across vault media, Audrey cartons, and Dogwood House contents.