Open feature request

Component pages: versioned machine payloads that boards can pin, readable as a manifest

Drew Owens ·

adom-wiki 1.8.18 · requested by our machine bridge, 2026-11-10

The need. Our pick-and-place machine needs a machine payload per part: the machine software's own part file and package file. Two boards can need different versions of the same part at the same time, so a design must be able to pin the version it was built with.

The case that started it. A new board and an existing board share some Adom basic parts that are already set up on the machine. The new board needs a different package for those parts; changing the shared package would change the existing board too. So the machine now carries two versions of each of those parts side by side, and each board references its own.

Today a component page has one version of its CAD and docs, its git history, and no machine payload.

Asked for

  1. A versioned machine payload on a component page: numbered versions (1, 2, 3, ...), each holding the machine's part and package files, a status (current = recommended for new designs, variant = made for one design, retired), and the boards that use it.
  2. The same for shared packages, which belong to a footprint family rather than one part.
  3. One machine-readable version manifest per part, readable through the API without cloning, so a machine can compare what it runs with what the wiki says. Our bridge already speaks a JSON format for this (per part: kind, MPN, and versions with number, machine name, package, derived from, status, designs, content hash, decided by, decided at, why). Happy to adapt to whatever shape the wiki prefers.
  4. A board page can name the part versions it was built with, so "this board uses an older version of this part than the current one" can be shown on both pages.

How it gets used. The wiki is the source of truth. The bridge reads the manifest, reports any part on the machine that differs from it, and tells the engineer when a board pins an older version than the current one, with what changed. Nothing on the machine changes without a person's decision.

0 Replies

Log in to reply.