Tyvonne Boykin
Founding full-stack engineer
← Back to selected work
Phygital SystemNikeEnterprise complexity

Constellation / Matchbox

A digital-twin and prototype-tracking system spanning RFID, QR, NFC, and workflow integration. It replaced spreadsheet-based visibility with a real operating surface for valuable physical assets and global collaboration.

OutcomeSpreadsheet workflows replaced
Value$50M+ IP protected
GeographyNorth America, EMEA, China
ExtensionParis 2024 activation
What it is

A system connecting physical objects to digital visibility.

Constellation / Matchbox gave teams a shared system for identifying, tracking, and interacting with prototypes and related assets as they moved through real-world workflows.

Business problem

High-value prototypes were moving through fragmented, low-visibility processes.

The existing operating model depended too heavily on spreadsheets and disconnected handoffs, creating loss risk, weak visibility, and poor system confidence across global teams.

What I owned

Backend and workflow architecture across a phygital system.

System framing

Connected digital-twin concepts to operational prototype handling in a way that non-technical stakeholders could actually use.

Integration logic

Worked across RFID, QR, and NFC touchpoints and the backend interfaces required to unify them.

Security and visibility

Helped design a platform where chain-of-custody and access visibility were meaningful business capabilities, not side effects.

Experience extension

Extended the same systems thinking into the Paris 2024 scavenger-hunt activation inside a consumer-facing environment.

Architecture

Inputs from the physical world, system logic in the digital one.

  • Physical identifiers such as RFID tags, QR codes, and NFC interactions.
  • Backend services to resolve identity, location, and workflow state.
  • Operational surfaces to expose visibility, movement, and status to internal teams.
  • A digital-twin layer that treated prototype state as a first-class systems problem.
Key technical decisions

Treat real-world complexity as a systems design problem.

  • Unify multiple sensing and interaction mechanisms rather than letting them become separate sub-projects.
  • Design around workflow reliability and visibility instead of novelty alone.
  • Keep the system legible enough for enterprise adoption across regions and teams.

Constraints

The system had to work across geographies, teams, and real-world handling environments while protecting valuable IP.

Impact

Improved supply-chain visibility, reduced prototype loss, and helped protect more than $50M in IP across North America, EMEA, and China.

Next

The next evolution would be a richer event timeline and clearer audit-oriented reporting layer for every asset journey.