Closed bug report

Molecule boards go onto a kind board page with a self-made GLB: the flow never hands off to molecule-publish

noah · ·closed by John Lauer

Molecule boards go onto a kind board page with a self-made GLB: the flow never hands off to molecule-publish

What happened. AM32 ESC 2S-6S run, adom-aiflow 0.2.47, 2026-11-03. The spec has a molecule block, and the board is a 40 x 40 mm large-pin molecule with MP1 to MP4 and 11 machine contacts. finish, export and deliver passed, and finish-guard said complete. The board was then published following the AI Flow skills, and came out as a plain project page:

  • kind board;
  • a GLB the AI converted with step2glb and bound to component.parts.model_3d;
  • model status reports buildsThisPage: false, so the wiki's model registry never built the model, footprint or symbol;
  • the molecule cannot be imported into Hydrogen with wire attach points.

Where the flow leads the AI the wrong way

  1. tools/project-page.py (make_page) always creates the page with adom-wiki page create ... --kind board, even when the spec declares a molecule.

  2. The aiflow-project-page skill, step 2: "Explicitly set component.parts.model_3d to the reviewed complete board/assembly GLB". On a molecule page the registry serves its own model, and molecule-publish refuses a pushed GLB (REGISTRY_MODEL_FILE_REFUSED).

  3. The aiflow-molecule skill, section 5: "hand the bundle (STEP, board, every schematic sheet, .kicad_pro, custom 3D models, the GLB and the footprint and symbol JSON) to the molecule-publish skill". molecule-publish 3.0.0 refuses the GLB and the footprint and symbol JSON. What it needs is the STEP, the board, the schematic, <slug>-fab.zip and export.json, which kicad-export-molecule builds with molecule-publish's fab_bundle.py.

  4. Nothing tells the AI that molecule-publish is a separate package or how to install it:

    • package.json depends only on adom/adom-lbr and adom/adom-fields;
    • no NEXT: or Hint: line from export, finish or deliver names it;
    • finish-guard reports complete while the molecule is unpublished.

    The skill was not installed in this workspace (45 packages); bootstrap issue adom/hydrogen-bootstrap#9.

Suggested change

  • When the spec has molecule, create the page with --kind molecule. Do not push a GLB or bind model_3d for it, and say why in the aiflow-project-page skill.
  • Make the molecule publish a step after export for molecule specs. Its proof would be a passed registry build: model status showing the model slot with origin pipeline and metadataComplete: true. finish-guard should not report complete before that step.
  • Have export write the molecule bundle (<slug>-fab.zip and export.json through fab_bundle.py create) from the same saved board as the Gerbers, or call kicad-export-molecule's steps.
  • Correct the bundle list in aiflow-molecule section 5. Add adom/molecule-publish (and adom/kicad-export-molecule) to dependencies.

Related: the contact naming issue filed alongside this one (contacts named J<n> pass molecule check, while the registry counts only MC<n>).

1 Reply

John Lauer ·

Noah, fixed in adom-aiflow 0.2.49. A molecule board now hands off to molecule-publish.

The project page

  • When the spec has molecule, project-page creates the page as --kind molecule and never pushes a self-made GLB.
  • Its README says that molecule-publish puts the sources there and the wiki registry builds the model, footprint and symbol.
  • project-page-check no longer wants model_3d on a molecule page. If one is bound, the check suggests dropping it.

The aiflow-molecule skill (section 5) now lists the molecule-publish 3.x bundle:

  • the STEP, board, schematic sheets, <slug>-fab.zip and export.json;
  • the fab_bundle.py create command line;
  • what never goes in the bundle: a GLB, or footprint and symbol JSON;
  • how a publish is proven: adom-wiki model status.

The hand-off

  • adom/molecule-publish is now a dependency.
  • export, finish and deliver print a "NEXT (molecule)" suggestion until stage end molecule-publish --result <owner/slug> records it.

Not yet: export doesn't build the fab bundle itself, and nothing reads model status automatically. Both are next if you want them.

Upgrade: tell your AI "give me the latest adom-aiflow" (or adom-wiki pkg install adom/adom-aiflow); adom-aiflow --version says 0.2.49.

John Lauer closed this ·

Log in to reply.