Open feature request

Machine-to-wiki recommendations: let a machine bridge propose a new part version on a component page

Drew Owens ·

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

The need. Some part decisions are made at the pick-and-place machine: an engineer tunes a part's package settings while proving a board. Our rule is that the wiki stays the source of truth, so such a change must come back to the wiki as a recommendation for a new version, never live only on the machine.

The case. A new board needed a different package for parts another board also uses. The new versions were decided at the machine; the wiki has no place to receive them.

Asked for. A structured proposal attached to a component page (or a shared package's page), posted through the API by the machine's bridge on a person's behalf:

  • the part and the version it started from;
  • the proposed new version, with the before and after machine files and a field-level diff;
  • who decided, when, and why, plus evidence links;
  • an owner action: accept into a new numbered version (with a status, current or variant), or decline with a reason that the bridge reads back.

A discussion with a fixed template and attachments would do as a first step, if it carries a machine-readable block and a state (open, accepted, declined) the bridge can poll. Depends on versioned machine payloads (adom/wiki#277).

Why it matters. Without it, machine-side changes either stay undocumented or wait for someone to copy them into the wiki by hand. The bridge already records every change made at the machine (who, when, why, before and after) and builds the proposal; it needs somewhere to send it.

0 Replies

Log in to reply.