The digital half of the mark-and-bind duet. Emboss the leather tag first (blank chip through the press), then encode here.
Order: emboss (blank) → encode → read back → verify → bind. The chip is blank through the press, so a press-death costs nothing encoded, and the verify proves it survived.
Written to chip · embossed on tag
dwntwn.io/00001
record · TOT01-2632-0001 · H-2608-CWB03-014
Ready. Set the serial and hide, then Write.
RULE 1 — the tamper-evident chaining happens in the backend, not here. This console writes the tag URL and records the pairing; it never exposes the binding method (Patent 4). For NTAG 424 / SUN, keys are self-generated and destroyed in a separate secured step — never in this console.
Encode the fixed pads
The workshop's own threshold nodes. Encode each once at install. NTAG213 — routing, no auth.
Pick a pad, hold it to the phone, Write.
Verify any chip
Tap a finished tag or a mounted pad. Confirms what's written and that it resolves.
Hold a chip to the phone and press Read.
The workshop chip architecture
Chip
Where
Count
Type
Product · bag
panel, at the mark (under / 15mm beside — per survival test)
1 / bag
213 → 424
Product · belt
buckle-end tab
1 / belt
213 → 424
— straps / panels
fold into the finished product's passport
0
—
T1 intake
Cell 1 bench (cow + buffalo)
1 fixed
213
T2 cut
Cell 2 bench
1 fixed
213
SERVICE
press · skiver · stitch · strap cutter
~4 fixed
213
DIES
die rack
1 fixed
213
STOCK
twin-bin order rail
1 fixed
213
HAZARD
Cell 4 oil bench
1 fixed
213
CLOSE
street door
1 fixed
213
Fixed pads: ~10, one-time install (213 — routing, no auth). Product chips: one per finished bag and belt, ongoing, from twin-bin C-NFC-001. Mark&bind / finish / pack use the product chip itself — no separate fixed pad there.
Type logic: 213 everywhere for the pilot. Upgrade product chips to NTAG 424 DNA + SUN only when anti-counterfeit / resale authentication matters. Fixed pads stay 213 — internal witnessing needs no anti-clone.
DPP · product chipvenue OM pad
Serial scheme: the tag shows dwntwn.io/<running number> — public, human-readable, from zero. Behind it the backend maps to the structured record <CAT><NN>-<YYWW>-<seq> and the hide. The running number narrates; the chip (and later SUN) authenticates. A not-yet-made serial must resolve to a clean "not yet made," not an error.
Session log
Nothing encoded yet this session.
This is a session log only. In production every write and bind posts to your backend (Supabase) — the source of truth. The console is the bench tool; the record lives in the backend, cached never trusted as truth.