Cyborg Badge

Physical GFAVIP member key — launched at Cross Border Summit, useful long after the lanyard comes off

← Cyborg wave hub  ·  Principles  ·  Shopping list  ·  GFAVIP Perks  ·  CBS GTM  ·  Eventbadge (translator)

Status: product brief / launch plan — not a finished SKU. Hardware DNA lives in the cyborg wave; community OS is GFAVIP (SSO, wallet, webchat, perks).

Inspiration (event hardware people keep): Three.js conf badge progress (@rbriaux) — ESP32-class board + real enclosure energy.

One sentence

A small ESP32-class wearable (e‑paper or stick form) that is your physical GFAVIP identity at Cross Border Summit and a year-round button/display into member apps — not a disposable name tag.

Why this page exists

The site already has pieces; this page is the commercial + community product that ties them together.

Existing What it covers Gap this fills
/eventbadge Wearable translator / subtitles vision Not GFAVIP-linked; not CBS launch plan
/badger Badger Smart Badge reverse-engineer Third-party product teardown, not our SKU
/cbs2026avatar Stage co-host avatar Stage presence, not attendee wearable
/gfavipperks CBS launch, year-round software benefits Software only — no hardware key
/cyborg2 + carts Maker paths, BOM, agents Personal R&D, not community productization

Same product thesis as Perks: CBS is the launch moment; GFAVIP is the OS that keeps the device alive.

What it is (and is not)

Is

  • Member-linked wearable (device id ↔ GFAVIP account)
  • Event badge UX at Cross Border Summit (name, role, QR)
  • Evergreen desk/lanyard device after the summit
  • Physical CLI into wallet, perks, light agent dump
  • First commercial face of the cyborg hardware wave

Is not

  • Single-use printed plastic with a dead battery on day 2
  • A full omni.me replacement on v1
  • On-device 70B LLM (see swarm only for later edge intent)
  • Anonymous “AI badge” with no named community
  • Stage avatar hardware (that’s CBS avatar)

Two modes: summit vs evergreen

Mode When Jobs
Summit mode Cross Border Summit (Nov target) Display name / company / role; QR to profile or meet; optional check-in; path into GFAVIP Perks; sponsor/session cues
Evergreen mode Home, desk, future events GFAVIP status; perks nudge; hold-to-talk dump (cyborg e‑paper pattern); “open to chat”; reflash/OTA so firmware keeps evolving

If firmware and account binding die at closing ceremony, we built swag, not product.

Architecture (GFAVIP + cyborg stack)

Layer Job Systems
Physical E‑paper/OLED, button, battery, lanyard shell, optional mic Cart A class board — shopping list
Device identity Stable device key; pair once to member Provision at pickup or claim flow
Tiny API Profile payload, claim links, optional voice-in GFAVIP backend + same pattern as /status, /voice-in
Member OS SSO, wallet, apps, chat gfavip.com, Headless SSO, Webchat
Value layer Benefits that outlive the event GFAVIP Perks
Agent layer (v1.5+) Dumps / briefs into personal or community agents E‑paper dump, HEOS, named agents

Branding: sell “GFAVIP badge / member device”, not “ESP32 kit.” Same lesson as character path: people buy the identity, not the BOM.

Feature tiers

Tier Must ship for CBS? Features
MVP Yes Pair device ↔ GFAVIP user; show name + company + tier on e‑paper; QR to live profile or perks hub; charge path; non-embarrassing shell
Summit+ Nice Session check-in, “open to meet” state, sponsor QR day, LED/attention blink
Evergreen v1 Post-event OTA or day-1 if ready Home Wi‑Fi config; status from GFAVIP; button opens wallet/perks deep link
Evergreen v2 Later Hold-to-talk dump (cyborg path); light agent reply; optional translator mode from eventbadge

Hardware recommendation (reuse cyborg carts)

