Issue dossier

The organizer-published app calls the target a conference badge and adds a user-facing write workflow immediately before the event, but reviewed sources do not state who received a badge, whether every ticket holder was eligible, whether it was optional, whether it functioned for entry, how it was handed out, or how many units existed.

A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.

Back to issues index

allocation and credential boundary · organizer-published app source · event-linked artifact confirmed; allocation unverified

The catalogue records a factual event-linked electronic badge and companion workflow without upgrading it to an all-attendee entitlement, admission credential, or distribution ledger.

Badge
Flutter & Friends 2025 E-Paper Conference Badge
Category
allocation and credential boundary
Severity
note
Confidence
organizer-published app source
Status
event-linked artifact confirmed; allocation unverified
Timeframe
August-September 2025
Source note
Flutter & Friends organizer-published conference-app commit, badge UI source, schedule data, and friends_badge repository.

Evidence

Related Resources

conference-badge update protocol

NFC data format

Package documentation identifying the badge as an NFC Forum Type 4 tag using NfcA and documenting the passive image-transfer path. Generic active/Bluetooth material is kept separate from the 2025 event-unit assertion.

Badge: Flutter & Friends 2025 E-Paper Conference Badge

Source trail

Evidence Sources