Issue dossier
The repository describes three badge types and publishes three named Gerber archives plus two schematic PDFs. It does not publish a reconciled production BOM, revision history, component-substitution record, test plan, final assembly record, per-variant quantity split, or mapping from technical files to each delivered badge.
A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.
Back to issues index
multi-variant hardware and final-unit mapping gap · public repository tree · three design archives visible; production mapping unrecovered
The entry keeps the collection-level hardware description bounded and does not imply that every unit had identical hardware, display, sensors, power, firmware, or physical finish.
- Badge
- MNSEC 2025 Electronic Badge Collection
- Category
- multi-variant hardware and final-unit mapping gap
- Severity
- note
- Confidence
- public repository tree
- Status
- three design archives visible; production mapping unrecovered
- Timeframe
- 2025 source archive review
- Source note
- MNSEC2025BADGE repository, Schematics directory, and Badge PCB Gerber Files directory.
manufacturer project record
Beelog's official project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order, including hardware, firmware, and deployment-ready work. The page does not identify individual recipients, per-unit configuration, ticket entitlement, or image-reuse permission.
Badge: MNSEC 2025 Electronic Badge Collection
official event announcement
MNCERT/CC's official announcement identifies the September 25, 2025 MNSEC Cybersecurity Conference, Cyber Resilience theme, and Shangri-La Ulaanbaatar Hotel ballroom. It establishes the completed event context, not badge allocation, hardware, delivery, or image rights.
Badge: MNSEC 2025 Electronic Badge Collection
official organizer recap
MNCERT/CC's official organization feed records a post-event MNSEC 2025 recap. It corroborates completed organizer event context but does not identify a badge programme, recipient list, or technical artifact details.
Badge: MNSEC 2025 Electronic Badge Collection
public Gerber archive
The public directory contains separate Gerber archives for Albat, HaruulZangi, and Humun. It corroborates three named design variants without proving that all archive files correspond exactly to every delivered unit.
Badge: MNSEC 2025 Electronic Badge Collection
public badge source archive
The public repository identifies the MNSEC 2025 electronic-badge commission, says three badge types and 418 completed units, names MNCERT/CC and Beelog Tech, and links hardware, firmware, and supporting material. It is a project archive, not a recipient ledger or blanket licence for all media.
Badge: MNSEC 2025 Electronic Badge Collection
public firmware and example-code archive
The public directory contains a firmware binary, a named sketch, and example source folders. It does not establish a reconciled final release, source-to-unit mapping, support lifecycle, or safe operating/reconfiguration instructions.
Badge: MNSEC 2025 Electronic Badge Collection
public schematic archive
The public directory contains two schematic PDFs. It establishes a technical design archive without proving final BOM, final board revision, uniform unit population, production testing, electrical safety, or per-variant delivery state.
Badge: MNSEC 2025 Electronic Badge Collection
source archive license
The repository root publishes a BSD 2-Clause license credited to DavgaBeelog. This is recorded as a source-archive licence statement, not assumed to resolve rights in physical artifacts, brands, photos, renders, or a selected local image.
Badge: MNSEC 2025 Electronic Badge Collection
Beelog Technologies · retrieved 2026-05-15
Primary manufacturer project record stating that Beelog designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. It does not map those units to named event recipients or selected source-media rights.
Badge: MNSEC 2025 Electronic Badge Collection
DavgaBeelog / MNSEC2025BADGE · retrieved 2026-05-15
Primary repository license text. It is scoped as the archive's BSD 2-Clause source/binary statement and is not treated as automatic permission for photographs, renders, badges, branding, or a locally published image.
Badge: MNSEC 2025 Electronic Badge Collection
MNCERT/CC · retrieved 2026-05-15
Official organizer feed recording a post-event MNSEC 2025 recap. It corroborates the conference's completion without attributing badge design, manufacture, delivery, or media permission.
Badge: MNSEC 2025 Electronic Badge Collection
MNCERT/CC · retrieved 2026-05-15
Primary official event announcement for the September 25, 2025 Ulaanbaatar conference, Cyber Resilience theme, and venue. It does not describe the badge collection or prove an attendee allocation.
Badge: MNSEC 2025 Electronic Badge Collection
helicopteresdc / Beelog Tech · retrieved 2026-05-15
Primary public badge archive identifying the MNSEC 2025 commission, MNCERT/CC customer context, Beelog Tech role, three badge types, and 418 completed units. Its design archive is not treated as proof of every final delivered configuration.
Badge: MNSEC 2025 Electronic Badge Collection
helicopteresdc / Beelog Tech · retrieved 2026-05-15
Primary public source for the three named Gerber archives. It supports the collection's multi-variant design trail, not an exact final manufacturing or recipient record.
Badge: MNSEC 2025 Electronic Badge Collection
helicopteresdc / Beelog Tech · retrieved 2026-05-15
Primary public source for the preserved firmware binary, named sketch, and examples. It does not establish a complete released software inventory, operational configuration, or support policy.
Badge: MNSEC 2025 Electronic Badge Collection
helicopteresdc / Beelog Tech · retrieved 2026-05-15
Primary public source for the two schematic PDFs. It establishes design-document availability without a production, safety, or all-unit configuration guarantee.
Badge: MNSEC 2025 Electronic Badge Collection