Choice Path Why
Primary MVP Waveshare-class ESP32-S3 e‑paper AIoT (Cart A + lanyard / clip shell Name readable in hall light; low power; mic available for later dump
Alt demo M5 StickS3 Cart C Faster bring-up; less classic “flat badge”
Mic / dump later Onboard mic or INMP441 After identity + display are boring-reliable
Avoid v1 Full local swarm LLM on every badge Cost, support, and flash risk at scale — see swarm for edge experiments

Unit economics sketch (order of magnitude — validate quotes): electronics ~$30–60 + shell + packaging; giveaway vs sell depends on sponsor subsidy and margin. Character thesis (~$25 → $99) is the pricing frame if you sell, not BOM + 5%.

Software contract (minimum APIs)

Endpoint / flow Job
Provision Staff or self-serve: bind device_id + secret → GFAVIP user_id
GET /device/status JSON for e‑paper: name, company, tier, QR payload URL, event day flags
Deep links Perks claim, profile, wallet — already GFAVIP surfaces
POST /voice-in (later) Same dump pattern as e‑paper console; scoped device key only
Revoke Lost badge → unbind device without burning the member account

Blast radius (from cyborg principles): device key can show profile + claim links + dumps — not auto-send email, not spend, not admin SSO.

CBS launch path (giveaway or sell)

Option When it fits Risk
VIP / sponsor giveaway Limited run (e.g. 50–200), high touch provision Support load; must still work after event
Sell / upgrade Optional paid “member hardware” at registration or booth Expectations on polish and warranty
Hybrid Core badge software features for all (app QR); hardware for tier that pays or sponsors Messaging clarity

Align messaging with CBS GTM and Perks: hardware is another reason to be in GFAVIP, not a one-off merch drop.

Timeline toward November (working)

  1. Now: Lock MVP feature list; order 5–10 Cart A boards + shell experiments
  2. +2–4 weeks: Provision API stub + e‑paper name/QR prototype (one device, one test user)
  3. +1–2 months: GFAVIP pair flow; 20-device pilot with internal team
  4. Pre-summit: Decision — giveaway tier, sell, or hybrid; packaging; staff playbook
  5. Summit: Pickup / claim; daily status content; Perks cross-promo
  6. Week after: OTA or email “evergreen firmware” so the badge is clearly not dead

Dates are directional — treat as a checklist, not a signed PMO plan.

Design principles (product)

  1. Evergreen first — if it only works at CBS, cut the feature
  2. GFAVIP is the brand — cyborg is the R&D label on this site
  3. One job per firmware mode — summit display vs home status vs dump
  4. Write to real systems — profile, perks, dumps land in GFAVIP / vault
  5. Human gates — no silent spend or outbound from the badge
  6. Supportable volume — better 100 solid devices than 1,000 bricks

First ship definition

MVP “real” when:

  • Device shows the correct GFAVIP member name after provision
  • QR opens a live GFAVIP URL (profile or perks), not a static PDF
  • Lost-device revoke works
  • Written plan for post-CBS firmware or content update (not optional)

Prior art on this site

Eventbadge

Wearable translator / subtitle vision — feature stretch later.

Read →

Badger teardown

Commercial e-ink BLE badge architecture reference.

Read →

GFAVIP Perks

Same launch pattern: CBS moment, year-round member value.

Read →

CBS avatar

Stage embodiment — different form factor, same event.

Read →

Cyborg wave links

Wave hub

All hardware paths + shared architecture.

Hub →

Shopping list

Cart A e‑paper kit is the badge MVP base.

Parts →

E‑paper console

Status + dump patterns to reuse in firmware.

Path →

Character product

Sell identity, not ESP32 — pricing mindset.

Path →

M5 StickS3

Faster modular demo form factor.

Path →

Local swarm

Later: offline intent nodes, not badge v1.

Path →

Living notes

This page productizes the cyborg hardware wave for GFAVIP community + Cross Border Summit distribution. Next edits: unit cost spreadsheet, provision API owner, shell CAD/print path, and giveaway vs sell decision.

Comments

Approved comments appear below. Log in once with GFAVIP — it applies across the whole site. GFAVIP login

View comments archive