Not just specs
Safety warnings, delivery problems, app-store gaps, team-process history, and first-hand reports are tracked as sourced records.
The badge still had useful modes, but the entry records the documented feature limitation instead of implying a fully working clock.
The machine-learning feature is documented as an experimental constrained-device implementation rather than a broad general-purpose on-watch AI platform.
The record treats the badge as a teaching artifact for keystroke injection and preserves operational risks instead of presenting it as a harmless novelty.
The badge page preserves the original safety context instead of presenting USB HID payload experimentation as risk-free.
The catalogue treats Uber Badges as an award lineage attached to the challenge and avoids naming unverified 2026 winners.
The record links the standalone Tanmatsu/Konsool platform to the same Dutch camp badge-history branch as WHY2025 without treating it as the shipped WHY2025 attendee badge.
The compendium should revisit the platform periodically rather than treating this page as a frozen historical badge entry.
The catalogue avoids implying that every 2019 badge had an onboard camera, Wi-Fi-capable core, or face-recognition hardware.
The compendium avoids MCU, firmware, LED, battery, and circuit claims and records the audio, physical, lanyard, and printed clue surfaces instead.
This keeps the catalogue honest about flow3r's app lifecycle and gives app authors the real publication path.
The compendium keeps the app and author record while flagging that source-code provenance is weaker than other Tildagon app entries.
The compendium records representative apps but keeps status and caveat language visible for users who may revive old TiDAL hardware.
The app store was curated and collaborative rather than an anonymous binary upload service.
The visible page stays concise while preserving the key source trail for deeper later archaeology.
The dossier separates hardware, software, event, and challenge claims by source instead of treating one page as a complete archive.
The catalogue ties the badge to the Hardware Hacking Village public archive and avoids claiming exact distribution volume or universal attendee issuance.
The record preserves the verified hardware and software surfaces while leaving deeper artifact archaeology for a later pass.
The record captures the verified hardware/software surfaces without claiming complete CTF reconstruction or complete production logistics.
Future maintenance should prefer a restored official page, badge-team repository, or post-event writeup if one appears, and should not weaken the record to the current default-page response.
The badge workflow is historical; live redemption behavior should not be inferred from the archived page.
The badge workflow is historical; live redemption behavior should not be inferred from the archived page.
The record is classified as an identity/payment and CTF artifact instead of inventing electronics, components, firmware, or distribution details beyond the official wiki.
The entry is modeled as official role and competition badge artwork instead of being upgraded into an unsupported hardware badge.
The entry is classified as a playable event artifact rather than upgraded into unsupported electronic-badge claims.
The dossier preserves the real public badge-sponsor evidence while avoiding unsupported hardware or final-artifact claims.
The catalogue models the object as a presenter wearable/event artifact rather than a general admission badge or attendee-wide distribution claim.
The catalogue keeps the 2018 record as a paid-badge entitlement and avoids unsupported physical or electronic details.
The catalogue records verified hardware and social-game behavior while leaving firmware, challenge, and complete variant archaeology for a later pass.
The catalogue preserves the artwork credit as source context while leaving the visual empty until a specific image can be cleared under the project image rules.
This is useful lore for European badge culture: the organizers optimized for immediate on-site play and beginners, not only for people already comfortable with microcontroller programming.
The badge page preserves the original power-safety context for the AD8317 RF detector instead of presenting the module as a no-risk plug-in.
The record preserves the original assembly warnings and avoids silently normalizing the battery spelling beyond the source text.
The record captures the real operational work behind the polished attendee artifact and preserves a useful production failure mode for future badge teams.
The record keeps hardware claims tied to the assembly PDF rather than inventing design files or firmware surfaces.
The record keeps this as a CTF-solving and archive detail rather than treating it as a badge defect or official intended workflow.
The record treats NodeWatch as the NodeConf EU 2019 attendee badge without claiming exact batch size, every-ticket entitlement, or post-event availability limits.
The record distinguishes hardware capability and project ambition from the exact final attendee experience.
The catalogue records the verified analog badge surfaces and leaves complete audio forensics for a later artifact-level pass.
The compendium records the artifact under DerbyCon while avoiding claims of general conference distribution or regular attendee-badge status.
The record should not imply that every attendee received the final physical art badge immediately at registration; the temporary paper credential is part of the event artifact history.
The catalogue cites the firmware and writeups while avoiding copied board artwork, undocumented image reuse, or claims of complete open hardware release.
The catalogue records practical handling behavior that matters for surviving badges and post-event hacking.
The record presents the badge as a real deployed event artifact with field power lessons rather than a frictionless reference design.
The badge record preserves the production constraint instead of describing the hardware as a polished low-power device.
The catalogue preserves the badge's material lifecycle and avoids treating a plantable local artifact as universally exportable swag.
The record avoids treating documentation images, pin locations, or layout details as universal across all BUSSide boards.
This captures a practical beginner trap: the badge worked, but the serial workflow depended on reconnect timing and terminal setup.
The detail page should preserve first-boot and recovery behavior, not only final hardware specifications.
The final badge may differ from the early public ambition, so hardware claims should be revisited when production docs are published.
The record presents Winglet OS as publicly buildable and hackable while making clear that toolchain, USB, and access workflows are not frictionless for every host.