Optional LED and MPN display variants: verified reusable assets and library guidance

Overview Files Skills Discover Packages Releases Dependencies Issues3 Breadcrumbs Pull Requests1 Activity

Closed general

John Lauer · 20d ago ·closed by John Lauer

For Fable: optional lit LED assets are ready for the component-library phase.

John requested reusable LED on/off STEP and GLB extras, with the MPN independently visible, defaulting to LED on + MPN on for the selected illustration. The ESC's two LED types are now published with tested extra files:

Each has on/off STEP and GLB, a standalone light-overlay STEP, six-state review across the pair, per-file SHA-256 provenance, manufacturer datasheet color evidence, retained source license, generator source and a two-LED checkbox viewer example. Both pages and their source files are now public; anonymous download hashes of both on STEP/GLB pairs match local output. The prior pages were private with sealed source, which a successful repo push did not reveal. The green page also had an incorrect Everlight brief; corrected to NationStar from its datasheet.

Reusable interface: named groups Adom.LED.Emission and Adom.LaserEtch.MPN, with glTF extras adomRole=led-emission/mpn-marking and defaultEnabled=true. GLB standard emissiveFactor makes the lens illustration luminous. No claim of calibrated photometry, electrical simulation, physical extra lens material, or guaranteed bloom/scene illumination. STEP retains colors and separately named geometry, but per-group visibility depends on the importer. KiCad needs selected on/off files unless its viewer grows per-group controls. The default board bindings were not changed by these optional downloads.

Suggested AI Flow library guidance: verify actual MPN/color from manufacturer evidence, offer lit variants, preserve plain models and polarity features, cache separately with provenance, record selected LED and MPN state in the library manifest, demonstrate both toggles, then use the selected variant in library tour and final board. Check anonymous asset access when promising global reuse; publication success alone is insufficient.

A stage-accounting limitation encountered: adom-aiflow stage start led-models --ai-thread "ESC AI Flow Astra" --run /home/adom/aiflow-esc-astra printed OK: stage led-models started at 2026-09-16T17:02:31Z by binary, although it is an AI-authored stage. take led-models=ai returned ERROR: unknown stage led-models with the fixed stage list. End note records that the work was performed by AI. Please allow actor=ai for custom stages or default manual stage starts to AI.

Local evidence: /home/adom/aiflow-esc-astra/components/quality-audit/led-variants on this AdomLapper container. viewer-check.json, states.png, public-download-check.json, build.py and per-part led-provenance.json. This is a working asset/demo contribution, not a claim the shared board viewers already expose these toggles.

1 Reply

John Lauer · 18d ago

Published and installed from insiders: adom-aiflow0.1.27 (and adom-fields0.3.1 for input identities). Source and registry publication both completed; installed hashes match the tested builds.

take accepts valid custom stage names with ai/binary ownership, and manual stage start defaults to ai while respecting an explicit decision. Verified native-text-review=ai on the maintenance run. Ownership remains recorded in the ledger.

Release notes: https://wiki.adom.inc/adom/adom-aiflow/files/docs/release-0.1.27.md Validation records: /home/adom/project/adom-aiflow-release-audit/ .